"Tim Meddick" <timmeddick@gawab.com> wrote in message
news:eDEsZhr8JHA.1340@TK2MSFTNGP05.phx.gbl...
>I think there is a valid place for URL links to help- pages in these posts.
>
> However, some of the time, it looks very like laziness that's going on,
> rather than to be concise.
>
> I don't see why, when replying a query, people can't just answer the
> question themselves.
>
> Perhaps it might make people feel more responsible for their advice than
> just posting a URL of another's work.
>
> Not criticizing another's original works, but one may not realize that
> advice was not relevant to a question, having not written it one's self.
>
> ==
>
> Cheers, Tim Meddick, Peckham, London.
While I see what you're getting at within the context of the current thread,
I do not agree with you on this occasion. I find that there is a vast amount
of information available on how to trouble-shoot Windows problems and it is
simply not feasible to test every recipe quoted in some link, especially
when it is as authoritative and well-written as this one. Quite often the
quoted article is correct and allows the poster to fix his problem. I feel
that Gerry gave an excellent answer that was highly relevant. It is not is
fault that the article he quoted is superficial and I would not have
expected him to perform the same test as I did. It takes courage and
perseverance to deliberately wreck, then repair one's own machine!
missing or corrupted hal.dll file
Moderators: DllAdmin, DLLADMIN ONLY
Re: missing or corrupted hal.dll file
Pegasus
I agree that using the Recovery Console is not easy. My first thought
was to replace hal.dll from the backup copy on the hard drive. I used
the link because it had clear instructions on using the Expand
command.in the Recovery Console.
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> "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.
I agree that using the Recovery Console is not easy. My first thought
was to replace hal.dll from the backup copy on the hard drive. I used
the link because it had clear instructions on using the Expand
command.in the Recovery Console.
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> "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.
-
- Posts: 59
- Joined: 22 Mar 2009, 00:00
Re: missing or corrupted hal.dll file
"Gerry" <gerry@nospam.com> wrote in message
news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
> Pegasus
>
> I agree that using the Recovery Console is not easy. My first thought was
> to replace hal.dll from the backup copy on the hard drive. I used the link
> because it had clear instructions on using the Expand command.in the
> Recovery Console.
If you have a backup copy of the System32 folder then this strategy would be
your best option. See also my reply to Tim Meddick.
news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
> Pegasus
>
> I agree that using the Recovery Console is not easy. My first thought was
> to replace hal.dll from the backup copy on the hard drive. I used the link
> because it had clear instructions on using the Expand command.in the
> Recovery Console.
If you have a backup copy of the System32 folder then this strategy would be
your best option. See also my reply to Tim Meddick.
Re: missing or corrupted hal.dll file
Pegasus
When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
folder was placed at c:\windows\drivercache\i386\sp3.cab
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> "Gerry" <gerry@nospam.com> wrote in message
> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>> Pegasus
>>
>> I agree that using the Recovery Console is not easy. My first
>> thought was to replace hal.dll from the backup copy on the hard
>> drive. I used the link because it had clear instructions on using
>> the Expand command.in the Recovery Console.
>
> If you have a backup copy of the System32 folder then this strategy
> would be your best option. See also my reply to Tim Meddick.
When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
folder was placed at c:\windows\drivercache\i386\sp3.cab
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> "Gerry" <gerry@nospam.com> wrote in message
> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>> Pegasus
>>
>> I agree that using the Recovery Console is not easy. My first
>> thought was to replace hal.dll from the backup copy on the hard
>> drive. I used the link because it had clear instructions on using
>> the Expand command.in the Recovery Console.
>
> If you have a backup copy of the System32 folder then this strategy
> would be your best option. See also my reply to Tim Meddick.
-
- Posts: 59
- Joined: 22 Mar 2009, 00:00
Re: missing or corrupted hal.dll file
Indeed, but the OP would have to extract halxxx.dll from this cab file.
Remember - his machine does not boot and I suspect that he cannot extract
files from a cab file while in the Recovery Console.
"Gerry" <gerry@nospam.com> wrote in message
news:e8bDL9r8JHA.4176@TK2MSFTNGP02.phx.gbl...
> Pegasus
>
> When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
> folder was placed at c:\windows\drivercache\i386\sp3.cab
>
> --
>
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> Pegasus [MVP] wrote:
>> "Gerry" <gerry@nospam.com> wrote in message
>> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>>> Pegasus
>>>
>>> I agree that using the Recovery Console is not easy. My first
>>> thought was to replace hal.dll from the backup copy on the hard
>>> drive. I used the link because it had clear instructions on using
>>> the Expand command.in the Recovery Console.
>>
>> If you have a backup copy of the System32 folder then this strategy
>> would be your best option. See also my reply to Tim Meddick.
>
Remember - his machine does not boot and I suspect that he cannot extract
files from a cab file while in the Recovery Console.
"Gerry" <gerry@nospam.com> wrote in message
news:e8bDL9r8JHA.4176@TK2MSFTNGP02.phx.gbl...
> Pegasus
>
> When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
> folder was placed at c:\windows\drivercache\i386\sp3.cab
>
> --
>
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> Pegasus [MVP] wrote:
>> "Gerry" <gerry@nospam.com> wrote in message
>> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>>> Pegasus
>>>
>>> I agree that using the Recovery Console is not easy. My first
>>> thought was to replace hal.dll from the backup copy on the hard
>>> drive. I used the link because it had clear instructions on using
>>> the Expand command.in the Recovery Console.
>>
>> If you have a backup copy of the System32 folder then this strategy
>> would be your best option. See also my reply to Tim Meddick.
>
Re: missing or corrupted hal.dll file
Pegasus
Expand
Extracts a file from a compressed file.
Source: http://technet.microsoft.com/en-us/libr ... S.10).aspx
http://technet.microsoft.com/en-us/libr ... .aspx#EBAA
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> Indeed, but the OP would have to extract halxxx.dll from this cab
> file. Remember - his machine does not boot and I suspect that he
> cannot extract files from a cab file while in the Recovery Console.
>
>
> "Gerry" <gerry@nospam.com> wrote in message
> news:e8bDL9r8JHA.4176@TK2MSFTNGP02.phx.gbl...
>> Pegasus
>>
>> When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
>> folder was placed at c:\windows\drivercache\i386\sp3.cab
>>
>> --
>>
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>>
>> Pegasus [MVP] wrote:
>>> "Gerry" <gerry@nospam.com> wrote in message
>>> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>>>> Pegasus
>>>>
>>>> I agree that using the Recovery Console is not easy. My first
>>>> thought was to replace hal.dll from the backup copy on the hard
>>>> drive. I used the link because it had clear instructions on using
>>>> the Expand command.in the Recovery Console.
>>>
>>> If you have a backup copy of the System32 folder then this strategy
>>> would be your best option. See also my reply to Tim Meddick.
Expand
Extracts a file from a compressed file.
Source: http://technet.microsoft.com/en-us/libr ... S.10).aspx
http://technet.microsoft.com/en-us/libr ... .aspx#EBAA
--
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Pegasus [MVP] wrote:
> Indeed, but the OP would have to extract halxxx.dll from this cab
> file. Remember - his machine does not boot and I suspect that he
> cannot extract files from a cab file while in the Recovery Console.
>
>
> "Gerry" <gerry@nospam.com> wrote in message
> news:e8bDL9r8JHA.4176@TK2MSFTNGP02.phx.gbl...
>> Pegasus
>>
>> When I last installed Windows XP with a new SP3 OEM disk an SP3 cab
>> folder was placed at c:\windows\drivercache\i386\sp3.cab
>>
>> --
>>
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>>
>> Pegasus [MVP] wrote:
>>> "Gerry" <gerry@nospam.com> wrote in message
>>> news:upvBbxr8JHA.1252@TK2MSFTNGP04.phx.gbl...
>>>> Pegasus
>>>>
>>>> I agree that using the Recovery Console is not easy. My first
>>>> thought was to replace hal.dll from the backup copy on the hard
>>>> drive. I used the link because it had clear instructions on using
>>>> the Expand command.in the Recovery Console.
>>>
>>> If you have a backup copy of the System32 folder then this strategy
>>> would be your best option. See also my reply to Tim Meddick.
-
- Posts: 59
- Joined: 22 Mar 2009, 00:00
Re: missing or corrupted hal.dll file
"Gerry" <gerry@nospam.com> wrote in message
news:umfp$Ss8JHA.2120@TK2MSFTNGP02.phx.gbl...
> Pegasus
>
> Expand
> Extracts a file from a compressed file.
> Source: http://technet.microsoft.com/en-us/libr ... S.10).aspx
>
> http://technet.microsoft.com/en-us/libr ... .aspx#EBAA
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
OK, I'm wrong, there is an "expand" command available under the Recovery
Console.
news:umfp$Ss8JHA.2120@TK2MSFTNGP02.phx.gbl...
> Pegasus
>
> Expand
> Extracts a file from a compressed file.
> Source: http://technet.microsoft.com/en-us/libr ... S.10).aspx
>
> http://technet.microsoft.com/en-us/libr ... .aspx#EBAA
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
OK, I'm wrong, there is an "expand" command available under the Recovery
Console.