iTunes hates Windows

So I update iTunes and get the following error message when I launch it:

"The iTunes application could not be opened. An unknown error occurred (0x666D743F)."

It turns out that by default you can't run iTunes through a Remote Desktop Connection. Luckily, the fix is simple, from within the Remote Desktop Connection program navigate to:

Options -> Local Resources -> Remote Computer Sound

Then select either:
"Leave at remote computer" or "Do not play"

As long as you don't select "Bring to this computer", which causes iTunes to crash when Windows attempts to reroute the audio, everything will work fine.

Who uses a serial mouse?

So you've got your GPS plugged into your serial port and you boot your computer. Only when it comes up you find that your mouse is bouncing all over the screen and randomly clicking shit. Well, this is because Windows thinks your GPS is a serial mouse. Here's how to fix this on Windows XP by telling the OS not to load a serial mouse:

1. Click Start -> Run
2. Type regedit
3. Browse to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\sermouse]
4. Change the value "Start"=dword:00000003 to "Start"=dword:00000004 by double clicking the "Start" value and changing the 3 in the box to a 4.
5. You're done!

Props to ret of the mp3car.com forums for showing me this tip. Note that some Windows updates will revert this setting and force you to perform the fix over again. If your GPS is permanently wired into your internal serial port like mine was, you can just disable the serial port in the BIOS until you have a chance to apply the fix.

Warning, I am a: "fail to set the install registry key"

Tried to update the my ATI Radeon X800's Catalyst drivers to version 5.8, only to be greated with a wonderful message from the driver installer:

"fail to set the install registry key"

Luckily I found a solution and I'm just dying to pass it on to you:

(Courtesy saintberry)

[QUOTE]
1) uninstall cat driver and the CP from yo pute
2) go to http://p-nand-q.com/download/supershell.html and download supershell
3) after unzipping it, run the proggie and type "regedit" then wack enter
4) in the registry editor nav to HKLM>Software and get rid of anything ATi related
5) close regedit go back to supershell type "exit" then wack enter agian.
6) restart if you want...i didnt
7) install new drivers/cp and restart...all should now be working with TABS!!!
[/QUOTE]

If you're still having problems you might want to try installing the latest .NET Framework (v2.0) available here: http://msdn.microsoft.com/netframework/ After installing (or using the package's repair function) try repeating the above Catalyst install procedure again.

What about me Mr. H and Mr. P?

I have an HP Photosmart 7550 printer, I also have Windows XP Pro x64 Edition. HP decided that there was no compelling reason to make a driver for this combination. Luckily, they were kind enough to point me in the right direction. To get your HP Deskjet, Officejet, PSC, and Photosmart printers working in x64 you definately want to check out this page: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00364537 For the HP Photosmart 7550 check out this page specifically: http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c00365046&dlc=en&lc=en&cc=us If either of these links go dead just head over to the HP website and type c00364537 in the search area at the bottom.

Fire Liar

I download the latest Linux distro and throw a blank DVD in the drive only to find that, WTF, my Firewire DVD-RW drive is no longer supported by Windows. I was just using it yesterday, I think to myself. Well after absolutely no luck finding drivers (apparently they're only required for and thus only developed for Windows 98) I finally found a solution. After downloading and installing the latest non-beta BIOS for my Asus K8V SE Deluxe my drive is working again as good as new. The new Asus BIOS must have improved Firewire support, so if you're having a similar problem getting peripherals to work I urge you not to forget about trying a BIOS update.

DRM Implementing Bastards

So you just bought or built a brand new shiney media center PC only to find that, oh shit, I can't play 3/4 of the DVDs ever made on it. Welcome to the world of DRM (Digital Rights Management), where it just so happens 3/4 of DVD publishers prevent the playback of DVDs through any video outputs designed for a TV. This includes, especially, component and S-Video. Well, today's your lucky day as there is a solution and a very good one at that. Head over to DVDIdle.com and grab a copy of DVD Region+CSS Free: http://www.dvdidle.com/dvd-region-free.htm Once installed this sweet app will let you watch any protected DVD you could imagine through your TV outputs, yes, including component and S-Video.

Really Shoot the Messenger (with x64 compatibility)

So you're fed up of that jack ass MSN Messenger wasting your precious RAM everytime you turn on your computer. Well here's the non-convoluted and very straightforward way to keep that program closed from where it all begins.

1. Click Start -> Run...
2. Type "msconfig" and click OK
3. Click the Startup tab and uncheck msmsgs
4. Click OK

Now when you restart your computer and for the rest of eternity MSN Messenger will remain closed. The first time you restart your computer you'll see a message telling you that settings have been changed, just click the check box saying not to tell you this anymore and click OK. You're all set!

But I Don't Want to Find a Path

Windows 2000 and Windows XP do away with the AUTOEXEC.BAT file forcing you to set command prompt environment variables in a different manner. Personally, I needed to add the Java SDK bin directory to my PATH environment variable, here's how:

1. Right click My Computer -> Properties
2. Click the Advanced tab and then Environment Variables
3. Under "User variables for (current user)" click New
4. Name the new variable PATH and give it the value to which you want to set your PATH, in my case I gave it the value: D:\j2sdk1.4.2_08\bin
5. Click OK three times and you're done; the path will be automatically appended to your PATH variable whenever you open the command prompt

For more info you might want to check out the following Microsoft document: http://support.microsoft.com/default.aspx?scid=kb;en-us;310519&sd=tech