INF file for scsiscan

NTDEV
1

Following on from a previous posting I made, I was told that with an
appropriate INF file I should be able to get Windows 2000’s scsiscan.sys to
load so that I can use SCSI_PASSTHROUGH calls from my application. Having
never written an INF file before, can anybody tell me what I need to put in
it to get it to work? Or does somebody already have such a file?

Thanks
Steve Ford

2

If yours was the post on how to do an INF file to satisfy Win2000 without
writing a driver, the INF file below should be pretty close to what you
need. The really critical line is:

%DeviceDesc%=SDUMMY.Dev, SCSI\NetXXI_____XXI_2000________5.0_

The line after the comma must be changed to match your device’s hardware ID.
This can be a little tricky to figure out for some SCSI devices. It is
probably easiest to attach your device, go to the device manager, and select
scan. When you are prompted for a driver, hit cancel. You will be
installed as an ‘unknown’ device in the registry. If you know your
manufacturer or product ID, search the registry with RegEdit. One of the
created keys is hardware ID. It will be in Unicode, but you can pretty
easily extract the ASCII line (like above) from the dump view regedit shows.

Good Luck,
-jjf

****** Sample INF for SCSI device, no class driver ******

[Version]
Signature=“$CHICAGO$”
Class=Image
provider=%MfgName%
LayoutFile=layout.inf

[SourceDisksNames]
1=“Some Product Installation Disk”,

[SourceDisksFiles]
SDUMMY.inf = 1

[SourceDiskFiles]
SDUMMY.inf = 1

[Manufacturer]
%MfgName%=MyProduct

[MyProduct]
%DeviceDesc%=SDUMMY.Dev, SCSI\NetXXI_____XXI_2000________5.0_

[PreCopySection]
HKR,NoSetupUI,1

[DestinationDirs]
SDUMMY.Files.Inf = 10,INF

[SDUMMY.Dev]
CopyFiles=SDUMMY.Files.Inf
AddReg=SDUMMY.AddReg

[SDUMMY.Dev.NT]
CopyFiles=SDUMMY.Files.Inf
AddReg=SDUMMY.AddReg

[SDUMMY.AddReg]
HKR,DevLoader,*ntkern

[SDUMMY.Files.Inf]
SDUMMY.inf

;---------------------------------------------------------------;

[Strings]
MfgName=“My Company”
DeviceDesc=“Some Product”

-----Original Message-----
From: Steve Ford [mailto:xxxxx@tecsa.com]
Sent: Monday, November 20, 2000 2:28 AM
To: NT Developers Interest List
Subject: [ntdev] INF file for scsiscan

Following on from a previous posting I made, I was told that with an
appropriate INF file I should be able to get Windows 2000’s scsiscan.sys to
load so that I can use SCSI_PASSTHROUGH calls from my application. Having
never written an INF file before, can anybody tell me what I need to put in
it to get it to work? Or does somebody already have such a file?

Thanks
Steve Ford

You are currently subscribed to ntdev as: xxxxx@eTree.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

Joe,

Thank you for your help once again, I’ve finally had time to try the INF
file you gave and it works fine. I’m still a bit confused though…

To access the device from my application, I now have to open a device called
\.\ScsiN rather than \.\ScannerN as I do when running in NT4. I guess this
is because the device hasn’t been “claimed” by scsiscan? Is this a
limitation I’m going to have to live with because of the way I want to drive
my scanner, or is there also some way to make scsiscan start up and claim
the device and hence create the link to \.\ScannerN?

Thanks again,
Steve

-----Original Message-----
Subject: RE: INF file for scsiscan
From: “Fitzpatrick, Joe”
>Date: Mon, 20 Nov 2000 17:00:21 -0800
>X-Message-Number: 13
>
>If yours was the post on how to do an INF file to satisfy Win2000 without
>writing a driver, the INF file below should be pretty close to what you
>need. The really critical line is:
>
>%DeviceDesc%=SDUMMY.Dev, SCSI\NetXXI XXI_2000___ 5.0_
>
>The line after the comma must be changed to match your device’s hardware
ID.
>This can be a little tricky to figure out for some SCSI devices. It is
>probably easiest to attach your device, go to the device manager, and
select
>scan. When you are prompted for a driver, hit cancel. You will be
>installed as an ‘unknown’ device in the registry. If you know your
>manufacturer or product ID, search the registry with RegEdit. One of the
>created keys is hardware ID. It will be in Unicode, but you can pretty
>easily extract the ASCII line (like above) from the dump view regedit
shows.
>
>Good Luck,
>-jjf