I've been experiencing the same thing rth described.. with the unfortunate exception that I hadn't made a system restore point from the start to return to so bootcamp is still broken... It works under parallels, but restarting the Mac from the bootcamp disk gets to the point of the black screen that says windows.. and its loading windows and the green dots are moving back and forth.. and then the green dots stop moving and its hung.. attempting to boot next time to safe mode gets to crcdisk.sys and then it stops/hangs.. Booting to the windows install CD and telling it to repair leads to it claiming it couldn't find any problems..
I'm also running Vista Ultimate, an 8 core Mac Pro with 9 gig RAM and lots of disk space.. Bootcamp broke back around one of the version 3 releases, likely the same one rth found to be the issue, and I've upgraded to each new Parallels release (now up through 5570) and after running running under Parallels with the newest tools installed (hoping something might have been fixed).. I've shut down and tried to restart the Mac under bootcamp and still gotten the same problem.. I also upgraded the Mac to Leopard and when running under Parallels tried installing the newest Bootcamp drivers off the Leopard install disk.. and still the same problem..
It'd be useful to know what files Parallels broke and how to fix/reinstall them.. I'd prefer not to need to need to reinstall vista on a new partition, etc.. (don't know if there is some version of the vista install (rather than just repair) that will keep all my data but fix the issue by writing missing/corrupt system files that repair didn't spot..).
Obviously if Parallels doesn't find a way to fix their bug I may need to waste time to create a new Bootcamp partition and install Vista from scratch, etc.. Though until they fix the bug presumably the new bootcamp will just be broken by parallels again (though I'd have a restore point to fall back on). I can do without booting the Mac to bootcamp for the moment so I'll try to wait till Parallels has fixed things before wasting time on new bootcamp partitions..
As another data point, I'd waited a long time before trying this to avoid further complicating things, but I just used VMWare Fusion with the same Bootcamp partition, and it was able to boot.. then I tried again and the Mac still has the same problem booting directly to the Bootcamp partition.. So whatever it is that Parallels broke is used by bootcamp run directly.. but not when run under a VM from either company..
Last edited: Nov 26, 2007