Can I copy a different boot.ini file into/over what appears to be a bad/dorked boot.ini file
and get away clean?  The OS is WinXPpro SP3.

I am working a C2D PC that thinks it only has one core operational. Yes, the DM/Computer indicates the HAL is a 'uni-processor' PC. CPUZ confirms. OK, the HAL is wrong. Fine. Later.... :( Yes, I'm told that I can use the F5 key to suggest a HAL during an OS Update! Not there yet! BTW, this PC is one of 3 identical C2D PCs build in 2008. The other two are fine.

So, I go back to one of Greg's shares about the boot.ini file. I find that the two working PCs have matching boot.ini files. Only this troubled PC' boot.ini file is different/dorked up.

This boot.ini boots to a black screen that lets me select an OS to boot from. They are:

Bottom Choice: <hy-lited> Windows (default)
This choice boots to another Black Screen: "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."

Odd because the file called out is present.

Top Choice: Windows (default)    [the one I use ATM!]
This choice boots to the normal WinXP Logon Screen; and, on to the old working desktop.

Thoughts/suggestions/opinions?
Duncan

Reply via email to