William Bartholomew

There is a feature in Windows XP and Vista that not many people know which can save you endless hours and it’s called pushd.

From the command-line if you type:

pushd \\someserver\someshare\somedirectory

Then Windows will automatically map a temporary drive to \\someserver\someshare, change to that drive, then change directory to somedirectory.

When you’re finished you can then type:

popd

Then Windows will change back to your original working directory and remove the mapped drive.

Here is an example:

C:\Temp\> pushd \\someserver\someshare\somedirectory
X:\somedirectory\> del somefile.txt
X:\somedirectory\> popd
C:\Temp\ >

Enjoy!

Well, it seems that yesterday’s issue was not hardware or driver related at all (sorry Asus!). Windows Server 2008 (“Longhorn”) does not install wireless networking support by default and you must install it by adding the Wireless Networking feature (details at http://blog.kirupa.com/?p=99). Although I do feel a little stupid (especially after buying a second wireless adapter) it would have been nice if the Network Diagnostics told me that Wireless Networking had to be installed rather than suggesting a hardware/driver issue or a missing TCP/IP protocol.

I’m currently in the process of setting up a Windows Server 2008 box and cannot get an Asus WL-168g USB wireless adapter working.

The adapter wasn’t detected by the installation so I installed the Vista driver from the Asus website. With this driver installed the wireless connection appears in Network Connections but is disabled, when you try and enable it the connection is enabled briefly and then is disabled again without any error message.

Installing the Windows 2000/2003 driver fails completely saying that the device already exists (even though I uninstalled it).

Off to the local computer retailers tomorrow to buy another wireless card I’d say… Any recommendations?