Forum - DLL-files.com

keith wrote:

> I intensionally deleted the 'hal.dll' while cleaning up my drive and now
> the boot up fails, due to a missing or corrupted hal.dll.
>
> Q. How do I recover my system?
>
> I can get to Recovery Console, select R and selecting Windows operating
> system 1 (the only op sys on my p.c.), but don't know the commands or file
> name on my XP pro disk to copy the correct file to the C:\Windows\System32
> directory.
>
> Can anyone help me recovery from the command promp in recovery console?

I can't imagine why you thought deleting hal.dll would be A Good Thing.
However, from the command prompt in Recovery Console:

Attrib -H -R -S C:\boot.ini [enter]
DEL C:\boot.ini [enter]
to delete the bad one
BootCfg /Rebuild [enter]

to search for Windows installations and make a new boot.ini.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

"keith" <keith@discussions.microsoft.com> wrote in message
news:839A3A9F-B77D-4796-9210-D689965F98D8@microsoft.com...
>I intensionally deleted the 'hal.dll' while cleaning up my drive and now
>the
> boot up fails, due to a missing or corrupted hal.dll.
>
> Q. How do I recover my system?
>
> I can get to Recovery Console, select R and selecting Windows operating
> system 1 (the only op sys on my p.c.), but don't know the commands or file
> name on my XP pro disk to copy the correct file to the C:\Windows\System32
> directory.
>
> Can anyone help me recovery from the command promp in recovery console?
>
> Thanks in anticipation.
>
> Keith

What were you hoping to gain by deleting a file that consumes one millionth
of the average disk size? What other files fell victim to your spring
cleaning? - You will find a number of hal.dll versions in the folder
c:\windows\ServicePackFiles\i386. Their names are hal????.dll. The version
you need is motherboard specific. On my current machine I would need
halacpi.dll but you might need one of the other versions. You probably have
to do the recovery by trial and error: Copy one file after the other to the
System32 folder, rename it to hal.dll, then reboot the machine and watch
what happens.

"Malke" <malke@invalid.invalid> wrote in message
news:u%2345%23ip8JHA.1340@TK2MSFTNGP05.phx.gbl...
> keith wrote:
>
>> I intensionally deleted the 'hal.dll' while cleaning up my drive and now
>> the boot up fails, due to a missing or corrupted hal.dll.
>>
>> Q. How do I recover my system?
>>
>> I can get to Recovery Console, select R and selecting Windows operating
>> system 1 (the only op sys on my p.c.), but don't know the commands or
>> file
>> name on my XP pro disk to copy the correct file to the
>> C:\Windows\System32
>> directory.
>>
>> Can anyone help me recovery from the command promp in recovery console?
>
> I can't imagine why you thought deleting hal.dll would be A Good Thing.
> However, from the command prompt in Recovery Console:
>
> Attrib -H -R -S C:\boot.ini [enter]
> DEL C:\boot.ini [enter]
> to delete the bad one
> BootCfg /Rebuild [enter]
>
> to search for Windows installations and make a new boot.ini.
>
> Malke

Would your recipe recover/restore hal.dll?

Pegasus [MVP] wrote:

> Would your recipe recover/restore hal.dll?

The error message is misleading. hal.dll doesn't need to be restored. The
error really means (to quote the late MVP Alex Nichol) "...happens because
the boot.ini file that tells the boot where to look for 'Windows' is
damaged, so it is looking for files in the wrong place - hal.dll just
happens to be the first one it looks for".

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Tim Meddick wrote:

> Wouldn't the OP need to copy the 'hal.dll' file from either the
> installation CD or (in the case of SP3) the ServicePackFiles\i386 folder
> from within RC first?
>
> Does rebuilding the boot.ini file, using the 'bootcfg' command, somehow
> accomplish this?

The error message is misleading. hal.dll doesn't need to be restored. The
error really means (to quote the late MVP Alex Nichol) "...happens because
the boot.ini file that tells the boot where to look for 'Windows' is
damaged, so it is looking for files in the wrong place - hal.dll just
happens to be the first one it looks for".

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Pegasus

http://www.kellys-korner-xp.com/xp_haldll_missing.htm

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Pegasus [MVP] wrote:
> "Malke" <malke@invalid.invalid> wrote in message
> news:u%2345%23ip8JHA.1340@TK2MSFTNGP05.phx.gbl...
>> keith wrote:
>>
>>> I intensionally deleted the 'hal.dll' while cleaning up my drive
>>> and now the boot up fails, due to a missing or corrupted hal.dll.
>>>
>>> Q. How do I recover my system?
>>>
>>> I can get to Recovery Console, select R and selecting Windows
>>> operating system 1 (the only op sys on my p.c.), but don't know the
>>> commands or file
>>> name on my XP pro disk to copy the correct file to the
>>> C:\Windows\System32
>>> directory.
>>>
>>> Can anyone help me recovery from the command promp in recovery
>>> console?
>>
>> I can't imagine why you thought deleting hal.dll would be A Good
>> Thing. However, from the command prompt in Recovery Console:
>>
>> Attrib -H -R -S C:\boot.ini [enter]
>> DEL C:\boot.ini [enter]
>> to delete the bad one
>> BootCfg /Rebuild [enter]
>>
>> to search for Windows installations and make a new boot.ini.
>>
>> Malke
>
> Would your recipe recover/restore hal.dll?

