XP (Whistler) RC1 Debugging Advice

Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and
RC1, where we are completely broken, M$ has changed something (and rejected
the bug report we logged). I was hoping to delay setting up an XP debugging
environment but now it can’t wait.
In the past I have simply installed the free build of the OS, booted to a
floppy/alternate OS and replaced the kernel and hal components. XP appears
to have taken WFP (Windows File Protection) a step further and it “repairs”
the checked kernel and hal, albeit incorrectly (the system won’t get beyond
the logon screen and requires a full reinstall).
Have any of you gotten this approach to work on XP? What are the tricks? Is
there a better/different way?

Thanks,
Kjell
**************
Kjell Swedin
Software Engineer
WRQ Inc.


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Hello kjells,

I have no clue on how it works on WinXP. But I had success under win2k
with this
http://www.microsoft.com/hwdev/sfp/wfp.htm

regards,
Anders

Wednesday, July 18, 2001, 8:36:59 AM, you wrote:

kwc> Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and
kwc> RC1, where we are completely broken, M$ has changed something (and rejected
kwc> the bug report we logged). I was hoping to delay setting up an XP debugging
kwc> environment but now it can’t wait.
kwc> In the past I have simply installed the free build of the OS, booted to a
kwc> floppy/alternate OS and replaced the kernel and hal components. XP appears
kwc> to have taken WFP (Windows File Protection) a step further and it “repairs”
kwc> the checked kernel and hal, albeit incorrectly (the system won’t get beyond
kwc> the logon screen and requires a full reinstall).
kwc> Have any of you gotten this approach to work on XP? What are the tricks? Is
kwc> there a better/different way?

kwc> Thanks,
kwc> Kjell
kwc> **************
kwc> Kjell Swedin
kwc> Software Engineer
kwc> WRQ Inc.

kwc> —
kwc> You are currently subscribed to ntfsd as: xxxxx@flaffer.com
kwc> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


Best regards,
Anders mailto:xxxxx@flaffer.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You should be able to disable WFP the same way as in Win2k. Specifly,
perform the replacement in SafeMode or set the reg key, reboot with KD
attached and then replace the files.

Actually if I were you the first thing I would do is turn on Driver
Verifier for the driver & see what happens. It might find the issue for
you w/o having to start system binaries.

-----Original Message-----
From: xxxxx@wrq.com [mailto:xxxxx@wrq.com]
Sent: Wednesday, July 18, 2001 8:37 AM
To: File Systems Developers
Subject: [ntfsd] XP (Whistler) RC1 Debugging Advice

Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and
RC1, where we are completely broken, M$ has changed something (and
rejected
the bug report we logged). I was hoping to delay setting up an XP
debugging
environment but now it can’t wait.
In the past I have simply installed the free build of the OS, booted to
a
floppy/alternate OS and replaced the kernel and hal components. XP
appears
to have taken WFP (Windows File Protection) a step further and it
“repairs”
the checked kernel and hal, albeit incorrectly (the system won’t get
beyond
the logon screen and requires a full reinstall).
Have any of you gotten this approach to work on XP? What are the tricks?
Is
there a better/different way?

Thanks,
Kjell
**************
Kjell Swedin
Software Engineer
WRQ Inc.


You are currently subscribed to ntfsd as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Why do you need to replace the kernel and Hal for setting up the
debugger?

-----Original Message-----
From: xxxxx@wrq.com [mailto:xxxxx@wrq.com]
Sent: Wednesday, July 18, 2001 8:37 AM
To: File Systems Developers
Subject: [ntfsd] XP (Whistler) RC1 Debugging Advice

Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and
RC1, where we are completely broken, M$ has changed something (and
rejected
the bug report we logged). I was hoping to delay setting up an XP
debugging
environment but now it can’t wait.
In the past I have simply installed the free build of the OS, booted to
a
floppy/alternate OS and replaced the kernel and hal components. XP
appears
to have taken WFP (Windows File Protection) a step further and it
“repairs”
the checked kernel and hal, albeit incorrectly (the system won’t get
beyond
the logon screen and requires a full reinstall).
Have any of you gotten this approach to work on XP? What are the tricks?
Is
there a better/different way?

Thanks,
Kjell
**************
Kjell Swedin
Software Engineer
WRQ Inc.


You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I’m assuming that what you’re trying to do is to run a checked kernel/hal
on xp.

Try the following:
Copy the *correct* checked hal/kernel to the %WINDIR%\system32 and rename
them something like krnchk.exe and halchk.dll. Next create a new line in
boot.ini with the current setup but add /kernel=krnchk.exe /hal=halchk.dll

