Don
Mon Jul 31 12:07:08 CDT 2006
I would strongly recomend you reconsider your approach, for the following
reasons:
1. The SCSI port driver interface is undocumented, and subject to
change.
2. Two firms offer SCSI port drivers, OSR and StorageCraft. They
charge big bucks (over $100,000) for these.
3. Even if you get the driver working, supporting Microsoft drivers
above this such as MPIO require lots of tweaking, since the upper drivers
expect certain error codes and only those codes, etc.
4. Microsoft has a new policy and will shortly no longer WHQL a SCSI
port driver, so you will not have signed code which will limit the sales of
your device.
If you can look at the Virtual Storport efforts Microsoft is currently
beta'ing. This may allow you enough flexibility to handle what you need.
If not, reengineer your device to not need a custom Port driver it will be
cheaper.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
"vs" <windrv@gmail.com> wrote in message
news:1154364834.569779.150840@i42g2000cwa.googlegroups.com...
> Hi All,
>
> I need to write a bus driver for a customer storage controller chip. I
> cannot use the SCSIPORT model as the enumeration of the devices is very
> specific and I feel writing a bus driver will provide me the most
> flexibility to do this. I am trying to decide between using the WDM and
> KMDF framework for writing this driver. From KMDF documentation I could
> not figure out what the framework entry point will be for IRP_MJ_SCSI.
> Is it possible to do this storage bus driver using KMDF?
>
> vs
>