http://tomgee.us/?p=172

This is from the original blog post (thanks to Tom Gee):

——————————————————–

The problem

Today, when I booted directly into my Windows 7 partition (not via VMWare), I noticed that I couldn’t print anything anymore.

I checked the Event Viewer and found the following error in the System log:
The Print Spooler service terminated unexpectedly.

In the Application section of the Event Viewer, I found the following:

Faulting application name: spoolsv.exe, version: 6.1.7600.16385, time stamp: 0×4a5bd3d1
Faulting module name: TPVMMon.dll, version: 2.0.51.5, time stamp: 0×48359080
Exception code: 0xc0000005
Fault offset: 0×000000000000846e
Faulting process id: 0×1300
Faulting application start time: 0×01caa2aa2c4394d8
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\System32\TPVMMon.dll
Report Id: 7188e318-0e9d-11df-9123-895fd79b6e49
Faulting application name: spoolsv.exe, version: 6.1.7600.16385, time stamp: 0×4a5bd3d1Faulting module name: TPVMMon.dll, version: 2.0.51.5, time stamp: 0×48359080Exception code: 0xc0000005Fault offset: 0×000000000000846eFaulting process id: 0×1300Faulting application start time: 0×01caa2aa2c4394d8Faulting application path: C:\Windows\System32\spoolsv.exeFaulting module path: C:\Windows\System32\TPVMMon.dllReport Id: 7188e318-0e9d-11df-9123-895fd79b6e49

The only thing I could attribute the Print Spooler issue to was VMWare Fusion.

I tried uninstalling the VMWare Tools program listed in the Control Panel > Uninstall Program section, but it would not remove.

No errors were displayed, but the program wouldn’t remove from the Programs list.

The solution

I deleted the following folder (and all related subkeys) from the Registry (via Start > Run > regedit):

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Monitors\ThinPrint Print Port Monitor for VMWare]

My partition setup is a bit special, 3 partitions in total. I want Mac OS on the first partition, Vista 64bit on the second and Vista 32 bit on the last.

Installing Mac OS X is no problem, slide in the installation DVD fire up the Disk Utility (Do not install yet). Partition the disc as planned (remember to choose GPT as partitioning system). The first partition should be the suggested Mac, the two nest should be MS-DOS FAT (Don't worry, we will reformat to NTFS later).

Install Mac OSX.

After that, put the Vista x64 installation DVD in the drive and initiate that installation. There should not be any real problems in this.

Finish the first Vista installation and boot up. Now we need to install the Boot Camp 64bit 2.1, and this can be a bit of a problem. The problem is, the Boot camp software on the Mac OS X DVDs are not compatible with Vista 64bit on an iMac. I then downloaded the updated Boot Camp 2.1 for Vista 64. Unfortunately this is an update, requiring an earlier version, which we cannot install. Read more about that here: http://www.iotashan.com/index.php/2008/07/06/install-vista-x64-sp1-under-bootcamp/

But do the following and you should be home safe:

1. Download Boot Camp Update 2.1 for Windows Vista 64
   http://www.apple.com/downloads/macosx/apple/application_updates/bootcampupdate21forwindowsvista64.html
2. Install an older version of Boot Camp from the installation DVDs (I used Leopard 10.5 update disc)
3. Run the downloaded Boot Camp 2.1 64bit update
4. If you encounter the problem "Error applying transforms. Verify that the specified transform paths are valid."
   The system is trying to tell you (I think) that you are installing a software that is using another culture/language than your system.
   Read more about resolving this issue here or find a short version below:
   http://www.tiagodherbe.eu/Page/3191/articleType/ArticleView/ArticleID/118/Home.aspx
5. Now try the install again.

This worked for me.

Fixing "Error applying…"

1. Start the Registry editor
2. Go to this key (or search for Boot Camp): {HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\1972E1D59AAA4FE4B9DA97EEB1F70D04}
3. Change language to 409 (1033, the culture/language of the installation)
4. Try the install again