Printable View
If you have a floppy drive, copy the following files from the root of your hard drive to a floppy. When you boot the floppy, Windows will load from your Windows folder on the hard drive. The files are: ntldr, ntdetect.com, boot.ini. Now you have an emergency boot floppy that will work if the windows folder on the hard drive is OK.
dell went through very little, and they said to have me reformat the drive...
Do you have data on there you need to recover? Or is formatting an option afterall?
sorry for the late post, but dell had no other solution besides reinstall of windows...
i did a check for hal.dll and boot.ini, and there is a fix on microsofts site....my pc is running fine.
You should tell Dell how to fix this problem so they can give more constructive advice the next time someone calls them!
If dell doesn't want to accept the hard drive. Do it youself. What brand is it?
OK.....
this is the error message
this is the fixCode:Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file
I just went through hell and back again with a Dell Dimension 2400 on WinXP SP2 Homey Edition.Code:Bootcfg /rebuild
I managed to save the day using above command ;)
FIXBOOT doesn't do diddly :(
I did walk through of FIXMBR, but didn't follow through b/c I know Dell has a proprietary FAT16 partition of ~30MB as 1st partition.
If you are swift - you'll notice an ERROR message FLASH UPON THE SCREEN just prior to the error above...and it has to do with the BOOT.INI file.
So I Pause/Break key the screen to stop it and read (just at the right time, mind you) to see the BOOT.INI error message (can't recall exactly, but something like "No Boot.ini file found")
After booting from Orig Dell XP SP1 CDROM (set BIOS to Boot from CDROM as 1st boot device)
I had previously EXPANDED Hal.dll from XP CDROM
D:\i386\HAL.DL_ C:\WINDOWS\SYSTEM32
no good - I mean it copied over but that didn't do any good, so I tried FIXBOOT C: ......no go
BTW - guess what - there's no EDIT command from Recovery Console....and the usual DOS like commands don't work either
For ex;
CD\ in a CMD window, while in windows, takes you to ROOT - but
CD \ is necessary from the Recovery Console (XP CDROM - I later found out RC has it's own different command interpretor)
there are many others I can list - but atleast DOSKEY is installed as default ;) (DIR desn't require [/p /o:n] etc to be useful - also recycling through previous commands is a snap)
It's a NIGHTMARE - but can be done
IIRC (and it's a bit foggy now, after awakening from one :p )
Boot from XP CDROM
choose R for Repair
let winblows load all it's crud (which takes 5000 yrs longer than on 98)
type in 1 hit ENTER (make sure NumLock is engaged - it wasn't on this Dell POS :eek:
(obviously when "1" is C:\WINDOWS and your only choice)
then hit ENTER when presented with the ever-loving-$hit-of "Enter Admin Password" (do NOT type anything, just hit the ENTER key)
Now you're at a C:\WINDOWS prompt (hopefully..and if so - you CAN repair this - BTW - What a DUMP!....sorry, just had to digress for a moment :) )
...so BOOTCFG /?..or even BOOTCFG yields the menu options - one is SCAN (who cares) the IMPORTANT one is rebuild
I did NOT have another working PC at my location of incident, and I recalled "HOW" a typical BOOT.INI file should kinda look, but not exactly ...so
I fixed it wth some munging during the process and repaired the BOOT.INI file to pristine state once I got onlne again and found these MS articles (which contain errors BTW)
http://support.microsoft.com/default...b;EN-US;289022
and http://support.microsoft.com/default...b;en-us;291980Quote:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
....all I messed up was the [/fastdetect] crud on the 2nd question ("Enter Operating System Load Options:") presented -- (I inserted [Timeout:30] by mistake, instead of /fastdetect)Quote:
The bootcfg /rebuild command scans the hard disks of the computer for Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays the results. You can add the detected Windows installations.
You may receive a message that is similar to the following message:
Total Identified Windows Installs: 2
[1] C:\Windows
Add installation to boot list? (Yes/No/All):
Enter Load Identifier: (Custom description for an operating system loading from the Boot menu)
Enter Operating System Load Options: (that is: /fastdetect)
- the 1st question ("Enter Load Identifier:") really just asks for what you'd like to see upon boot (ala "WinBlows XP Homey Edition")
....so - switch to C: to see the results (use DIR, and use TYPE BOOT.INI)..that's the other thing -- can't use C:\ - gots to use C: only :(
BUT - in the CMD window (after WINBLOWS is loaded and utilizing wowexec.exe and ntvdm.exe) - all old DOS commands work well
ALL in ALL -- XP .....=== WHAT A DUMP! :D
*edit
BTW - I did a search on SHARKYs for HAL.DLL and BOOT.INI and replied with a link to this response :D
Quote:
Originally posted by I4one
O
*edit
BTW - I did a search on SHARKYs for HAL.DLL and BOOT.INI and replied with a link to this response :D
Does Microsoft have a reason as to why this problem occurs?
I really have no idea what MS has to say about it - if anything....
I can speculate somewhat;
This 'seems' to occur, from what few cases I've seen, mostly when there's a "hidden" FAT (or other type) partition located on the HDD, at the beginning of the Drive. That's what Dell's consumer line (2400 Dimension, etc) does. They give an XP CDROM, but it's a Dell OEM and specifically designed to only work on their boxes...while the CDROM likely has a Full XP version on it - it is not a Full Retail ver, nor can I say it's "just-like" other OEM versions (the idea of OEM is to customize the Setup, for both proprietary specific Hardware and Piracy-prevention reasons).
- and while this scheme isn't NEARLY as BAD as a Disk Image only ver of the OS (like Comcrud/HP and many other OEMs do nowadays) - it has it's flaws, and annoyances. One being that the BOOT.INI file points to partition(2) instead of (1) as in;
------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
-------------------
because the small FAT partition resides at (1)
Run Disk Management (or Startup and Recovery Tab) - you can see the FAT partition, but can't really get any good info on it, other than size - the Toolbar changes the options/chooices when you select it - and it doesn't even have a name.
Before I started on my recovery journey - I had viewed the BOOT.INI file though My Computer | Properties | Startup and Recovery ?? oh...I forget ...but you know - where you can EDIT the BOOT.INI file directly
BUT
BOOT.INI did NOT exist - yet the box was booting and rebooting regularly as I was uninstalling typical OEM bloat software, and no error messages or anything upon POST - go figure
So I started monkeying around in there (I think I unticked or ticked the default TiMEOUT boxes crud that's there) after the bloat uninstalls, and that's when I got hit with the "INVALID Boot.ini file" which flashes only for a split second and then - boom - the <windowsroot>\system32\hal.dll error appears and sits there tauntiing you - and daring you to try and fix it -- which I did eventually, BTW(see excursion details above) - without losing any data or anything :D
just remember - MS Mystery = MS Misery :eek:
*just to recap from above;
BOOTCFG /list will list all installed versions of OS (or winblows)
BOOTCFG /? or BOOTCFG or
HELP will list all available BOOTCFG switches/parameters available
and most importantly
BOOTCFG /rebuild will rebuild the Boot.ini file and you can view the contents only using the
TYPE BOOT.INI command, once it's rebuilt
BTW - anyone know how to actually EDIT the BOOT.INI file when in Recovery Console -- the EDIT command seems to be NON-EXISTENT - if you type HELP at any prompt in Recovery Console , you'll see all the available commands - and there's no EDIT command
This is a major oversight and most of the reason why the RC isn't as helpful as it could be. I'm sure you've noticed that even if you have an executable available on disk, you cannot run it.Quote:
Originally posted by I4one
BTW - anyone know how to actually EDIT the BOOT.INI file when in Recovery Console -- the EDIT command seems to be NON-EXISTENT - if you type HELP at any prompt in Recovery Console , you'll see all the available commands - and there's no EDIT command
This is what set off my search a while ago for a boot CD that can see NTFS partitions just like an old DOS environment.
ahhhh....I recall that thread rock
hmm - a thought occurs -
HEADLINE
"MS locks out Front End Owners
/ leaves back door holes wide enough for a semi to drive through" :eek:
I should have known..ugh!
No Prob - I guess I'll be building a Bart PE disk and/or getting more comfortable using my Knoppix LiveCD :D
OHHH!!
some Good news though (well somewhat) - remember (as Russell will) when I said that I couldn't get the dang Recovery Console installed on a XP SP2 system (using the Dell orig XP SP1 CD). Well, I eventually did in my previous escapade..IIRC, I had to make sure I was in root C:\ (can't run WINNT.EXE from CDROM)....anyway, I think the correct same command worked from C:\ [Copy D:\i386\winnt.exe /cmdcons]
....so it worked -- but what's the benefit ?? I though maybe I could use Recovery Console in a GUI or similar.
Also;
Check out these articles - for allowing permissions in RC -- I have to re-read them myself
http://www.amset.info/windows/console.asp
and http://www.amset.info/windows/policy.asp
Quote:
Recovery Console - Allow Floppy Copy and Access to all drives and folders. If you have installed the recovery console, then you need to make this change before the recovery console needs to be used. It will give you access to the entire machine should you need to use the recovery console.
Computer Configuration | Windows Settings | Security Settings | Security Options | Recovery Console | Allow Floppy Copy and Access to all drives and folders