wes40oz
Tue Oct 04 16:14:38 CDT 2005
agreed,
right now it is stable but I was going to copy the hal file to c: root for
an easy copy (probably along with NTLDR and
NTdetect.com)
also going to try out bootitng tonight see how that goes, eventually I am
planning on putting Solaris 10 on there, quad boot? if for business
purposes, since I mainly work with windows xp x32 and various Solaris
versions (think the current one in our office is 8) in our office, would be
nice to fool around with also.
probably end up deleting the second install of xp 64 once I get every thing
stable. plus my mother board ate shit the other day anyways (ordered
another, think I voided the warranty by putting thermal epoxy on the NVIDIA
north bridge to hold on my water cooler, they tend not to like that...)
thanks for every ones help!!!!
wes
ps,
had the wrond address on a few of the posts so they didnt make it to the
board... probably went straight to charlie or john
"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message
news:%23RRj6bSyFHA.2076@TK2MSFTNGP14.phx.gbl...
>I only knew because I had to try to find that little bit of information for
>the BDD project I worked on...
>
> And we're all here to learn and help, and you're doing plenty of the
> second.
>
>
> --
> Charlie.
>
http://msmvps.com/xperts64
>
> "Darrell Gorter[MSFT]" wrote:
>> Hello,
>> Darn it I hate it when John and Charlie are right and I am wrong.
>> It looks like we only ship one hal file with x64 and it's always to
>> hal.dll Sorry thinking back to the x86 days with multiple hals and I
>> should have looked first.
>> I stand corrected. My mistake,
>> sorry guys.
>> Thanks,
>> Darrell Gorter[MSFT]
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>> --------------------
>> <From: "Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org>
>> <References: <u69mnEPyFHA.3408@TK2MSFTNGP09.phx.gbl>
>> <eaBGXQPyFHA.3720@TK2MSFTNGP14.phx.gbl>
>> <mAcRCUQyFHA.3020@TK2MSFTNGXA01.phx.gbl>
>> <Subject: Re: hal.dll, please read
>> <Date: Tue, 4 Oct 2005 10:11:02 -0700
>> <Lines: 95
>> <X-Priority: 3
>> <X-MSMail-Priority: Normal
>> <X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> <X-RFC2646: Format=Flowed; Original
>> <Message-ID: <uM#uCbQyFHA.2992@TK2MSFTNGP11.phx.gbl>
>> <Newsgroups: microsoft.public.windows.64bit.general
>> <NNTP-Posting-Host: h24-207-96-14.cst.dccnet.com 24.207.96.14
>> <Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
>> <Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.64bit.general:18750
>> <X-Tomcat-NG: microsoft.public.windows.64bit.general
>> <
>> <So far, on every AMD based system I've seen, it's been "hal.dll" pure
>> and
>> <simple. Now that may well not be true for multiple processor Opteron
>> <systems, and I have no idea what EM64T systems have. But for Athlon64
>> and
>> <Turion64, it's hal.dll.
>> <
>> <--
>> <Charlie.
>> <
http://msmvps.com/xperts64
>> <
>> <"Darrell Gorter[MSFT]" wrote:
>> <> Hello John,
>> <> Have to be careful here, there are different hal files so the
>> installed
>> <> hal may be different than the one listed as hal.dll in driver.cab.
>> <> look at the list of the hal*.dll files in the driver.cab file
>> <> The correct hal file is determined at setup time and then renamed to
>> <> hal.dll when it's copied to the system.
>> <> So you have to replace hal.dll with the correct one or the system may
>> not <> work or have other issues later.
>> <> Right-Click on hal.dll that is installed and choose properties to find
>> the
>> <> original name of the file.
>> <>
>> <> in Recovery Console, Expand is separate command used to extract the
>> file <> from a cab file and place it at a new location.
>> <>
>> <> Thanks,
>> <> Darrell Gorter[MSFT]
>> <>
>> <> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>> <> --------------------
>> <> <From: "John Barnes" <jbfoofy@email.net>
>> <> <References: <u69mnEPyFHA.3408@TK2MSFTNGP09.phx.gbl>
>> <> <Subject: Re: hal.dll, please read
>> <> <Date: Tue, 4 Oct 2005 07:58:29 -0700
>> <> <Lines: 40
>> <> <X-Priority: 3
>> <> <X-MSMail-Priority: Normal
>> <> <X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>> <> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>> <> <X-RFC2646: Format=Flowed; Response
>> <> <Message-ID: <eaBGXQPyFHA.3720@TK2MSFTNGP14.phx.gbl>
>> <> <Newsgroups: microsoft.public.windows.64bit.general
>> <> <NNTP-Posting-Host: 0-1pool150-50.nas8.spokane1.wa.us.da.qwest.net
>> <> 67.0.150.50
>> <> <Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>> <> <Xref: TK2MSFTNGXA01.phx.gbl
>> microsoft.public.windows.64bit.general:18733 <> <X-Tomcat-NG:
>> microsoft.public.windows.64bit.general <> <
>> <> <hal.dll is located on the x64 install cd in AMD64\DRIVER.CAB
>> <> <When you use copy in recovery console, remember the expand command
>> <> <
>> <> <"wes40oz" <wes@kelman.com> wrote in message
>> <> <news:u69mnEPyFHA.3408@TK2MSFTNGP09.phx.gbl...
>> <> <>
>> <> <> for some reason this file keep getting deleted or corrupted, and
>> wont <> <> boot, I have actually had to install xp 64 on another drive
>> and copy <> <> hal.dll to the other windows install (then it works). it
>> is not on the
>> <> <> windows xp 64 OEM cd (using the recovery consol...)
>> <> <>
>> <> <> also, what other files are associated with hal.dll?
>> <> <>
>> <> <> any information on this one, it is annoying... very annoying
>> <> <>
>> <> <> also it seems (since I have duel boot x32 and x64, or tri boot with
>> the
>> <> <> other x64 XP installed, same license same computer different drive,
>> <> works
>> <> <> fine, I wonder if that is legal...) x32 keeps over writing NTLDR
>> and
>> <> <> NTdetect.com (which results in the error message discussed above
>> <> <> "ntoskrnl.exe missing or corrupt please reinstall") and / or
>> killing
>> <> <> hal.dll every boot (almost it seems) I spent 7 hours last night in
>> the <> <> recovery consol trying to fix this, I gave up and installed x64
>> on <> another
>> <> <> drive (I have 2 raptors so that worked out well, xp x32 is
>> installed
>> on
>> <> a
>> <> <> 40gb ide drive)
>> <> <>
>> <> <> and everything works, but I will have to go back into the recovery
>> <> consol
>> <> <> to config the boot.ini since it no longer sees xp x32 anymore. oh
>> god <> this
>> <> <> is getting TEDIOUS!
>> <> <>
>> <> <> any help on preventing this in the future, I'll buy you a 6 pack!
>> <> <>
>> <> <> thanks!!!
>> <> <> --
>> <> <> Wes Newman
>> <> <> Seismic Data Processor / IT Manager
>> <> <> Kelman Technologies
>> <> <> Denver, CO
>> <> <>
>> <> <
>> <> <
>> <> <
>> <
>> <
>> <
>
>