Yeah, I think the last time I had to deal with it was when I was in the BIOS and changed the hard drive controller from SATA to AHCI. Something distracted me (a phone call, or something) and I was getting ready to go out anyway, so just shut the computer down instead of rebooting.
The next day I got the hal.dll error, but had forgotten that I changed the BIOS, and had no idea what to do!
After much Googling with a different computer, I remembered the change I had made, went into the BIOS and changed it back, rebooted and Windows started normally.
rogerX
--- In simplycomputers2@yahoogroups.com, B Welkin <welkinator@...> wrote:
>
> Hi,
>
> I have encountered this error a time or two in the past and each time
> it was a major PITA. The hal.dll file is different for different
> systems to start with. Here is a quote of what Wikipedia says about
> this file. My suggestion is to copy off desired files, format and
> reinstall. Bear in mind that this is a solution I almost NEVER
> suggest - except now. Test the hard drive first.
>
> ...Bryce
>
> /quote on http://en.wikipedia.org/wiki/Microsoft_Windows_library_files#Hal.dll
>
> Hal.dll
>
> Hal.dll is Windows'
> <http://en.wikipedia.org/wiki/Hardware_Abstraction_Layer>Hardware
> Abstraction Layer, or HAL. The HAL implements a number of functions
> that are implemented in different ways by different hardware
> platforms, which in this context, refers mostly to the
> <http://en.wikipedia.org/wiki/Chipset>Chipset. Other components in
> the operating system can then call these functions in the same way on
> all platforms, without regard for the actual implementation. For
> example, responding to an interrupt is quite different on a machine
> with an
> <http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller>Advanced
> Programmable Interrupt Controller (APIC) than on one without. The HAL
> abstracts such differences so that nothing outside the HAL need be
> concerned with them.
>
> The HAL is loaded into kernel address space and runs in kernel mode,
> so routines in the HAL cannot be called directly by applications, and
> no user mode APIs correspond directly to HAL routines. Instead the
> HAL provides services primarily to the Windows executive and kernel
> and to kernel mode device drivers. Although drivers for most hardware
> are contained in other files, commonly of file type .sys, a few core
> drivers are compiled into Hal.dll.
>
> Kernel mode device drivers for devices on buses such as
> <http://en.wikipedia.org/wiki/Conventional_PCI>PCI and
> <http://en.wikipedia.org/wiki/PCI_Express>PCI Express directly call
> routines in the HAL to access I/O ports and registers of their
> devices. The drivers use HAL routines because different platforms may
> require different implementations of these operations. The HAL
> implements the operations appropriately for each platform, so the
> same driver executable file can be used on all platforms using the
> same CPU architecture, and the driver source file can be portable
> across all architectures.
>
> On x86 systems there are several different HAL files on the
> installation media. The Windows installation procedure determines
> which ones are appropriate for the current platform and copies it to
> the hard drive, renaming it to Hal.dll if necessary. Among the
> criteria for this selection are the presence of an
> <http://en.wikipedia.org/wiki/ACPI>ACPI-compatible BIOS, the presence
> of an
> <http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller>APIC,
> and whether or not multiple processors are present and enabled. (The
> multiple cores of a multi-core CPU, and even the "logical processors"
> implemented by a hyperthreading CPU, all count as "processors" for
> this purpose.) On x86-64 and Itanium platforms there is just one
> possible Hal.dll for each CPU architecture.
> /quote off
>
>
>
>
> At 11:29 PM 10/26/2011, you wrote:
> >
> >
> >Just do a Google search for hal.dll
> >
> >There are lots of suggestions on how to fix this problem.
> >
> >This one seems pretty informative:
> >
> ><http://pcsupport.about.com/od/findbyerrormessage/a/missinghaldll.htm>http://pcsupport.about.com/od/findbyerrormessage/a/missinghaldll.htm
> >
> >However, keep in mind that this error is sometimes not telling you
> >what is wrong.
> >
> >Computers are like little kids .. they know they don't feel good,
> >they just have a hard time telling you what is wrong with them.
> >
> >HAL (Hardware Abstraction Layer) is not only the file hal.dll, but
> >also what Windows does with it when it boots.
> >
> >Replacing the hal.dll may not fix the problem, but it is the first
> >place to start.
> >
> >Even though the error message refers to a single file, it may be
> >caused by a failing hard drive, or a corrupted install of Windows.
> >
> >If replacing the file does not fix the problem, you may need to
> >reinstall Windows.
> >
> >If this fails, you may need a new hard drive.
> >
> >But take it one step at a time. There are lots of helpful sites in
> >the Google search for hal.dll
> >
> >rogerX
> >
> >--- In
> ><mailto:simplycomputers2%40yahoogroups.com>simplycomputers2@yahoogroups.com,
> >"Rene" <kevrendom@> wrote:
> > >
> > > Hi, the problem with my PC is it did not boot up and it give me
> > this message:
> > >
> > > Windows could not start because the ff: file is missing or corrupt
> > >
> > > <windows root>\system 32\hal.dll.
> > > Please reinstall a copy of the above file
> > >
> > > My problem is where do I get this file and how to reinstall it if
> > my PC didnt boot at all. Thanks and any help will be greatly appreciated.
> > >
> > > My OS is Windows XP
>
>
> [Non-text portions of this message have been removed]
>
http://tech.groups.yahoo.com/group/simplycomputers2
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.