Webspace of Eric Brodeur

Perspectives on storytelling and digital cinema technology

Category: Windows

The upgrade from VMware Fusion 1.x to 2.0 was smooth except for an error from Windows XP’s Device Manager. Before I could install the newest VMware Tools, Windows complained about “missing driver for Base System Device.”

Dismissing the error I installed VMware Tools 2.0 but the error persisted. On this tip I reinstalled VMware Tools using the Custom option. The VMCI driver was already selected (a head scratcher since this would suggest it was previously installed) but I continued the installation. Upon restart the missing driver was found.

Today I was tussling with a client’s computer in an effort to remove malware. During the process Windows XP decided it was no longer activated and during a reboot demanded to be activated or I would be logged off.

Windows Product Activation was either hosed and/or the malware prevented me from properly accessing the Internet. I decided against the 4-to-8 hour reinstall of Windows and application software while preserving existing user data. My shortcut? A spare hard drive and legit copy of Windows XP.

Cracking open the PC case I plugged in the spare hard disk, disconnecting the original one. The next hour was spent installing Windows XP to the same Service Pack level (WPA has changed over time). Without installing any additional updates I copied the WPA data file (c:\windows\system32\wpa.dbl) to a USB flash drive.

Reverting to the original hard disk I booted into Safe Mode (which recognizes USB flash drives) and copied the wpa.dbl file to its respective location on C:. Reboot.

At login, Windows asked to be activated and prompted me with choices – I was no longer stuck. The rest of the process was quick and painless.

Regardless of your backup strategy consider keeping a copy of the WPA file. Lest I forget to mention it, the malware was successfully removed.

Essential Windows software

Although I make a habit of avoiding Windows it’s unavoidable. A typical installation of Windows is devoid of many useful tools such as ISO creation and burning, a tabbed text editor, a useful file archiver…the list goes on.

I’ve built a list of core software, all free, which fills many of these gaps in Windows including:

  • Unzipping
  • Text editing
  • Media codecs
  • Remote control
  • Secure file deletion
  • ISO manipulation

Check out the complete list here.

Accessing Mac HFS volumes in Windows

Today I found myself staring at a FireWire drive formatted under Mac OS X with not a Mac in sight but an urgent need to extract data from said drive.

A bit of Googling revealed HFSExplorer, an excellent piece of software by Erik Larsson which reads Mac formatted volumes under Windows. This is a lightweight Java application with full source code and executables. A quick install and at launch HFSExplorer will autodetect an HFS volume or ask me to choose a volume from a list. In moments I’m greeted with a fully-browsable directory listing of the Mac HFS volume.

Extracting a 2 GB file took a few minutes to complete but a progress bar guides you to fulfillment. A confirmation dialogue informs of completion and the file is at your disposal in Windows.

There are some limitations in volume types, such as Mac OS X Extended with Case Sensitivity, but your typical OS X Non/Journaled volume works fine.

HFSExplorer is a must-have for those times when you forget to copy your Mac-centric data files to Windows-friendly media.

Windows logoThe tedium of a Windows user account without Administrator privilege is almost unbearable. Installing software and other updates would require logout/in as Administrator and, while not difficult, is a hassle.

Microsoft introduced the RunAs command from the Command Prompt and the graphical user interface to overcome this. Right-click a program, choose Run As…, and enter your Administrator details. The application will install within your limited user account.

The trouble arises when you want to install an MSI file because they aren’t executables like SETUP.EXE. You’ll find that right-clicking an MSI from Windows Explorer only provides an Install option, not Run As. This makes it almost impossible to install the MSI from a limited user account.

I found ways to hack your Registry to enable RunAs for MSI files but there’s an easier way if you don’t mind some typing. In short, you’ll be using the command line to execute MSIEXEC using runas and referencing the MSI file. Example:

runas /u:[domain]\[user] "msiexec.exe /i [path-to-file]\[file.MSI]"

Substitute the bracketed fields as needed. If you are not connected to a Windows Server Domain you can ignore the [domain]\ text. Make sure the MSIEXEC command is enclosed in double-quotes. You may have trouble if there are space characters in your folder path or filename; try enclosing them in double-quotes or copy the MSI file to a location such as C:\TEMP to keep the path simple.

Hit Enter and you’ll be prompted to type a password (assuming Administrator) and the MSI will install as if you chose Run As… from Windows Explorer.

Powered by WordPress. Theme: Motion by 85ideas.