Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows 7 checked HAL source file

49 views
Skip to first unread message

Sethu

unread,
Dec 24, 2009, 1:27:02 PM12/24/09
to
I went through the following page about installing just checked build OS and
HAL for Windows 7, as it stated for Vista and later
http://msdn.microsoft.com/en-us/library/cc835892.aspx

I cant find HAL SourceFileName from "%SystemRoot%\Inf\setuppapi.dev.log"
file as hal.dll is not available

I had halacpi.dll and halmacpi.dll file available in WDK i386 debug
directory, these file names are not present on the log file(!)

I just went on and used halmacpi.dll file as the HAL source file (as my
target system is multiprocessor) and updated the boot entry as well, as less
expected the system failed to boot and gone for a system repair

I tried the other hal file also, the results are the same

How to get the correct HAL source file for Windows 7?

Don Burn

unread,
Dec 24, 2009, 1:35:13 PM12/24/09
to
Have you tried in explorer right clicking hal.dll and choosing properties,
then under the version tab checking original file name? I've done this ons
systems through Vista, but not on Win7 to get the name?


--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"Sethu" <Se...@discussions.microsoft.com> wrote in message
news:3035C58A-9541-4217...@microsoft.com...

> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4715 (20091224) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4715 (20091224) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


Maxim S. Shatskih

unread,
Dec 25, 2009, 5:23:48 AM12/25/09
to
Am I wrong that Vista+ Windows has 1 and only 1 HAL (halmacpi)?

--
Maxim S. Shatskih
Windows DDK MVP
ma...@storagecraft.com
http://www.storagecraft.com

"Don Burn" <bu...@stopspam.windrvr.com> wrote in message news:OiuZWfMh...@TK2MSFTNGP02.phx.gbl...

Sethu

unread,
Dec 28, 2009, 2:35:02 AM12/28/09
to

I checked the halmacpi.dll version (6.1.7600.16385) and original file name
(same name).

If halmacpi.dll is the HAL file for the multiprocessor system then why it is
not logged in setuppapi.dev.log file?

Yeah Scott, I used kernel and HAL files together

Sethu

unread,
Dec 28, 2009, 1:00:01 PM12/28/09
to
I followed the same procedure in Vista SP1 x86 PC (dual boot)

1. Searched hal.dll in setuppapi.dev.log file and found HAL source file name
(halmacpi.dll)
2. Got the kernel file name by running 'lmv mnt' command in the attached
debugger
3. Renamed halmacpi.dll and ntkrpamp.exe file from WDK debug directory to
halmacpi.chk and ntkrpamp.chk resp
4. Copied both the files to %SystemRoot%\system32 folder
5. Modified kernel and HAL boot entries as specified (bcdedit /set {ID}
kernel ntkrpamp.chk) (bcdedit /set {ID} hal halmacpi.chk)

During the next boot I am getting PSHED.dll file missing or corrupted with
status code 0xC0000098

I even reset system file protection in registry before copying the files
(HKLM\Software\Policies\Microsoft\Windows NT\Windows File
Protection\SFCDisable (REG_DWORD) 2)

If I went for system repair with boot disk, HAL and kernel checked files are
removed and system boots properly with HAL and kernel boot entry options
present

How to solve this to get checked build for Vista and 7?
Please post your comments

Maxim S. Shatskih

unread,
Dec 28, 2009, 2:16:24 PM12/28/09
to
> 1. Searched hal.dll in setuppapi.dev.log file and found HAL source file name
> (halmacpi.dll)

You can also compare the installed HAL with all hal*.dll files in the distro.

> 2. Got the kernel file name by running 'lmv mnt' command in the attached
> debugger
> 3. Renamed halmacpi.dll and ntkrpamp.exe file from WDK debug directory to
> halmacpi.chk and ntkrpamp.chk resp
> 4. Copied both the files to %SystemRoot%\system32 folder
> 5. Modified kernel and HAL boot entries as specified (bcdedit /set {ID}
> kernel ntkrpamp.chk) (bcdedit /set {ID} hal halmacpi.chk)

Correct. This works fine for me for 2008 R2 x64 (the only OS where I use the checked kernel).

Sethu

unread,
Dec 29, 2009, 3:10:01 AM12/29/09
to
Thanks Maxim for your post

I tried all the three HAL dll files, halmacpi.dll, halacpi.dll and hal.dll
(orginal file name halmacpi.dll), the results are the same

The errors may be different in Vista and 7, on Vista SP1 pshed.dll is
missing and on 7 it launches system repair utility

Please suggest where I can get more help on this

Scott Noone

unread,
Dec 30, 2009, 12:02:41 PM12/30/09
to
Have you booted with /debug and hooked a debugger up when the system fails
to boot? It could be something as simple as an ASSERT in the checked build
firing, which would cause instant death if you aren't booted with debugging
enabled.

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

"Sethu" <Se...@discussions.microsoft.com> wrote in message

news:714FAF34-CE1C-436F...@microsoft.com...

Sethu

unread,
Jan 5, 2010, 7:37:01 AM1/5/10
to
Still I am having this problem

Sethu

unread,
Jan 6, 2010, 2:27:01 AM1/6/10
to
Yeah Scot. I already had the debugger attached through firewire cable

I guess the problem is happening before debugger attachment, that why no
exception is caught on debugger

In Win7 'Starting Windows' is appearing for few sec and going to system
repair after that, no error message

I am using the HAL checked binaries from WDK 7600.16385 for Win7

Since the document for Win7 is not complete I am bugging you (HAL source
file name not present in setuppapi.dev.log file)

Scott Noone

unread,
Jan 6, 2010, 8:37:45 AM1/6/10
to
Bummer, so the boot loader doesn't like it.

Here's the checklist that I follow when things don't work:

1) Both kernel and HAL are in \SystemRoot\System32

2) Both kernel and HAL have 8.3 names

3) Both kernel and HAL are checked

4) Switches in BCD/boot.ini are spelled correctly

5) Parameters to switches in BCD/boot.ini are spelled correctly

If that's all correct then I'm definitely stumped.

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com


"Sethu" <Se...@discussions.microsoft.com> wrote in message

news:294E7A4A-CE7C-415E...@microsoft.com...

Pavel Lebedinsky [MSFT]

unread,
Jan 6, 2010, 1:12:54 PM1/6/10
to
> Bummer, so the boot loader doesn't like it.
>
> Here's the checklist that I follow when things don't work:

You can also try enabling boot debugging (bcdedit /set bootdebug on)
to see if that gives any additional clues.

--
Pavel Lebedinsky/Windows Fundamentals Test
This posting is provided "AS IS" with no warranties, and confers no rights.


Sethu

unread,
Feb 3, 2010, 1:54:01 AM2/3/10
to

Hi Scott,

I got partial checked build working, there couple of problems lying

1. Although my system is multi-core (core 2 and Event ID 6009 as
Multiprocessor Free), I need ntkrnlpa.exe kernel file which is for
Uniprocessor PAE support

My big surprise is when I ran 'lmv mnt' through debugger it lists
ntkrpamp.exe as the kernel file loaded ?? but why it needs ntkrnlpa.exe file
instead?

2. This Uniprocessor kernel file is not available with WDK unlike
Multiprocessor file. I have to download and install checked build Win7 to get
this kernel file, which contradicts the need for going to partial checked
build

Thanks
Sethu

Maxim S. Shatskih

unread,
Feb 3, 2010, 5:50:53 PM2/3/10
to
> 2. This Uniprocessor kernel file is not available with WDK unlike
> Multiprocessor file.

Am I wrong that the released Windows have no uniprocessor kernel since Vista?

0 new messages