problem when loading windows setup from cd (halaacpi.dll)

[NuVanDibe]

(halaacpi.dll or halacpi.dll or something like it) could not be loaded. the error code is 4. press any key to reset.

Anyone know what could be causing this? I went and made a fresh root dir and a fresh winnt.sif file, billboard, and copied my \INSTALL AND \$OEM$ directories into it. Still gives me the same error message. Never gave me the error before, and I'm copying from the exact same backup ISO of my windows cd.

=edit=

this is after the [setup is checking your system configuration] and before the partition select screens.

Edited April 8, 2006 by NuVanDibe

[dirtwarrior]

(halaacpi.dll or halacpi.dll or something like it) could not be loaded. the error code is 4. press any key to reset.

Anyone know what could be causing this? I went and made a fresh root dir and a fresh winnt.sif file, billboard, and copied my \INSTALL AND \$OEM$ directories into it. Still gives me the same error message. Never gave me the error before, and I'm copying from the exact same backup ISO of my windows cd.

=edit=

this is after the [setup is checking your system configuration] and before the partition select screens.

BUMP I am having this issue also with my new iso of windows 2000. I looked in the cd and halacpi.dll is in there but installation halts. Any ideas?

[cluberti]

From what you've posted, it sounds like Windows is complaining that the file cannot be loaded due to it either not being there, or being corrupted. If you press F5 when you see the "Press F6..." text along the bottom, and choose the "Standard PC" option, does the installation continue properly from that point?

[dirtwarrior]

I will try that thanks. What does this dll do?

[IcemanND]

That dll is the HAL that is loaded on the machine. It will be renamed to HAL.DLL.

[cluberti]

Pressing F5 and choosing "Standard PC" will get the setup to load the file hal.dll as the hal, rather than the hal it has determined you need (halaacpi.dll). Using the "Standard PC" option isn't necessarily a good choice long term (no acpi or apm support, so no power management, for starters), but it will be a good test to see if the disk installs otherwise. If that works, then it is indeed a problem with the file on the CD - if it fails, it could be something else innocuous like a BIOS setting (or even a BIOS update), or a piece of hardware it doesn't like, etc. I'm still leaning towards the CD itself having the issue, but I never rule out hardware, especially on older machines. That's why I suggested this test - it should tell us which is the culprit.

[dirtwarrior]

Thanks guys. You all are the best.