Keith

http://pcsupport.about.com/od/fixthepro ... haldll.htm


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
keith wrote:
> I intensionally deleted the 'hal.dll' while cleaning up my drive and
> now the boot up fails, due to a missing or corrupted hal.dll.
>
> Q. How do I recover my system?
>
> I can get to Recovery Console, select R and selecting Windows
> operating system 1 (the only op sys on my p.c.), but don't know the
> commands or file name on my XP pro disk to copy the correct file to
> the C:\Windows\System32 directory.
>
> Can anyone help me recovery from the command promp in recovery
> console?
>
> Thanks in anticipation.
>
> Keith

Tim

Malke will probably say the same to me given what I have just posted.

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Tim Meddick wrote:
> (You just said that to Pegasus!!)
>
> Malke,
> I see, so you are working under the impression that the OP
> did NOT delete hal.dll but just THINKS that he did because after doing
> some cleaning up, found that he got the boot.ini inspired error
> message - 'hal.dll missing' ???
>
> Have I got that right?
>
> But the OP seems fairly sure that he actually DID delete the actual
> file 'hal.dll' - should you not have given advice on the assumption
> that what the OP said was true?
>
> Or, at least, asked him for some confirmation and further details?
>
> Perhaps, if he is reading this, he can confirm just what he did?
>
> ==
>
> Cheers, Tim Meddick, Peckham, London.
>
>
>
>
> "Malke" <malke@invalid.invalid> wrote in message
> news:%23yhY$Yq8JHA.5064@TK2MSFTNGP03.phx.gbl...
>> Tim Meddick wrote:
>>
>>> Wouldn't the OP need to copy the 'hal.dll' file from either the
>>> installation CD or (in the case of SP3) the ServicePackFiles\i386
>>> folder
>>> from within RC first?
>>>
>>> Does rebuilding the boot.ini file, using the 'bootcfg' command,
>>> somehow
>>> accomplish this?
>>
>> The error message is misleading. hal.dll doesn't need to be restored.
>> The
>> error really means (to quote the late MVP Alex Nichol) "...happens
>> because
>> the boot.ini file that tells the boot where to look for 'Windows' is
>> damaged, so it is looking for files in the wrong place - hal.dll just
>> happens to be the first one it looks for".
>>
>> Malke
>> --
>> MS-MVP
>> Elephant Boy Computers - Don't Panic!
>> http://www.elephantboycomputers.com/#FAQ

"Tim Meddick" <timmeddick@gawab.com> wrote in message
news:e41RQkq8JHA.5064@TK2MSFTNGP03.phx.gbl...
> (You just said that to Pegasus!!)
>
> Malke,
> I see, so you are working under the impression that the OP did
> NOT delete hal.dll but just THINKS that he did because after doing some
> cleaning up, found that he got the boot.ini inspired error message -
> 'hal.dll missing' ???
>
> Have I got that right?
>
> But the OP seems fairly sure that he actually DID delete the actual file
> 'hal.dll' - should you not have given advice on the assumption that what
> the OP said was true?
>
> Or, at least, asked him for some confirmation and further details?
>
> Perhaps, if he is reading this, he can confirm just what he did?
>
> ==
>
> Cheers, Tim Meddick, Peckham, London.

Well said. I suggest that the OP should go one step further: Check while in
Recovery Console mode that the file c:\windows\system32\hal.dll exists.

keith <keith@discussions.microsoft.com> wrote:

>I intensionally deleted the 'hal.dll' while cleaning up my drive and now the
>boot up fails, due to a missing or corrupted hal.dll.
>
>Q. How do I recover my system?

You're a moron. Let someone else have it.

"Gerry" <gerry@nospam.com> wrote in message
news:u1S6dlq8JHA.1252@TK2MSFTNGP04.phx.gbl...
> Keith
>
> http://pcsupport.about.com/od/fixthepro ... haldll.htm
>
> Hope this helps.
>
> Gerry

This link made me curious: How can a generic hal.dll, as restored from the
WinXP installation CD, replace a hardware-specific / Service Pack-specific
hal.dll, as found in the System32 folder? Well, it doesn't. Tim Fisher, the
author of the article at that link, says that the job is rated "Easy" and
should take 15 minutes. Neither is true. The job is not easy (unless you are
an expert) and it takes considerably more than 15 minutes. Since I'm a
glutton for punishment, I tried his recipe for myself.

After using the generic hal.dll recommended by Tim Fisher, the machine
booted into a very basic mode. It had forgotten about *all* the PC-specific
hardware: Motherboard, disk controller, display adapter, display settings,
network adapter, sound adapter, mouse, Service Pack, you name it, it had
forgotten about them. Some it was able to install automatically; for others
it demanded driver CDs. The IP settings defaulted to DHCP, which is not at
all what I need. And worse as well: System Restore would not touch the
restored hal.dll file.

It seems that Tim Fisher's recipe will allow the OP to boot up his PC but he
would have his work cut out in restoring it to a fully functional condition.
Conversely, if he found the correct hal.dll in his Service Pack folder then
he would land on his feet straight away.