Have you considered formatting the system?
Ha...just trying to keep it light!
Main Topics
Browse All TopicsI couldn’t boot my system
A hal.dll is corrupted!
So, I used the start up disk technique which is really useful in such occasions!
Then I copied a hal.dll file from another computer to the one in labor.
so I still can’t reboot because of the same problem!
Don’t ever try to go even close the Ever Solution of Mr.FORMAT.
I’m not formatting my system.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
if that's not working, here is another solution, but it's quite radical actually...
quote:
I found the fix to this problem. 1. It is the corruption of the boot.ini file. 2. To fix it, I did a parallel install of XP to create a new boot.ini file and get access to the PC. 3. I have seen references to booting off of the XP CD-ROM and this works by going to setup and then selecting "Repair". This only works however when the setup program actually sees the installation to repair. In my case it did not, so I did the paralleled install. 4. Using the paralleled install, I modified the boot.ini file so that it would boot off of my old installation and not the new one. This is done by change the reference for the [boot loader] section to refer to the original install folder. In my case, the big issue was that the boot.ini was corrupted by a program called BOOTXP and it was not referring to the correct partition. 5. The only down side is that I had to reactivate XP. After all of this, I am back in business and no thanks to MS Support. They were not sure what to do. If you want info. on how to delete the paralleled install, let me know. Hope this helps.
Actually, you may be able to avoind much of the dram by examing the existing Boot.ini. The problem may be that iT is not referring to the correct location of the windows installation.
Boot to a command prompt and type the following
Copy boot.ini boot.bak - to make a backup
(if you get in trouble type "copy boot.bak boot.ini" to restore)
attrib -h -r -s boot.ini
to make the file editable
then type
edit boot.ini
under the heading [operating systems]
you'll see something like default
multi(0)disk(0)rdisk(0)par
might be a little difficult to figure out where the mistake is, but multi 0 means the primary controller, disk (0) is always (0), rdisk is the physical disk number, and the partition is the partition number.(beginning at 1, not 0)
Basically if windows is on the first partition of your only hard disk, it should be multi 0, disk0,rdisk0,part1
and if you installed on d, it'll mean the partition value is 2. (Unless thats a second disk, then the rdisk value is 1, and partition is also 1)
once you have made changes, press alt, f and x to exit
If the error you get is that the following file is missing or corrupt "hal.dll"
and windows can't find the file in <windows root>\system32
Then you can solve it by installing XP on another hard disk, put your old disk as slave and copy the new hal.dll to the same directory on your old disk.
Since this is only your hardware abstraction layer, this doesn't change anything to your data.
I hope this is a solution to your problem.
i got the same corrupt "hal.dll" but it had to do with
multi(0)disk(0)rdisk(0)par
reading something like...
signature(s234894)disk(0)r
i find it easiest to fix these problems by just making the hard drive a slave to an existing computer and you can find and edit F:\boot.ini (make under tools and folder options that you don't have the "hide protected operating system files" checked) with the ease of XP and notepad (not a big fan of DOS (never learned))
GO TO POPULARTOOLZ IT HAS LINKS TO YOU WOULDNT BELIEVE THIS WINXP CORP WITH IT YOU DONT HAVE TO HAVE IT REGISTERED WHEN YOU EXCEED THE MAXIMUM NUMBER OF HARDWARE DEVICE CHANGES. ALSO THERE ARE A COUPLE OF FILES WPA.DBL AND WPA.BAK
IF YOU COPY THEM TO A FLOPPY EVEN FROM ANOTHER MACHINE AND THEN TO YOUR WIN DIRECTORY WILL DEFEAT THE TOTALLY USELESS ACTIVATION INCONVENIENCE.
http://www.theeldergeek.co
GET TO KNOW YOUR RECOVERY CONSOLE IT MAY APPEAR TO BE DAUNTING BUT NO PAIN NO GAIN. ALSO GET YOURSELF A COPY OF HIREN'S BOOTCD & BARTS PE WHICH ALLOWS YOU TO BOOT INTO WINXP SO YOU CAN ATTEMPT TO REPAIR YOUR INSTALLED OS.
I NORMALLY DONT POST SO CONSIDER YOURSELF LUCKY.
Business Accounts
Answer for Membership
by: stevenlewisPosted on 2002-07-27 at 06:03:36ID: 7181940
please see here om/default .aspx?scid =kb;en- us; Q314477
http://support.microsoft.c