- September 2018
- May 2018
- December 2017
- April 2017
- June 2016
- February 2016
- November 2015
- January 2015
- August 2014
- July 2014
- May 2014
- March 2014
- February 2014
- January 2014
- November 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- December 2012
- November 2012
- September 2012
- June 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- June 2011
- May 2011
- March 2011
- January 2011
- October 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- September 2009
- July 2009
- June 2009
- May 2009
- March 2009
- September 2008
- April 2008
- December 2007
- June 2007
- June 2005
- September 2004
- May 2002
- October 2001
- August 2001
Blog posts tagged "windows vista" – Posts 1..5 of 6 posts found:

2017-04-15: MIDI Selector tool updated
And then Windows 10 Creators Update came out. Along with all kinds of improvements came the reset of all customisation to default settings (ugh!). This included resetting the MIDI output to Microsoft's default and underwhelming "Microsoft GS Wavetable Synth". I found my MIDI Selector tool was no longer completely effective on Windows 10 x64 and had a minor bug as well as some slight inefficiencies. Fixed version 1.0.1 has been posted on the tools page.

2013-05-26: MIDI Selector tool created
Windows Vista and later no longer include the MIDI mapper that was used in earlier Windows versions to route MIDI output to the preferred device. Vista did away with this, supporting only the rather underwhelming "Microsoft GS Wavetable Synth". While this is adequate for most users, it simply won't do if you have a proper MIDI synth for retro gaming or for playing MIDI files through Media Player. There exist several tools on the net that can change the default MIDI output device, but it appears there are differences in registry keys used between Windows Vista and Windows 7. The tool for one simply won't work on the other, so unless you knew which one to use, you'd still be stuck with Microsoft's softsynth.

2012-01-14: Accessing sites blocked by your ISP
Just recently, MPAA/RIAA sock puppets Brein managed to convince some clueless judge to order two of the largest ISPs in the Netherlands, XS4ALL and Ziggo to block (in)famous torrent website The Pirate Bay. TPB have put up a message that is shown to anyone visiting from a Dutch IP address, as shown below. XSALL and Ziggo have both announced they will appeal to a higher court, which is a good thing. I don't even use TPB myself and wouldn't really miss it, but I do care deeply about worthless assholes doing anything limiting my internet access. So, how would this work and what can I (or anyone) do to give these lying thieves the finger and circumvent these blocks if they are upheld by the higher courts?

2011-03-27: Tunneling IPv6 over IPv4 using SixXS on Win7 x64
It's been a long time coming, and now the IPv4 address pool has been exhausted. Still it doesn't seem like world is scrambling to switch over to IPv6 (it doesn't even seem like they're preparing for it, even though they ought to be ready). My provider hasn't even given any information about their plans for implementing IPv6. This makes it difficult to see if my own network or any of the stuff I make will handle IPv6. Fortunately, there are services that allow you to experiment with IPv6 by tunneling it through IPv4. SixXS is one such service, but setting up a tunnels, especially on Windows 7 (64 bit) is a bit more involved than you might think from the documentation or the 10 step guide and there's a few things that are unclear or downright missing. Here's my step-by-step walkthrough.

2010-01-22: Windows Update woes
Windows Update is a great technology. It ensures that most Windows users are automatically kept up to date with the latest security patches for their OS. Especially now that is no longer tied to Microsoft's Internet Explorer browser, I'm a big fan (with one exception). Unfortunately, on rare occasions, the Windows Update client gets in a corrupted state and things get messed up in a big way. This can be difficult to diagnose or troubleshoot.