I can’t edit the message now - or I would - I believe I violated rule number one - no personal attacks. It was late at night. I apologize. As I can’t edit it, mods - please delete the original message. I will repost. At that moment - I was simply saying what I was thinking. While I am usually very good at saying things nicely - sometimes I have been known to be obtusely blunt in my opinions. I do not know why - sometimes things just pop out. Again - I apologize.
Let me try this again.
This thread is old - but it came up high in a search - so I want to add some things to it. My Windows dual install has, for the first time in my experience, produced this error. I’ve had to fix the hal.dll errors before, but not in a dual boot environment.
Re-installing windows WILL, without a doubt, no questions, no prisoners - destroy your grub mbr entries. In the OP case - a dual boot, linux and Windows, the hall.dll error has a high possibility of being associated with the linux install. This error also has about 10 jillion permutations - but they mostly point to “boot.ini”, the Windows partition boot record, a real hal.dll error, or hard drive/file system issues.
The Windows “how-to” guides mention the above - boot.ini, partition boot record. etc.
So, if you have this problem - start here:
How To Fix Missing Hal.dll Errors in Windows XP
That particular page covers most of the issues quite well.
The answer could be as simple as the partition pointers in the Windows boot.ini file. Also don’t hesitate to run chkdsk on the Windows volume, even if you are running fsck on the whole hard drive.
However, that page doesn’t cover linux/windows specific possibilities. For one thing - if you have to get to the reinstall stage, plan on fixing your grub (or lilo or grub2). I don’t know of anyone who has ever used the Windows multiple boot loader - so I don’t know how it would be affected. Fixing the MBR portion of grub and grub2 is not hard - but you should start the reinstall knowing how to fix it.
Since I am still in the middle of finding the solution in my case, I will come back and repost when I have found my answer. At the moment I am looking at doing the reinstall - but before I do that I want to try and mess with the boot.ini again. It points to the 2nd partition, which is correct - but I am wondering if it is looking at partitions the way grub does - where the numbering starts at 0.
boot.ini contains pointers like this one
In my current case it says 2, and Windows is on sda2, the 2nd primary partition. Should be good, but I’m still getting the error. So maybe it is seeing the logical partitions in front of it - or is counting like grub does. I don’t know and I still have to find out.
Worst possible case, I will have to reinstall Windows. Blech. Nuisance, but not killer.
As for myself, I am still working on answers, and if I find any - I will post them here.