Member Avatar for Rick_in_CT

On a HP A610N Computer:
After using the HP Recovery CDs, that were built from this computer, the following error was displayed:

Windows could not start because the following file is missing or corrupt:
Windows\System32\Hal.dll

I read the MS Bulletin about the boot.ini. I used my BartsPE boot disk to make a backup of the boot.ini, and edited several settings.

Here is a good boot.ini: (also from a HP Computer)
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Media Center Edition" /noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

The bad PC’s boot.ini was the same except the following:
“partition(1)\WINDOWS”, and had XP Home edition.


I changed the boot.ini, and the boot up error changed slightly.

This computer was working fine, but I am giving this computer to a friend, and wanted to put it back to when I created the HP Recovery CDs. (what a mistake!)

I have run the “on board” HP Recovery, and the HP Recovery that I built from the CDs several times. I have tried the destructive, and non-destructive methods, both with the same results.

It seems like the HP Recovery is not updating the computer to fix the problem. Using my BartsPE boot CD, should I delete everything on the C: Drive, and run the HP Recovery again?:sad:

  • 2 Contributors
  • 1 Reply
  • 233 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by vikonava

Dani AI

Generated

Follow-up note for : the symptom set you describe (HP recovery runs but the machine still won’t boot, and editing boot.ini changed the behaviour) points at a boot/partition-mapping or boot-sector problem more often than a simple missing file. ’s suggestion to use the Windows Recovery Console is the right, non‑destructive first step before any full wipe.

Recommended Recovery Console sequence (boot from the XP CD or a recovery environment, choose Repair and open the console) — run these in order:

chkdsk c: /r
fixmbr
fixboot c:
bootcfg /rebuild
  • chkdsk c: /r checks for and repairs filesystem errors and bad sectors that can leave files unreadable.
  • fixmbr repairs the master boot record if it is damaged.
  • fixboot rewrites the partition boot sector.
  • bootcfg /rebuild scans for Windows installs and recreates a correct boot.ini (this avoids manual partition-number guesses).

Use BartPE (which you already have) to confirm which partition actually contains the Windows folder before doing destructive work: from BartPE’s command prompt run dir C:\Windows, dir D:\Windows, etc., until the real Windows install is found. Also check that the partition containing \Windows is the active/boot partition. While in BartPE, verify C:\Windows\system32\hal.dll exists and looks reasonable (size/date). Copying a HAL from the wrong source can create an incompatible HAL mismatch, so avoid blind file swaps.

Do not delete C: as the first move. Image the disk first (Ghost/Clonezilla), run the HDD manufacturer’s diagnostics, and verify the recovery discs (reburn at low speed or request replacement media) before a full wipe. If Recovery Console and partition fixes fail, a clean install from original XP media or replacement HP recovery media is the reliable fallback.

Member Avatar for vikonava

i suppose you can get a windows xp cd and get to boot from the cd then select instead of installing, the Windows Repair thingy and it will open DOS for you, in there type HELP and look for a command called BOOTFIX or FIXBOOT something like that, youll need just to know the command name and execute it

:) hope this works, it has worked when i ruin my boot because of installing and managing dualboots :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.