Jump-start your project by learning from devs who
write Windows drivers and file systems every day.
Take an OSR seminar!

Upcoming OSR Seminars:
WDM Lab, Seattle, WA 16 August 2010
WDF Lab, Santa Clara, CA 27 September 2010
Debug Lab, Portland, OR 18 October 2010
Windows Internals & Software Drivers Lab, Santa Clara, CA 15 November 2010


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 5  
26 Jun 00 18:49
ntdev member 2898
xxxxxx@usa.net
Join Date:
Posts To This List: 4
NT Fake out SCSI Miniport driver

I'm looking for information on, or sample code for, a fake out NT scsi miniport driver. I need to know how to make it look like I have a bogus device hooked up to a bogus HBA. I took the aha154x DDK sample and have it looking like \Device\ScsiPort2 to NT, but I need to know how to get NT to think there's a device attached that it can talk to. How do I configure HW_INITIALIZATION_DATA, and how do I handle callbacks for the various routines to and from the scsi port driver. Thanks. Chuck xxxxx@usa.net PS - My DebugPrint()s don't show up on windbg. --
  Message 2 of 5  
26 Jun 00 21:06
ntdev member 955
xxxxxx@hp.com
Join Date:
Posts To This List: 102
RE: NT Fake out SCSI Miniport driver

NT (SCSIPORT) discovers LUNs on the HBA by sending SCSI inquiry and/or report-LUNs commands to potential SCSI addresses. These are sent to your miniport as SRBs via HwStartIo. You just need to mock valid device responses to these commands for one such address (LUN should be zero, as SCSIPORT won't discover non-zero LUNs if there is no response on LUN zero). ----------------------------------------------------------------------- Dave Cox Hewlett-Packard Co. HPSO/SSMO (Santa Barbara) https://ecardfile.com/id/Dave+Cox -----Original Message----- From: Chuck R [mailto:xxxxx@usa.net] Sent: Monday, June 26, 2000 3:51 PM To: NT Developers Interest List Subject: [ntdev] NT Fake out SCSI Miniport driver I'm looking for information on, or sample code for, a fake out NT scsi miniport driver. I need to know how to make it look like I have a bogus device hooked up to a bogus HBA. I took the aha154x DDK sample and have it looking like \Device\ScsiPort2 to NT, but I need to know how to get NT to think there's a device attached that it can talk to. How do I configure HW_INITIALIZATION_DATA, and how do I handle callbacks for the various routines to and from the scsi port driver. Thanks. Chuck xxxxx@usa.net PS - My DebugPrint()s don't show up on windbg.
  Message 3 of 5  
27 Jun 00 10:34
ntdev member 2374
xxxxxx@ami.com
Join Date:
Posts To This List: 12
RE: NT Fake out SCSI Miniport driver

Hi, I think ATAPI will be the best one to start with. Regarding the DebugPrint's you need to change the export variable ScsiDebug of SCSIPort to 1, 2 or 3. If you use DebugPrint((0, "....")); it will be displayed in WinDebug without changing the SCSIDebug variable. Ofcourse you need to copy the debug version of SCSIPort.sys to see all the debug messages anyway. Syam. -----Original Message----- From: Chuck R [mailto:xxxxx@usa.net] Sent: Monday, June 26, 2000 6:51 PM To: NT Developers Interest List Subject: [ntdev] NT Fake out SCSI Miniport driver I'm looking for information on, or sample code for, a fake out NT scsi miniport driver. I need to know how to make it look like I have a bogus device hooked up to a bogus HBA. I took the aha154x DDK sample and have it looking like \Device\ScsiPort2 to NT, but I need to know how to get NT to think there's a device attached that it can talk to. How do I configure HW_INITIALIZATION_DATA, and how do I handle callbacks for the various routines to and from the scsi port driver. Thanks. Chuck xxxxx@usa.net <mailto:xxxxx@usa.net> PS - My DebugPrint()s don't show up on windbg. --
  Message 4 of 5  
27 Jun 00 14:52
Paul Bunn
xxxxxx@ultrabac.com
Join Date:
Posts To This List: 248
RE: NT Fake out SCSI Miniport driver

A really nice solution to setting ScsiDebug automatically is to place the following registry value: HKLM\system\currentcontrolset\services\(scsi miniport driver name)\device\ScsiDebug:REG_DWORD You still need to be using the checked version of scsiport of course. Regards, Paul Bunn, UltraBac.com, 425-644-6000 Microsoft MVP - WindowsNT/2000 http://www.ultrabac.com -----Original Message----- From: Neela Syam Kolli [mailto:xxxxx@ami.com] Sent: Tuesday, June 27, 2000 7:27 AM To: NT Developers Interest List Subject: [ntdev] RE: NT Fake out SCSI Miniport driver Hi, I think ATAPI will be the best one to start with. Regarding the DebugPrint's you need to change the export variable ScsiDebug of SCSIPort to 1, 2 or 3. If you use DebugPrint((0, "....")); it will be displayed in WinDebug without changing the SCSIDebug variable. Ofcourse you need to copy the debug version of SCSIPort.sys to see all the debug messages anyway. Syam. -----Original Message----- From: Chuck R [mailto:xxxxx@usa.net] Sent: Monday, June 26, 2000 6:51 PM To: NT Developers Interest List Subject: [ntdev] NT Fake out SCSI Miniport driver I'm looking for information on, or sample code for, a fake out NT scsi miniport driver. I need to know how to make it look like I have a bogus device hooked up to a bogus HBA. I took the aha154x DDK sample and have it looking like \Device\ScsiPort2 to NT, but I need to know how to get NT to think there's a device attached that it can talk to. How do I configure HW_INITIALIZATION_DATA, and how do I handle callbacks for the various routines to and from the scsi port driver. Thanks. Chuck xxxxx@usa.net PS - My DebugPrint()s don't show up on windbg.
  Message 5 of 5  
27 Jun 00 16:11
ntdev member 739
xxxxxx@starcomtec.com
Join Date:
Posts To This List: 12
Re: NT Fake out SCSI Miniport driver

The first step would be to let scsiport know that a device is attached to the controller. ScsiPort will only create Device Objects when SP_RETURN_FOUND is returned to a call to your HwFindAdapter routine. You also need to fill in the correct values in the structure PORT_CONFIGURATION_INFORMATION that is returned to the scsiport. Good Luck! Niraj > Chuck R wrote: > > I'm looking for information on, or sample code for, a fake out NT scsi > miniport driver. > > I need to know how to make it look like I have a bogus device hooked > up to a bogus HBA. I took the aha154x DDK sample and have it looking > like \Device\ScsiPort2 to NT, but I need to know how to get NT to > think there's a device attached that it can talk to. <...excess quoted lines suppressed...>
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 13:50.


Copyright ©2005, OSR Open Systems Resourcs, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license