Shulou(Shulou.com)06/01 Report--

This article mainly introduces what causes the loss of hal.dll. It has certain reference value, and friends who need it can refer to it. Let's take a look at it with me.

A customer's machine does not connect to the monitor remotely, a prompt that hal.dll is lost and check the Internet.

Hal.dll is a Windows hardware extraction layer module. After booting, the system cannot enter. There is an error prompt: please reinstall the copy of the above files: windwos root\ system32\ hal.dll

Generally speaking, there are two reasons for this:

There is something wrong with the boot.ini boot.ini file; due to the current one-click restore, dwarf boot.ini or multiple systems will change the boot.ini file. In fact, the solution is also very simple, in this case, you can actually enter the safe mode. Go into safe mode, restore boot.ini to its normal (or previous) state, and OK!

Note: it is also possible that you have a brand machine, and many brand machines have a hidden partition. If you use a GhostXP installation disk, such as the computer company Special Edition 7.8, the recovered boot.ini files certainly do not match your machine! After installing the system in this way, the first automatic restart can successfully enter the system, and then reboot will prompt hal.dll to be lost, this is because the boot.ini file tries to boot the system through the first partition of the first hard disk, but due to the existence of hidden partitions, the system we installed is in the second partition (the first partition is not visible)! If the brand machine has not re-partitioned the hard drive, you must manually modify the boot.ini file after installing the Ghost system, otherwise it will make an error!

A typical boot.ini usually looks like this:

[boot loader]

Timeout=30

Default=multi (0) disk (0) rdisk (0) partition (1)\ WINDOWS / / rdisk (0) refers to the first physical hard disk partition (1) refers to the first partition

[operating systems]

Multi (0) disk (0) rdisk (0) partition (1) / / rdisk (0) refers to the first physical hard disk partition (1) refers to the first partition\ WINDOWS= "Microsoft Windows XP Professional" / noexecute=optin / fastdetect

Modify your BOOT.INI to change partition (1) to partition (2). Don't just change one! See clearly there are two partition (1) inside.

2. The version of the hal.dll file is incorrect or missing.

Because different computers correspond to different hal.dll files, but the current ghost systems are often misjudged, resulting in hal.dll files are not consistent with the reality. Hal.dll files and corresponding computer types: acpi multiprocessor pc halmacpi.dl_; acpi uniprocessor pc halaacpi.dl_; advanced configuration and power interface (acpi) pc halacpi.dl_; mps multiprocessor pc halmaps.dl_; mps unitprocessor pc halapic.dl_ standard pc hal.dl_; compaq systempro multiprcessor or 100% compatible halsp.dl_. This can be seen through the device Manager's computer project, or look at the hal.dll version information. If the system cannot be accessed, it is impossible to know which type it is. Can be tested one by one, which can be started is which ^ _ ^ (stupid method)

Solution:

(1) copy the system / hidden files under the root directory of C: disk from other machines and copy them to the problem machine (you can boot the system by DOS boot disk or WinPE boot system) this method is suitable for power outages, crashes and other abnormal shutdown caused by unable to boot the system, then only the boot file under the root directory of the boot area is lost, and the hal.dll file is not a problem.

(2) insert the XP installation disk to restart the computer and select the recovery console. Follow the prompt to enter the winnt directory.

At the DOS prompt, enter: expand x:\ i386\ driver.cab / f:hal.dll c:\ windows\ system32\ (x: is the CD drive letter. Once again, use expand to copy halaacpi.dll to c:\ winindows\ system32\, rename it to hal.dll, restart the computer, and then copy halacpi.dll (because the source file name of hal.dll is halacpi.dll). Restart after renaming (ren), and then restart

Or try to enter safe mode and then extract the file corresponding to the file

These are the details of what caused the loss of hal.dll, and whether there is any gain after reading it? If you want to know more about it, welcome to the industry information!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.