I use Parallels with the Bootcamp partition option. I had to close out and redo my whole Bootcamp partition from scratch. After doing so, and reinstalling Parallels 2.5, and later the newest 2.x (June 2007), when XP starts in Bootcamp, I see 2 installs to choose from. The top one is Parallels, and bottom one is Windows XP . If I let it sit a few seconds, it tries to start the Parallels one, and it stops with a black screen with white text, stating there is a corrupt or missing file: hal.dll . If I am quick, and arrow down to the second line of installs, the one that says Microsoft XP, it starts just fine. So, I renamed the hal.dll as hal.old, and got the file reinstalled off my Windows XP Pro (OEM) disk, using expand or extract, I forget which. It reinstalled a nw hal.dll. However, it still gives the same message about the error. Running Parallels from the Mac side works fine, it is just the startup in Bootcamp. Why is there this funny behavior, and is there a fix?
Simple: Just Delete boot.ini Real simple, just delete "boot.ini" and windows should re-creat it by its self, thereby correcting the problem.
Where is boot.ini? I searched all the files and hidden files in My Computer in Bootcamp, does not find boot.ini. Where does it live?
Hello, if you can't boot your Windows VM an Windows Guest OS boot process results in BSOD with an error message "HAL.DLL file is missing or corrupted", you can try to repair Windows installation. Best Regards, Alicia.
