I’ve had Windows 7 running under the Parallels VM for quite some time now– just for those odd occasions when I might need to do something on that platform like, err, watching streaming European association football matches from servers in the the Middle East. (I am perhaps one of few Brits who do not bristle when I hear North Americans call football “soccer”, because, “soccer” is derived from “association” football, and was used once upon a time to distinguish itself from that other footballing code: rugby.
I never particularly worried about internal backup of the Windows stuff, because it is a pretty naked install, with the usual stuff added:
MSFT Office 2010… and Visio
and the whole VM was backed up as part of the usual Mac backup (via Carbon Copy Cloner). However, I found the need for an image of this system this morning, and in going through the usual route of creating an ISO in Win 7 I was somewhat surprised to see that the outcome would be a whopping 46GB. What to do? WellI found a pretty damned helpful page at Scott Hanselman’s Computer Zen, Guide to Freeing up Disk Space under Windows 7. Particularly:
rd /s temp
couple of files could not be deleted in this directory… one that was open by ClamAV, so shutting that down did the trick. Also
FXSAPIDebugLogFile.txt was locked. The following steps fixed that:
- Go to Control Panel
- Click on Program
- Click On “Turn Windows Features On and Off”.
- Navigate to Print and Document Services
- Now uncheck that option
- Now click Ok to confirm
- Restart the computer
Identifying the processes that had these files open was pretty straightforward, but oftentimes this is *not* the case, then I recommend the free Unlocker. It adda a contextual menu to Windows Explorer that will identify the process that is using any particular file: very useful if one ever comes across “The file is in use by another program or user”, or “Cannot delete file: Access is denied”, or some such.
After following Scott’s advice, I’d saved about 10GB. Not enough. A running of WinDirStat identified one huge file and one large directory. The file was
20100314201842.vdmk, the directory
arc_20100314201842. Being prudent I duplicated my Win732.pvm, deleted these files, crossed my fingers and restarted Parallels. And all was good with the world! Win 7 ran faster in the VM, and the size of the resulting ISO was a *much* improved 12GB, 3 DVDs worth.
If you find these files (your names will be different, these are obviously timestamps) in your Parallels VM, IT IS SAFE TO REMOVE THEM! I suspect they are left over from when I was toying with VMWare Fusion and VirtualBox. If
*vmdk does not look like “Virtual Machine DisK” I do not know what does.
And as for the initial ISO creation when I installed win 7 in parallels back in 2010: The contents of the install CD were copied to a temp dir on the Mac, Disk Utility was used to create a DMG file, and then an ISO was created using
It seemed faster to go this route as I had a soft copy of the install disk, and anything coming of off the hard drive was obviously going to install faster that the original install medium.