driver debugg messages not printing on WinDbg.

NTDEV
1

Hi all,

My scsiminiport driver debugg messages are not getting printed on the WinDbg
running on host computer.

The message shows that the connection is estalbilshed and WinXP/SP1 symbol
files installed on the host computer. However I am getting this following
message

"The call to LoadLibrary(kdexts) failed, Win32 error 2 "
“The system cannot find the file specified.”

Please help,

Thanks,
shakeel.

2

Use the checked version of scsiport or cheat and call the DDK debug routines
directly.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
Sent: Friday, April 02, 2004 3:34 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] driver debugg messages not printing on WinDbg.

Hi all,

My scsiminiport driver debugg messages are not getting
printed on the WinDbg running on host computer.

The message shows that the connection is estalbilshed and
WinXP/SP1 symbol files installed on the host computer.
However I am getting this following message

"The call to LoadLibrary(kdexts) failed, Win32 error 2 "
“The system cannot find the file specified.”

Please help,

Thanks,
shakeel.

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

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

3

you mean checked version of my scsiminiport. Yes, I tried that still not
getting it.

Mark, What do mean by “cheat and call the DDK debug routines directly”? I
am using DebugPrint() macro defined in srb.h

Thanks,
Shakeel.

“Mark Roddy” wrote in message news:xxxxx@ntdev…
> Use the checked version of scsiport or cheat and call the DDK debug
routines
> directly.
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > Sent: Friday, April 02, 2004 3:34 PM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] driver debugg messages not printing on WinDbg.
> >
> > Hi all,
> >
> > My scsiminiport driver debugg messages are not getting
> > printed on the WinDbg running on host computer.
> >
> > The message shows that the connection is estalbilshed and
> > WinXP/SP1 symbol files installed on the host computer.
> > However I am getting this following message
> >
> > "The call to LoadLibrary(kdexts) failed, Win32 error 2 "
> > “The system cannot find the file specified.”
> >
> > Please help,
> >
> > Thanks,
> > shakeel.
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> > xxxxx@hollistech.com To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
>

4

No I meant used the checked version of scsiport.sys. Try installing the
checked build of your target os (w2k/xp/w2k3) on your test system.

The definition of DebugPrint in srb.h is:

#if DBG
#define DebugPrint(x) ScsiDebugPrint x
#else
#define DebugPrint(x)
#endif

This is going to call ScsiDebugPrint when compiled for your checked driver,
and I assure you that the released version of scsiport’s ScsiDebugPrint does
nothing at all.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
Sent: Friday, April 02, 2004 5:37 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] driver debugg messages not printing on WinDbg.

you mean checked version of my scsiminiport. Yes, I tried
that still not getting it.

Mark, What do mean by “cheat and call the DDK debug routines
directly”? I am using DebugPrint() macro defined in srb.h

Thanks,
Shakeel.

“Mark Roddy” wrote in message
> news:xxxxx@ntdev…
> > Use the checked version of scsiport or cheat and call the DDK debug
> routines
> > directly.
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > > Sent: Friday, April 02, 2004 3:34 PM
> > > To: Windows System Software Devs Interest List
> > > Subject: [ntdev] driver debugg messages not printing on WinDbg.
> > >
> > > Hi all,
> > >
> > > My scsiminiport driver debugg messages are not getting printed on
> > > the WinDbg running on host computer.
> > >
> > > The message shows that the connection is estalbilshed and
> > > WinXP/SP1 symbol files installed on the host computer.
> > > However I am getting this following message
> > >
> > > "The call to LoadLibrary(kdexts) failed, Win32 error 2 "
> > > “The system cannot find the file specified.”
> > >
> > > Please help,
> > >
> > > Thanks,
> > > shakeel.
> > >
> > >
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > >
> > > You are currently subscribed to ntdev as:
> > > xxxxx@hollistech.com To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> >
> >
> >
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

5

Mark,
you were right. Wroks for Checked w2k target OS with Checked miniport
driver.

But still have problem with the Checked WXP target OS, not getting the debug
messages of driver printed.

