Sean,
I’m one of the people who has been complaining about this. My test system
is a PIII, and I do believe ACPI is enabled.
I recently reinstalled XP on my test system. I only booted a couple of
times with WinDBG running before installing Driver Verifier, but those few
times it booted fine.
So this makes three major theories: Checked builds, ACPI and maybe Driver
Verifier?
-Evan
that works fine, we use the non-ACPI hal (hal.dll) but on the 2 where the
reboot fails if WinDBG is connected, they are both ACPI machines… I know
this could be quite a stretch, but it’s the only real difference
I’ve found
so far in the configurations of the machines… I am seeing this behavior
with the latest version (3.0.0020.0) of windbg…
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com