Win 2003 SP1 on checked build?

NTFSD
1

NTFSD Folk:

I’m doing fine with developing a minifilter driver with the Win 2003 SP1 IFS
kit, but I don’t see any way of testing on a checked build.

The installation notes clearly say that it requires “Windows Server 2003
Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that I
can find). I’m sure you’re aware of all the good reasons to use a checked
build for driver development.

Any ideas?

Thanks,
Ken Cross

2

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

3

Don:

Gotcha. Thanks.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003, Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED), with
an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

I’m successfully running partial checked on Win2003 (enterprise edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3 files
(ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be identified from
setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003, Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED), with
an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

6

Yes, actually I had copied *all* the files from the DDK \debug directory
(renamed to *.chk) to system32. I don’t want to name them *.exe since that
would probably result in an unbootable system.

Are you running with SP1 installed on the (partial) checked build? Maybe
that could be the difference. In my case, the kernel & hal are build 1228,
whereas the rest of the system is build 1218.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Friday, October 01, 2004 11:09 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

I’m successfully running partial checked on Win2003 (enterprise edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3 files
(ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be identified from
setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003, Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED), with
an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

7

If your kernel and hal are that out of sync (10 builds) with the rest of
the OS, it is very likely to cause this problem.

Do you have access to a beta build of the DDK/IFS Kit that is the same
as the beta Server 2003 SP1 build? If so, pull the chk kernel and hal
from there to ensure that everything remains in sync. We build the DDK
and IFS Kit along with the full operating system, so the DDK build picks
up the chk kernel and hal binaries from the same operating system build.
For example, the chk kernels and hals from build 1218 should work with
Server 2003 SP1 build 1218.

Thanks,
Molly Brown
Microsoft Corporation

This posting is provided “AS IS” with no warranties and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Friday, October 01, 2004 8:09 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

I’m successfully running partial checked on Win2003 (enterprise
edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3
files (ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be
identified from setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003,
Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED),
with an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked
kernel and hal under the debug directory. While I don’t consider this
complete, it does provide a significant improvement over a pure retail
build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003
> SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server
> 2003 Service Pack 1”, but SP1 isn’t available for Win 2003 checked
> builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a
> checked build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

8

Molly:

Good idea (I had the 1218 DDK was on another machine).

It got further, but no cigar. No BSOD, but it gets to “Windows is starting
up…” and just sits (20 minutes so far).

Thanks anyhow,
Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Molly Brown
Sent: Friday, October 01, 2004 11:51 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

If your kernel and hal are that out of sync (10 builds) with the rest of
the OS, it is very likely to cause this problem.

Do you have access to a beta build of the DDK/IFS Kit that is the same
as the beta Server 2003 SP1 build? If so, pull the chk kernel and hal
from there to ensure that everything remains in sync. We build the DDK
and IFS Kit along with the full operating system, so the DDK build picks
up the chk kernel and hal binaries from the same operating system build.
For example, the chk kernels and hals from build 1218 should work with
Server 2003 SP1 build 1218.

Thanks,
Molly Brown
Microsoft Corporation

This posting is provided “AS IS” with no warranties and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Friday, October 01, 2004 8:09 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

I’m successfully running partial checked on Win2003 (enterprise
edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3
files (ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be
identified from setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003,
Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED),
with an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked
kernel and hal under the debug directory. While I don’t consider this
complete, it does provide a significant improvement over a pure retail
build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003
> SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server
> 2003 Service Pack 1”, but SP1 isn’t available for Win 2003 checked
> builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a
> checked build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

9

As Molly pointed it out, the problem must be in build number difference. I’m
running Srv02-SP1 partial checked build number 1218. I’ve picked
ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll (renamed to .chk) from DDKSP1
(Microsoft beta).
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 5:48 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Yes, actually I had copied *all* the files from the DDK \debug directory
(renamed to *.chk) to system32. I don’t want to name them *.exe since that
would probably result in an unbootable system.

Are you running with SP1 installed on the (partial) checked build? Maybe
that could be the difference. In my case, the kernel & hal are build 1228,
whereas the rest of the system is build 1218.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Friday, October 01, 2004 11:09 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

I’m successfully running partial checked on Win2003 (enterprise edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3 files
(ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be identified from
setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003, Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED), with
an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

10

Right – I did the same thing. Unfortunately, as I pointed out in a
subsequent email, it gets further (no BSOD), but it just gets to “Windows is
starting up…” and hangs.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Tuesday, October 05, 2004 2:35 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

As Molly pointed it out, the problem must be in build number difference. I’m
running Srv02-SP1 partial checked build number 1218. I’ve picked
ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll (renamed to .chk) from DDKSP1
(Microsoft beta).
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 5:48 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Yes, actually I had copied *all* the files from the DDK \debug directory
(renamed to *.chk) to system32. I don’t want to name them *.exe since that
would probably result in an unbootable system.

Are you running with SP1 installed on the (partial) checked build? Maybe
that could be the difference. In my case, the kernel & hal are build 1228,
whereas the rest of the system is build 1218.

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Primoz Beltram
Sent: Friday, October 01, 2004 11:09 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

I’m successfully running partial checked on Win2003 (enterprise edition).
Did you copy 2 or 3 files to %SystemRoot%\System32 dir?
If you read “The NT Insider” page 34, Figure 2, you will see that 3 files
(ntkrnlmp.exe, ntkrpamp.exe and hallapic.dll) need to be identified from
setup.log and copied in system32 dir.
Boot.ini is OK.
WBR Primoz

-----Original Message-----
From: Ken Cross [mailto:xxxxx@comcast.net]
Sent: Friday, October 01, 2004 4:45 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Win 2003 SP1 on checked build?

Hmm … has anyone done this successfully?

I copied the files to \windows\system32 (renamed to ntoskrnl.chk and
halaacpi.chk – I got halaacpi from setup.log) and I get a BSOD. My
boot.ini line is:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Windows Server 2003, Checked”
/fastdetect /debug /kernel=ntoskrnl.chk /hal=halaacpi.chk

The crash I’m getting is BugCheck 6B (PROCESS1_INITIALIZATION_FAILED), with
an NT error code C000007A (STATUS_PROCEDURE_NOT_FOUND).

The kernel & hal are build 1228, whereas the rest of the system is build
1218. Could that be it? If so, are we stuck with no Win 2003 SP1 on a
checked build?

Ken

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, October 01, 2004 9:03 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Win 2003 SP1 on checked build?

Ken,

Look in the DDK for the same build, you will find the checked kernel
and hal under the debug directory. While I don’t consider this complete, it
does provide a significant improvement over a pure retail build.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I’m doing fine with developing a minifilter driver with the Win 2003 SP1
IFS
> kit, but I don’t see any way of testing on a checked build.
>
> The installation notes clearly say that it requires “Windows Server 2003
> Service Pack 1”, but SP1 isn’t available for Win 2003 checked builds (that
I
> can find). I’m sure you’re aware of all the good reasons to use a checked
> build for driver development.
>
> Any ideas?
>
> Thanks,
> Ken Cross
>
>
>

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com