Prev: Looking for nt CRT source code
Next: Signing kernel code x64
From: Sethu on 28 Dec 2009 13:00
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
From: Maxim S. Shatskih on 28 Dec 2009 14:16
> 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).

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Sethu on 29 Dec 2009 03:10
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
From: Scott Noone on 30 Dec 2009 12:02
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" <Sethu(a)discussions.microsoft.com> wrote in message
news:714FAF34-CE1C-436F-8012-238EF164FEA9(a)microsoft.com...
> 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


From: Sethu on 5 Jan 2010 07:37
Still I am having this problem

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Looking for nt CRT source code
Next: Signing kernel code x64