Thanks,
“Mark Roddy” wrote in message news:xxxxx@ntdev…
> No I meant used the checked version of scsiport.sys. Try installing the
> checked build of your target os (w2k/xp/w2k3) on your test system.
>
> The definition of DebugPrint in srb.h is:
>
> #if DBG
> #define DebugPrint(x) ScsiDebugPrint x
> #else
> #define DebugPrint(x)
> #endif
>
> This is going to call ScsiDebugPrint when compiled for your checked
driver,
> and I assure you that the released version of scsiport’s ScsiDebugPrint
does
> nothing at all.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > Sent: Friday, April 02, 2004 5:37 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] driver debugg messages not printing on WinDbg.
> >
> > you mean checked version of my scsiminiport. Yes, I tried
> > that still not getting it.
> >
> > Mark, What do mean by “cheat and call the DDK debug routines
> > directly”? I am using DebugPrint() macro defined in srb.h
> >
> > Thanks,
> > Shakeel.
> >
> > “Mark Roddy” wrote in message
> > news:xxxxx@ntdev…
> > > Use the checked version of scsiport or cheat and call the DDK debug
> > routines
> > > directly.
> > >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > > > Sent: Friday, April 02, 2004 3:34 PM
> > > > To: Windows System Software Devs Interest List
> > > > Subject: [ntdev] driver debugg messages not printing on WinDbg.
> > > >
> > > > Hi all,
> > > >
> > > > My scsiminiport driver debugg messages are not getting printed on
> > > > the WinDbg running on host computer.
> > > >
> > > > The message shows that the connection is estalbilshed and
> > > > WinXP/SP1 symbol files installed on the host computer.
> > > > However I am getting this following message
> > > >
> > > > "The call to LoadLibrary(kdexts) failed, Win32 error 2 "
> > > > “The system cannot find the file specified.”
> > > >
> > > > Please help,
> > > >
> > > > Thanks,
> > > > shakeel.
> > > >
> > > >
> > > >
> > > > —
> > > > Questions? First check the Kernel Driver FAQ at
> > > > http://www.osronline.com/article.cfm?id=256
> > > >
> > > > You are currently subscribed to ntdev as:
> > > > xxxxx@hollistech.com To unsubscribe send a blank email to
> > > > xxxxx@lists.osr.com
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> > xxxxx@hollistech.com To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
>

6

See the DDK (3790) documentation for ScsiDebugPrint.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
Sent: Friday, April 02, 2004 8:05 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] driver debugg messages not printing on WinDbg.

Mark,
you were right. Wroks for Checked w2k target OS with Checked
miniport driver.

But still have problem with the Checked WXP target OS, not
getting the debug messages of driver printed.

Thanks,
“Mark Roddy” wrote in message
> news:xxxxx@ntdev…
> > No I meant used the checked version of scsiport.sys. Try installing
> > the checked build of your target os (w2k/xp/w2k3) on your
> test system.
> >
> > The definition of DebugPrint in srb.h is:
> >
> > #if DBG
> > #define DebugPrint(x) ScsiDebugPrint x #else #define DebugPrint(x)
> > #endif
> >
> > This is going to call ScsiDebugPrint when compiled for your checked
> driver,
> > and I assure you that the released version of scsiport’s
> > ScsiDebugPrint
> does
> > nothing at all.
> >
> >
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > > Sent: Friday, April 02, 2004 5:37 PM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re:[ntdev] driver debugg messages not printing on WinDbg.
> > >
> > > you mean checked version of my scsiminiport. Yes, I tried
> that still
> > > not getting it.
> > >
> > > Mark, What do mean by “cheat and call the DDK debug routines
> > > directly”? I am using DebugPrint() macro defined in srb.h
> > >
> > > Thanks,
> > > Shakeel.
> > >
> > > “Mark Roddy” wrote in message
> > > news:xxxxx@ntdev…
> > > > Use the checked version of scsiport or cheat and call the DDK
> > > > debug
> > > routines
> > > > directly.
> > > >
> > > > > -----Original Message-----
> > > > > From: xxxxx@lists.osr.com
> > > > > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > > > > Sent: Friday, April 02, 2004 3:34 PM
> > > > > To: Windows System Software Devs Interest List
> > > > > Subject: [ntdev] driver debugg messages not printing
> on WinDbg.
> > > > >
> > > > > Hi all,
> > > > >
> > > > > My scsiminiport driver debugg messages are not
> getting printed
> > > > > on the WinDbg running on host computer.
> > > > >
> > > > > The message shows that the connection is estalbilshed and
> > > > > WinXP/SP1 symbol files installed on the host computer.
> > > > > However I am getting this following message
> > > > >
> > > > > "The call to LoadLibrary(kdexts) failed, Win32 error 2 "
> > > > > “The system cannot find the file specified.”
> > > > >
> > > > > Please help,
> > > > >
> > > > > Thanks,
> > > > > shakeel.
> > > > >
> > > > >
> > > > >
> > > > > —
> > > > > Questions? First check the Kernel Driver FAQ at
> > > > > http://www.osronline.com/article.cfm?id=256
> > > > >
> > > > > You are currently subscribed to ntdev as:
> > > > > xxxxx@hollistech.com To unsubscribe send a blank email to
> > > > > xxxxx@lists.osr.com
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > >
> > > You are currently subscribed to ntdev as:
> > > xxxxx@hollistech.com To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> >
> >
> >
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

