Asserts in checked kernel/hal of XP Pro x64

NTDEV
1

I installed XP Pro x64, Free build. I then pulled in the checked hal and kernel from the checked CD (I reviewed \windows\repair\setup.log to figure out which hal and kernel to use) using the /HAL= and /KERNEL= command line options.

Whenever I book the checked build, I get a couple of assertions:
*** Assertion failed: HighWatermark too large, use 0 if you dont know a reasonable value(HighWatermark < MAXLONG)
*** Source File: d:\srvrtm\base\ntos\io\pnpmgr\remlock.c, line 82

The system is based on an iWill DK8EW motherboard with two AMD Opteron 280 CPUs (those are dual-core).
4 gigs of physical ram.

I installed the latest available x64 drivers from nVidia (motherboard, audio, etc), and from Broadcom (the on-board GigE NICs). All other drivers are XP x64 stock.

Is this something I should worry about, or is it just the consequence of using the checked x64 build on this system?
It is a multi-boot system, and the first partition has XP Pro SP2 32 bit, both free and checked, which both boot without trouble.

So far, I just make sure WinDbg is running when I boot and I ignore the assertions. After that it seems to run fine. Am I setting myself up for trouble, or can I safely ignore this?

Michael Kohne
xxxxx@kohne.org
“You must be smarter than the equipment you are trying to operate.”

2

You can ignore them. I don’t know of any way to suppress them, which is
unfortunate, as they are irritating. Additionally, there are plenty
more distractions like these, particularly from some setup
applications.

mm

>> xxxxx@kohne.org 2006-10-26 14:32 >>>
I installed XP Pro x64, Free build. I then pulled in the checked hal
and kernel from the checked CD (I reviewed \windows\repair\setup.log to
figure out which hal and kernel to use) using the /HAL= and /KERNEL=
command line options.

Whenever I book the checked build, I get a couple of assertions:
*** Assertion failed: HighWatermark too large, use 0 if you dont know a
reasonable value(HighWatermark < MAXLONG)
*** Source File: d:\srvrtm\base\ntos\io\pnpmgr\remlock.c, line 82

The system is based on an iWill DK8EW motherboard with two AMD Opteron
280 CPUs (those are dual-core).
4 gigs of physical ram.

I installed the latest available x64 drivers from nVidia (motherboard,
audio, etc), and from Broadcom (the on-board GigE NICs). All other
drivers are XP x64 stock.

Is this something I should worry about, or is it just the consequence
of using the checked x64 build on this system?
It is a multi-boot system, and the first partition has XP Pro SP2 32
bit, both free and checked, which both boot without trouble.

So far, I just make sure WinDbg is running when I boot and I ignore the
assertions. After that it seems to run fine. Am I setting myself up for
trouble, or can I safely ignore this?

Michael Kohne
xxxxx@kohne.org
“You must be smarter than the equipment you are trying to operate.”

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Martin O’Brien wrote:

You can ignore them. I don’t know of any way to suppress them, which is
unfortunate, as they are irritating. Additionally, there are plenty
more distractions like these, particularly from some setup
applications.

mm

Thank you - I needed someone to confirm that I’m not setting myself up
for too much of a hard time.

Michael Kohne