How to enable ScsiDebugPrint without a kernel debugger?

I’m trying to catch a problem at our customers, so I need to get the
ScsiDebugPrint output without running a debugger.

It seems that the only way to enable it is to edit the scsiport.sys variable
ScsiDebug. But how would Microsoft debug disk issues in the at customer
sites if that’s the only way?

This is an NT 4.0 system (not XP), so it doesn’t use the new DbgPrintEx
stuff, which I think can be enabled in boot.ini.

Any help is appreciated!

There’s no way to get the output without having a debugger attached. We
would help the customer get a debugger connected to their failing
machine and/or spend lots and lots of time pouring through the crash
dump to piece together what happened.

We’d also try to reproduce the problem locally so we could put
instrumented binaries into the problem system more easily.

-p

-----Original Message-----
From: Taed Wynnell [mailto:xxxxx@vertical.com]
Sent: Friday, March 07, 2003 9:18 PM
To: NT Developers Interest List

I’m trying to catch a problem at our customers, so I need to get the
ScsiDebugPrint output without running a debugger.

It seems that the only way to enable it is to edit the scsiport.sys
variable ScsiDebug. But how would Microsoft debug disk issues in the at
customer sites if that’s the only way?

This is an NT 4.0 system (not XP), so it doesn’t use the new DbgPrintEx
stuff, which I think can be enabled in boot.ini.

Any help is appreciated!


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