SUCCESS!!!!!!!!!! I never thought Windows could look so pretty, LOL! I still have to do the Parallels backup.
There so far seems to be one issue that is now coming up when going into Windows. I am now getting the same error message that I started with except now it's this file: VSUTIL.dll
So you don't have to scroll up here's the original error msg, just replace the filename below with VSUTIL.dll
"winlogon.exe - Bad Image
The application or DLL c:\WINDOWS\system32\KBDUS.DLL is not a valid windows image. Please check this against your installation diskette.
OK BUTTON"
However, this new error msg is not preventing me from getting into Windows, thank goodness. I hope there's an easier way to fix it than going through this entire process again. Any ideas?
UPDATE: I *think* I have solved the VSUTIL.dll problem. For anyone else who has this problem, if you are using the ZoneAlarm firewall this is where it seems my issue stems from. ZA uses vsutil.dll but their are multiple files of the same name. You need to do a thorough search of all files and folders to find all references to it. You should then be able to determine which ones are owned by ZA/True Vector by hovering your mouse over the filename or right clicking it and go to Properties. The one I had that was NOT owned by ZA/True Vector is located here:
C:\windows\system32\vsutil.dll
It showed a file size of 0 (zero). I renamed this file vsutil.dll.OLD and this seems to have cleared up the error and after following some uninstall and reinstall instructions for Zone Alarm, it's now working and the vsutil.dll is still gone and so far my VM has not crashed.
WARNING: I am not a computer expert. I'm pretty good with Windows stuff, but DO THIS AT YOUR OWN RISK. I do not take responsibility if something goes wrong with your computer after following these instructions.
To John: THANK YOU - you definitely are my Hero of the Day! I'm now cloning my VM per your Parallels instructions and it's being cloned to my external drive and will also be added to my online backup service files. I have two more questions:
1) The cloned VM is now showing as a mounted drive on my desktop. Should I leave it there? I ask because it seems seasoned Mac users are quite adamant about not having to much stuff on the desktop but this seems awful handy if my main VM should go down again. It looks like by doing this if I do regular backups of it, that I could then work from the clone until I had time to fix the original VM.
2) It seems there is not a way to automate the backup (clone) so that it backs up on it's own at some set interval. Am I missing something?
Last edited: Jul 20, 2008