The Hal. dll is missing.
There are three possibilities for such a problem.
I. The Hal. dll file is indeed lost.
When the system prompts that the file is lost, find the PE and open the c: \ windows \ system32 \ directory. This file is missing. This may be caused by accidental file deletion or antivirus, it may also be caused by abnormal shutdown. This method is relatively simple. Just copy the file with the same name on another machine. Of course, if it is caused by a serious virus, it can be useful. At that time, we can only re-build the system.
II. The Hal. dll file is not lost, and the size is the same as that on other machines.
When the system starts up, it prompts that the file is lost. If you find that the file is not lost when you access the PE disk, there are two possibilities: generally compatible machines and only one master partition machine, it is probably caused by hardware. The main suspect is the memory. Find other memory plug-in tests. If there is a memory problem, you can normally enter the system after plugging in the correct memory. Remember, do not copy this file at this time. If you copy this file, other files will be lost. If the memory cannot be started, copy the file and prompt other file errors. You can also consider the virus. Press F8 at startup, select the last correct configuration, and then go to the system for antivirus, if you cannot enter the system, reinstall it.
3. There is also a situation where some brand-name machines have two primary partitions, such as Dell machines, with a hidden primary partition of MB. After installing earlier ghost XP versions, you will be prompted that the Hal. dll file is lost. This may happen after someone cleans up the C drive file. This is related to boot. ini. Open boot. ini on a normal machine and check the following content:
[Boot loader]
Timeout = 3
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"/noexecute = optin/fastdetect
No. Disk (0) rdsk (0) Partition (1) means the system with disk 0 partition 1 is started.
Therefore, a brand machine with two primary partitions will prompt Hal if startup fails. when the DLL is lost, you only need to enter PE to change the hidden file boot in the C drive root directory. the INI content is good, that is, change partition 1 to partition 2. After the change is completed, you can directly copy the following content to your boot. ini
[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 = "Microsoft Windows XP Professional"/noexecute = optin/fastdetect
Restart your computer after modification. You will find that the problem has been solved. Remember not to delete this file any more.
Note: If this problem occurs in my DLL 640m, the third solution is used.