This lets you swap back and forth between checked/free versions from the
boot menu and don’t have to worry about wfp.

If you don’t know what hal/kernel to use:
kernel: (pretty simple)
multiproc machines (except w/ > 4gb ram) = ntoskrnl.exe
uniprocessor (except w/ > 4gb ram) = ntkrnlmp.exe
multiproc w/ more than 4gb ram = ntkrpamp.exe
uniproc w/ more than 4gb ram = ntkrnlpa.exe

hal: open devmgmt.msc and look under the computer tab the text there is the
key to the hal being used.
“Standard PC”=hal.dll
“Advanced Configuration and Power Interface (ACPI) PC”=halacpi.dll
“ACPI Uniprocessor PC”=halaacpi.dll
“ACPI Multiprocessor PC”=halmacpi.dll
“MPS Uniprocessor PC”=halapic.dll
“MPS Multiprocessor PC”=halmps.dll
“Compaq SystemPro Multiprocessor or 100% Compatible”=halsp.dll
the short-lived SGI hal is halborg.dll (sgi was assimilated).

Note that the correct hal are all renamed to hal.dll by the system install
process which is why it may not appear to be on your system. (kernels are
renamed to ntoskrnl.exe).

A further note – on win2k, hal.dll was not protected by sfp because of the
multiple hal/renaming problem. So if you tried to replace the hal & kernel
without turning off wfp, wfp would restore the kernel but not the hal and
you’d bugcheck with ‘mismatched hal’ & be unbootable. For this reason &
others, it is usually much easier just to add the boot.ini line.

-jordan

On 07/18/01, ““Nathan Nesbit” ” wrote:
> You should be able to disable WFP the same way as in Win2k. Specifly,
> perform the replacement in SafeMode or set the reg key, reboot with KD
> attached and then replace the files.
>
> Actually if I were you the first thing I would do is turn on Driver
> Verifier for the driver & see what happens. It might find the issue for
> you w/o having to start system binaries.
>
> -----Original Message-----
> From: xxxxx@wrq.com [mailto:xxxxx@wrq.com]=20
> Sent: Wednesday, July 18, 2001 8:37 AM
> To: File Systems Developers
> Subject: [ntfsd] XP (Whistler) RC1 Debugging Advice
>
> Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and=20
> RC1, where we are completely broken, M$ has changed something (and
> rejected=20
> the bug report we logged). I was hoping to delay setting up an XP
> debugging=20
> environment but now it can’t wait.
> In the past I have simply installed the free build of the OS, booted to
> a=20
> floppy/alternate OS and replaced the kernel and hal components. XP
> appears=20
> to have taken WFP (Windows File Protection) a step further and it
> “repairs”=20
> the checked kernel and hal, albeit incorrectly (the system won’t get
> beyond=20
> the logon screen and requires a full reinstall).
> Have any of you gotten this approach to work on XP? What are the tricks?
> Is=20
> there a better/different way?
>
> Thanks,
> Kjell
> **************
> Kjell Swedin
> Software Engineer
> WRQ Inc.
>
> —
> You are currently subscribed to ntfsd as: xxxxx@microsoft.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

He wants to use the checked kernel/HAL. Of course, there’s a nice document
in the XP DDK that Peter Viscarola wrote regarding using the checked build,
and it discusses this issue, as well as a number of other issues.