7

That is correct. The ScsiDebugPrint() does nothing at all even if I
installed CHECKED version of My driver on target with retail version of
w2k/wxp. I don’t wan’t to install the checked version of target OS.

How can I force the scsiport driver to print debug messages?

Thanks,
Shakeel.
“Mark Roddy” wrote in message news:xxxxx@ntdev…
> No I meant used the checked version of scsiport.sys. Try installing the
> checked build of your target os (w2k/xp/w2k3) on your test system.
>
> The definition of DebugPrint in srb.h is:
>
> #if DBG
> #define DebugPrint(x) ScsiDebugPrint x
> #else
> #define DebugPrint(x)
> #endif
>
> This is going to call ScsiDebugPrint when compiled for your checked
driver,
> and I assure you that the released version of scsiport’s ScsiDebugPrint
does
> nothing at all.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > Sent: Friday, April 02, 2004 5:37 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] driver debugg messages not printing on WinDbg.
> >
> > you mean checked version of my scsiminiport. Yes, I tried
> > that still not getting it.
> >
> > Mark, What do mean by “cheat and call the DDK debug routines
> > directly”? I am using DebugPrint() macro defined in srb.h
> >
> > Thanks,
> > Shakeel.
> >
> > “Mark Roddy” wrote in message
> > news:xxxxx@ntdev…
> > > Use the checked version of scsiport or cheat and call the DDK debug
> > routines
> > > directly.
> > >
> > > > -----Original Message-----
> > > > From: xxxxx@lists.osr.com
> > > > [mailto:xxxxx@lists.osr.com] On Behalf Of shakeel
> > > > Sent: Friday, April 02, 2004 3:34 PM
> > > > To: Windows System Software Devs Interest List
> > > > Subject: [ntdev] driver debugg messages not printing on WinDbg.
> > > >
> > > > Hi all,
> > > >
> > > > My scsiminiport driver debugg messages are not getting printed on
> > > > the WinDbg running on host computer.
> > > >
> > > > The message shows that the connection is estalbilshed and
> > > > WinXP/SP1 symbol files installed on the host computer.
> > > > However I am getting this following message
> > > >
> > > > "The call to LoadLibrary(kdexts) failed, Win32 error 2 "
> > > > “The system cannot find the file specified.”
> > > >
> > > > Please help,
> > > >
> > > > Thanks,
> > > > shakeel.
> > > >
> > > >
> > > >
> > > > —
> > > > Questions? First check the Kernel Driver FAQ at
> > > > http://www.osronline.com/article.cfm?id=256
> > > >
> > > > You are currently subscribed to ntdev as:
> > > > xxxxx@hollistech.com To unsubscribe send a blank email to
> > > > xxxxx@lists.osr.com
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as:
> > xxxxx@hollistech.com To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
>
>