| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Anwylyd Al'Vos
Minmatar LightSpeed Industries
|
Posted - 2007.12.07 21:44:00 -
[1]
Sry all, I have read a lot of the the 75+ page whine about this, but I'm having this specific issue, and can't find any helpful references:
I was one of the few that patched and went to bed thus having my boot.ini erased before ccp acknowledged the issue.
When I boot I also get "the following file is missing or corrupt: <windows> /system32/hal.dll"
I find my windows xp install disk and restart.
f12 takes me to boot options and I tell me comp to boot from cd
I get to the install/repair blue scrren, hit R and it tells me windows cannot find my hard drive.
f3 reboot, f12 boot options, and go to my utility partition. I run a full system scan and it not only find all of my hardware, but there are no issues found.
Repair disk still doesn't find my hard drive, how do I fix this without spending $150-250 for a repair guy to help me out? If it's even possible. My hd is SATA btw. _ . - Justice, Mercy, and Faith My soul has horizons further away than those of early mornings, deeper darkness than the night |

Miss Anthropy
School of Applied Knowledge
|
Posted - 2007.12.07 22:19:00 -
[2]
Hmmmm, do you have any old bootdisks? That you could boot into DOS with? Technically you should be able to copy the file from the Windows CD into the c:\Windows\System directory. I did something similar years and years ago (back when Win 98 allowed you to boot up into DOS without needing boot disks).
I'm sure the DOS nerds here will be able to help you more (I remember very few DOS commands). You should be able to find the DOS commands for copying files pretty easy via Google I guess.
This is the only way I can think of to solve the issue bar formatting your drive and reinstalling Windows. The problem is, this file might not be on the CD (it may have been installed through some other software), so you may be looking at a format after all.
I hereby declare this thread as being satisfactorily trolled. |

Stickleback
|
Posted - 2007.12.07 22:39:00 -
[3]
This may well be caused by boot.ini rather than hal.dll, despite what it says.
As for it not recognising your drive, you probably need to load a driver before you get to recovery console. At some point during the process of getting to recovery console it should say at the bottom of the screen to press F6 if you need to load a driver (this may be very briefly flashed up so you'll have to be quick). You'll need to find this from the website of your mobo manufacturer, stick it on a floppy and give it a go.
If it does work, then try the repair process to see if it fixes the boot.ini problem. Shout if it doesn't work and we'll try something else.
|

Anwylyd Al'Vos
Minmatar LightSpeed Industries
|
Posted - 2007.12.07 23:04:00 -
[4]
Heh, well, don't have a floppy drive... I have a driver cd that has a copy of my utility partition on it as well as a virtual dos engine as if run through win 98... _ . - Justice, Mercy, and Faith My soul has horizons further away than those of early mornings, deeper darkness than the night |

Miss Anthropy
School of Applied Knowledge
|
Posted - 2007.12.08 00:24:00 -
[5]
Originally by: Anwylyd Al'Vos Edited by: Anwylyd Al''Vos on 07/12/2007 23:20:49 Edited by: Anwylyd Al''Vos on 07/12/2007 23:14:33 edit: thanks guys, your clues led me to a solution... we'll see if it's successful in a bit :)
edit2: I am up and running guys, thanks a ton!
I'm a genius really aren't I?
I hereby declare this thread as being satisfactorily trolled. |

Chainsaw Plankton
IDLE GUNS
|
Posted - 2007.12.08 02:03:00 -
[6]
i suppose having that ubuntu install disk around would have been handy had i not fixed the boot.ini before shutting down (then again i haven't actually restarted yet)
|

Bubba1977
Amarr Repo Industries
|
Posted - 2007.12.08 13:51:00 -
[7]
Originally by: Anwylyd Al'Vos Sry all, I have read a lot of the the 75+ page whine about this, but I'm having this specific issue, and can't find any helpful references:
I was one of the few that patched and went to bed thus having my boot.ini erased before ccp acknowledged the issue.
When I boot I also get "the following file is missing or corrupt: <windows> /system32/hal.dll"
I find my windows xp install disk and restart.
f12 takes me to boot options and I tell me comp to boot from cd
I get to the install/repair blue scrren, hit R and it tells me windows cannot find my hard drive.
f3 reboot, f12 boot options, and go to my utility partition. I run a full system scan and it not only find all of my hardware, but there are no issues found.
Repair disk still doesn't find my hard drive, how do I fix this without spending $150-250 for a repair guy to help me out? If it's even possible. My hd is SATA btw.
I had the same exact problem initially, so i made a floopy boot disk with a boot.ini, ntdetect.com, and ntldr file on it as well as a copy of hal.dll from my laptop. I booted the comp from the disk and figured since the error message said i was missing my hal.dll file, i copied the hal.dll from the boot disk into my windows folder. Also copied my boot.ini, ntdetect.com and ntdlr files into my c:\ directory.
The result was a F****D computer....some sort of kernel error. Apparantly, the hal.dll did not match with my os install since my laptop was service pack 1 and my main comp was service pack 2. So now i had to reinstall my os. FUN!
Bottom line, just put a boot.ini file into your c:\ directory and you should be fine. DO NOT mess with your hal.dll file under any circumstances!
|

Xeios
Caldari Sniggerdly Pandemic Legion
|
Posted - 2007.12.08 14:59:00 -
[8]
You can rebuild the boot.ini in the windows repair console.
Boot from your windows disk and when prompted select repair.
You will enter the repair console. Then type bootcfg it will give you a list of commands. just to be safe use, bootcfg /scan. this will return all installations. after this type bootcfg /rebuild and select the windows installation you want to do it for.
Thats basically it, theres a couple of other options i think but that was like 2 days ago so the alcohol has already erased it from my mind.
|

Anwylyd Al'Vos
Minmatar LightSpeed Industries
|
Posted - 2007.12.09 00:52:00 -
[9]
Just so people know, the hal.dll error is a false error if you're getting it.
If your windows repair disk isn't recognizing your hard drive check to see if you have a SATA drive. If so, in your bios it prolly has something like ACHI mode on, change it to something else and it should recognize your hd now.
Now follow microsoft's instructions for using the recovery disk to create an new boot.ini file.
*** Once complete go back to your bios and change the hd setting back to the ACHI thing, reboot and windows should be back, otherwise you'll get a blue screen of death *** _ . - Justice, Mercy, and Faith My soul has horizons further away than those of early mornings, deeper darkness than the night |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |