hal.dll missing or corrupted :( with BootCamp

M

mush

Junior Member
[SOLVED]hal.dll missing or corrupted :( with BootCamp

Hi, today i tryed to launch parallels running my Bootcamp partition.
And I found this message just before windows starts running.
And once it was perfectly running before today, I got this problem.

HERE IS THE SOLUTION
HERE IS THE SOLUTION said:
  • Launch parallels desktop on MacOsX
  • Select EDIT/Virtual machine/change boot sequence/ put first CDROM
  • Launch parallels, Laucnh windows CD
  • Don't go on restaure console MENU
  • Just make a Windows reinstallation
  • REBOOT, and ALL IS OK ;)
Click to expand...



So I watched everything who could help me to solve this.

I tryed this http://kb.parallels.com/entry/63/526/0/ and so http://kb.parallels.com/entry/63/526/0/
which means
FAQ parallels said:
For virtual machine that uses Boot Camp partition as a hard disk (Parallels Desktop for Mac only):

1. Launch Macintosh HD - Applications - Utilities - Boot Camp Assistant.
2. Choose to "Start Windows Installation".
3. Insert Windows Installation Disk into your Mac CD/DVD Drive and restart the Mac.
4. When prompted press any key to boot from the Windows CD.
5. Windows Setup should start loading, wait till it loads completely then press Enter (Return) key.
6. Press F8 to accept Windows License Agreement.
7. Now Windows should scan your VM for the existing Windows installation - wait for it to finish and choose to repair existing installation.
8. Wait till the repair operation finishes.
9. Start Windows in the Virtual Machine in order to re-install Parallels Tools .
Click to expand...

But still the same problem, it seems that the system is installating something or updating, but when launching BootCamp via parallels i get the same error message.

I tryed to boot with Win Xp pro CD, and in the MS DOS console i run :

bootcfg /rebuild --> nothing
EXPAND D:\i386\driver.cab /F:hal.dll C:\windows\system32 --> told me that hal.dll does not exist in driver.cab package :(
Click to expand...

I heard in other places that the problem is not always from the hal.dll file but could be too from the boot.ini file.
If someone know what I have to put on this file, cause I installed BootCamp un FAT32 system, so the file would be easy to edit.

here is my boot.ini file :
boot.ini said:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
Click to expand...


UPDATE : Tryed to make another VM for bootcamp and still the same error message.
I'm very frustated to see my Bootcamp partition on my MacOsX desktop and i can't do nothing with it :(
 
Last edited:
Well it was worth a try. So neither of the boot.ini that are in that post work in Parallels or booting directly into Boot Camp? If you have not already, try replacing the contents of the boot.ini with
Code: 
[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Parallels configuration" /fastdetect /NoExecute=OptOut
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /kernel=ntkopvs_.exe /hal=halopvs_.dll
again, but then try booting directly into Boot Camp and quickly select the "Microsoft Windows XP Professional" configuration.
 
Still the same with your new boot.ini
But there is 2 things weird since the beginning :

first : when i took your boot.ini file and i replaced mine by yours, VM start 3 boot options, of course i've tryed all but nothing go. I get hal.dll missing and in one other i have nothing just black screen with the cursor.

second : : is that when i boot with bootcamp partition in windows safe mode, I have to activate my windows altought that i ve activated it before ???????
 
wow, the same thing happened to me today. This morning I was running parallels just fine and I restarted my whole computer and upon restart and attempting to open parallels I got the missing or corrupted hal.dll file. It also told me I needed to download the dll files for the kernel.
 
The only thing I use is the Boot Camp partition, but I am out of town for Thanksgiving and don't have my windows boot disk, but I will try it as soon as I get home.
 
where should i do it ?
Booting with bootcamp partition or with parallels VM ?
With the first it's possible, but with the second I can't reach parallels tools installed on the Windows OS, because of course that's the problem i trying to solve.
 
mush said:
where should i do it ?
Booting with bootcamp partition or with parallels VM ?
With the first it's possible, but with the second I can't reach parallels tools installed on the Windows OS, because of course that's the problem i trying to solve.
Click to expand...

Booting from the Boot Camp partition of course, since your Boot Camp VM doesn't work. I probably should have been more specific with the wording in my previous post; you will likely need to do a manual uninstall of Parallels Tools since the uninstaller will probably insist that it needs to be run through a Parallels VM.
 
ok I just uninstalled parallels tools, what should I do now ?

update : Ok have to go to bed, what about uninstall and reinstall parallels on MacOsX ?
 
Last edited:
mush said:
ok I just uninstalled parallels tools, what should I do now ?

update : Ok have to go to bed, what about uninstall and reinstall parallels on MacOsX ?
Click to expand...

I am guessing that if Parallels Tools is fully uninstalled then Parallels Desktop should be able to start the Boot Camp VM and reinstall Parallels Tools. If it doesn't work then let me know what you get when trying to boot the Boot Camp VM (black screen, error message, etc.).
 
the error message is always the same, just before windows is loading that told me that Windows cannot run because the file hal.dll is missing or corrupt, altought the file is on the hard disk but I've downloaded another hal.dll from the net to test and still nothing...
So I replace the original file, but still the same :(
 
You must log in or register to reply here.
Back
Top