Driver Verifier, while useful, does not test for the same range of issues as
the checked build. The checked build can often discover what is wrong
before it has caused the kind of damage needed to invoke driver verifier.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ravisankar Pudipeddi [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, July 18, 2001 4:15 PM
To: File Systems Developers
Subject: [ntfsd] RE: XP (Whistler) RC1 Debugging Advice

Why do you need to replace the kernel and Hal for setting up the
debugger?

-----Original Message-----
From: xxxxx@wrq.com [mailto:xxxxx@wrq.com]
Sent: Wednesday, July 18, 2001 8:37 AM
To: File Systems Developers
Subject: [ntfsd] XP (Whistler) RC1 Debugging Advice

Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and
RC1, where we are completely broken, M$ has changed something (and
rejected
the bug report we logged). I was hoping to delay setting up an XP
debugging
environment but now it can’t wait.
In the past I have simply installed the free build of the OS, booted to
a
floppy/alternate OS and replaced the kernel and hal components. XP
appears
to have taken WFP (Windows File Protection) a step further and it
“repairs”
the checked kernel and hal, albeit incorrectly (the system won’t get
beyond
the logon screen and requires a full reinstall).
Have any of you gotten this approach to work on XP? What are the tricks?
Is
there a better/different way?

Thanks,
Kjell
**************
Kjell Swedin
Software Engineer
WRQ Inc.


You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Thanks all for the helpful responses.

A few follow-up questions:

If you don’t know what hal/kernel to use:
kernel: (pretty simple)
multiproc machines (except w/ > 4gb ram) = ntoskrnl.exe
uniprocessor (except w/ > 4gb ram) = ntkrnlmp.exe
Are the preceeding transposed?
multiproc w/ more than 4gb ram = ntkrpamp.exe
uniproc w/ more than 4gb ram = ntkrnlpa.exe

On my test system (a PII 410 with 128mb) XP installs both ntoskrnl.exe and
ntkrnlpa.exe. The setup log (%WINDIR%\repair\setup.log) indicates that
neither file was renamed. The hal started life as halapic.dll and was
renamed to hal.dll.

Kjell

-----Original Message-----
From: xxxxx@interactivesi.com [mailto:xxxxx@interactivesi.com]
Sent: Wednesday, July 18, 2001 6:20 PM
To: File Systems Developers
Subject: [ntfsd] RE: XP (Whistler) RC1 Debugging Advice

I’m assuming that what you’re trying to do is to run a checked kernel/hal
on xp.

Try the following:
Copy the *correct* checked hal/kernel to the %WINDIR%\system32 and rename
them something like krnchk.exe and halchk.dll. Next create a new line in
boot.ini with the current setup but add /kernel=krnchk.exe /hal=halchk.dll

This lets you swap back and forth between checked/free versions from the
boot menu and don’t have to worry about wfp.

If you don’t know what hal/kernel to use:
kernel: (pretty simple)
multiproc machines (except w/ > 4gb ram) = ntoskrnl.exe
uniprocessor (except w/ > 4gb ram) = ntkrnlmp.exe
multiproc w/ more than 4gb ram = ntkrpamp.exe
uniproc w/ more than 4gb ram = ntkrnlpa.exe

hal: open devmgmt.msc and look under the computer tab the text there is the
key to the hal being used.
“Standard PC”=hal.dll
“Advanced Configuration and Power Interface (ACPI) PC”=halacpi.dll
“ACPI Uniprocessor PC”=halaacpi.dll
“ACPI Multiprocessor PC”=halmacpi.dll
“MPS Uniprocessor PC”=halapic.dll
“MPS Multiprocessor PC”=halmps.dll
“Compaq SystemPro Multiprocessor or 100% Compatible”=halsp.dll
the short-lived SGI hal is halborg.dll (sgi was assimilated).

Note that the correct hal are all renamed to hal.dll by the system install
process which is why it may not appear to be on your system. (kernels are
renamed to ntoskrnl.exe).

A further note – on win2k, hal.dll was not protected by sfp because of the
multiple hal/renaming problem. So if you tried to replace the hal & kernel
without turning off wfp, wfp would restore the kernel but not the hal and
you’d bugcheck with ‘mismatched hal’ & be unbootable. For this reason &
others, it is usually much easier just to add the boot.ini line.

-jordan

On 07/18/01, ““Nathan Nesbit” ” wrote:
> You should be able to disable WFP the same way as in Win2k. Specifly,
> perform the replacement in SafeMode or set the reg key, reboot with KD
> attached and then replace the files.
>
> Actually if I were you the first thing I would do is turn on Driver
> Verifier for the driver & see what happens. It might find the issue for
> you w/o having to start system binaries.
>
> -----Original Message-----
> From: xxxxx@wrq.com [mailto:xxxxx@wrq.com]=20
> Sent: Wednesday, July 18, 2001 8:37 AM
> To: File Systems Developers
> Subject: [ntfsd] XP (Whistler) RC1 Debugging Advice
>
> Hi all - somewhere between beta 2 of XP, where our FSD worked fine, and=20
> RC1, where we are completely broken, M$ has changed something (and
> rejected=20
> the bug report we logged). I was hoping to delay setting up an XP
> debugging=20
> environment but now it can’t wait.
> In the past I have simply installed the free build of the OS, booted to
> a=20
> floppy/alternate OS and replaced the kernel and hal components. XP
> appears=20
> to have taken WFP (Windows File Protection) a step further and it
> “repairs”=20
> the checked kernel and hal, albeit incorrectly (the system won’t get
> beyond=20
> the logon screen and requires a full reinstall).
> Have any of you gotten this approach to work on XP? What are the tricks?
> Is=20
> there a better/different way?
>
> Thanks,
> Kjell
> **************
> Kjell Swedin
> Software Engineer
> WRQ Inc.
>
> —
> You are currently subscribed to ntfsd as: xxxxx@microsoft.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntfsd as: xxxxx@wrq.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: xxxxx@wrq.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com