Recently, I’ve been experiencing the joy that is Windows Home Server. To be short, I’d absolutely recommend WHS to anyone with at least two computers in their house. Anyway, in an effort to reduce redundancy between my computers, I’ve centralized my “Documents” folder onto my WHS machine. For the most part, this experience has been awesome. Anyway, As this posts’ title alludes to, I sometimes get the following error when installing new applications: “Error 1327. Invalid Drive U:/” My “U” drive happens to be a mapped network share that points to my documents folder. Apparently, these applications don’t like networks very much! In order to solve this problem, I’m forced to manually remap all of my shares to a local folder. Definitely not cool.
If, by chance, you’re like me and recently installed Visual Studio 2008 onto a 64-bit version of Windows, you may be getting the following error when you attempt to debug an application:
The components for the 64-bit debugger are not registered. Please repair your Visual Studio 2008 Remote Debugger installation via ‘Add or Remove Programs’ in Control Panel.
The reasoning behind this error is discussed here. In short, because VS2008 is still a 32-bit process, it cannot directly attach itself to a 64-bit application (.NET defaults to 64-bits when you’re on a 64-bit OS). As such, VS2008 needs to use the remote debugger to bridge the 32/64-bit gap. Unfortunately, this feature isn’t installed by default! In reading the error message, you are lead to believe that this can be fixed by adding additional components from the VS2008 add/remove programs screen. However, in actuality, you’ll need to run a separate application (found in CD-DRIVE:\Remote Debugger\x64). After installing the 64-bit debugger, you should see this problem disappear.