I've gotten tired of reading through pages and pages to find a hint on dealing with a new install. Perhaps this thread can be one of solutions and not problem posts. To help this concept, if you have a problem with a tip post or have an install issue, then create a new thread until someone can verify and come up with a solution. I think it is best to state your hardware and software before stating your tip. That way, different configs designed for each user can be quickly found. Here are mine for BootCamp and WinXP Pro SP3 using Parallels 4.0.3810 (1/23/09 build or 23/1/09 for non US readers). Hardware-- Model Name: MacBook Pro Model Identifier: MacBookPro3,1 Processor Name: Intel Core 2 Duo Processor Speed: 2.2 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 4 MB Memory: 2 GB Bus Speed: 800 MHz Boot ROM Version: MBP31.0070.B07 SMC Version: 1.16f8 Boot Camp Prep Prepare that install by making sure it runs correctly. Why bring problems into your Parallels VM? I've found Winclone to be great when a BootCamp partition got whacked and started causing corruption. Now I first back up BootCamp after a good install -- then after the following steps are done -- I create the VM based on the BootCamp partition. --When you have problems, try using the BootCamp Asst to delete the partition and start over again. Make sure you have a cloned backup. --I've had no issues using the built in Windows ntfs conversion for a smaller Fat32 partition when getting a larger drive. You'll need that if you go over the Fat32 partition size. Don't worry about checking the setup in the Disk Utility after having the BootCamp Asst make a large partition size, for it will say it's Fat32. Once you either install a new Windows operating system and partition it as ntfs or clone a ntfs backup, the ntfs partition will take hold. --Nor have I had problems migrating to a new and larger hard drive on my laptop. All thanks to the free Winclone. It saved me a reinstall. For the MacOS partition, I used SuperDuper after removing the BootCamp partition. --Make sure the BootCamp drivers are properly running and you are using v2.1. Reinstall the 2.1 BootCamp drivers if you are having problems. See if that helps. If you uninstall the BootCamp drivers you will need the 10.5 install DVD to first install the 2.0 version berfor the 2.1 update. Check the device manager to make sure everything is running with proper drivers. --In BootCamp, run a drive utility to correct any file errors and then defrag. --Use TweakUI (a MS Powertoy) to set the "login" to auto with the password set if windows opens to the login screen for a password. That prevents the Parallels auto install from freezing which makes you have to break into manual with the four finger salute of Ctrl-Option-Command-R. The install must have windows open to the desktop to correctly run based on my experience. --Turn off all anti-virus programs that monitor script behavior. That will freeze the auto install too. --If you have Parallels Tools installed, use the Windows "Add Remove Software" control panel app while running in BootCamp to uninstall it. --Boot into MacOS and back the BootCamp partition up in Winclone to save all this work. Now you are ready. Parallels Install --Open up Parallels and delete the VM if this is a reinstall. Use the delete files option. --On the first start Parallels opens VM Setup Asst. At the "Operating System Detection" screen select "Skip Detection", make your OpSys selection on the next, and on the next screen select "Custom" so you choose the BootCamp partition. --Run through all the remaining screens with your selected options. --When the last screen asks if you want to run it, SAY NO for there are more options available elsewhere. (Figure almost every time you make configuration changes to the VM you will most likely have to uninstall Tools and then reinstall. So it's best not to allow Parallels to start up Windows at this point for it will install Tools automatically) --Now you can click on the configuration button and have all the options available to set your VM up. Go through each setting on the left and make your choices. Click "OK". --Now "Start" the VM. --Note: If you have run out of activation 'points' with Windows, it will freeze the auto install. If you see the progress bar stop for 2-5 minutes, then use Ctrl-Option-Command-R to break into manual mode and you will probably see the MS "You have to activte" window. You might find you have no mouse or network capabilities for this has stopped the Parallels install at a early point. I've found the keyboard works on a laptop (don't know about towers with USB keyboards) and have been able to go through all the steps with a friendly call center rep from India via the telephone using the "Tab", arrows, and "Enter" keys. Try it. You'll see field and button changes if this method is successful. --After the auto install completes and Windows starts up, the cpu will probably be burning hot. Shut down Windows and Parallels, and Restart the Mac. --Go back and start your VM. Decide if you want the Kaspersky Anti-Virus installed. --Let the VM sit for a while to allow all the prefetching to be done. --Change your login options back in Tweak UI, and activate your Anti-Virus (script blocking program) if you had shut it down. Works for me, and I've tried everything in the past to the point of having to call India for permission to run windows. No high cpu, a quick Windows start. I'm actually pretty happy with V4 aside from a few quirks. One last tip. When tools is properly installed, you will always see a sprocket icon on the lower right of the window, even before you start the VM. If you get a warning on the bottom of the screen that Parallels Tools is not installed then you are not operating correctly. I've run for months not realizing that because after windows starts up the notice goes away and the Parallels Menu bar may only say 'Reinstall Tools' instead of 'Install'. I've gotten the high cpu issues with that one thinking Tools was fully installed when it really wasn't. Now I don't expect this to work for everyone nor do I think this is the only way. That's the purpose of the thread if it takes hold. Solutions to try without the baggage of multiple pages of troubleshooting. Been there, read that... Any other tips out there? For example, how's Acronis working out?