Do I need to write a driver for Win2K?

NTDEV
1

I’m trying to find out what the best (in my case, this equates to the
easiest) route is to support Win2K for our SCSI scanner and application. The
situation is this…

We produce a specialist SCSI scanner and the application software to drive
it. Currently this is hosted on NT4 and the application drives the scanner
by means of SCSI_PASS_THROUGH ioctl calls using NT4s scsiscan.sys driver.
This has worked fine for the last 3 years. Having looked through the Win2K
DDK documentation, I see that SCSI_PASS_THROUGH is still supported and so
I’m assuming that if I can get Win2K to recognise our scanner, then I can
continue to drive it in the same way. When Win2K boots up, it sees our
scanner and tries to find a driver for it, which of course it doesn’t find
because we don’t have one.

Is there a way to tell Win2K to just use the class driver as we did with
NT4?
Will this work?

I would obviously prefer not to have to drive the scanner differently on NT4
and Win2K as what we have at the moment works fine.

Thanks in advance for any help/advice you can give.

Steve Ford

2

You can create just an INF file to satisfy the request for a driver.
However, although SCSI_PASS_THROUGH is still supported on Win2K, the
security has been tightened. Basically you have to open for generic-read
and generic-write under Win2K. Depending upon how the system is setup,
average users may not have the appropriate security rights on the machine.

Good Luck,
-jjf

-----Original Message-----
From: Steve Ford [mailto:xxxxx@tecsa.com]
Sent: Monday, November 13, 2000 6:33 AM
To: NT Developers Interest List
Subject: [ntdev] Do I need to write a driver for Win2K?

I’m trying to find out what the best (in my case, this equates to the
easiest) route is to support Win2K for our SCSI scanner and application. The
situation is this…

We produce a specialist SCSI scanner and the application software to drive
it. Currently this is hosted on NT4 and the application drives the scanner
by means of SCSI_PASS_THROUGH ioctl calls using NT4s scsiscan.sys driver.
This has worked fine for the last 3 years. Having looked through the Win2K
DDK documentation, I see that SCSI_PASS_THROUGH is still supported and so
I’m assuming that if I can get Win2K to recognise our scanner, then I can
continue to drive it in the same way. When Win2K boots up, it sees our
scanner and tries to find a driver for it, which of course it doesn’t find
because we don’t have one.

Is there a way to tell Win2K to just use the class driver as we did with
NT4?
Will this work?

I would obviously prefer not to have to drive the scanner differently on NT4
and Win2K as what we have at the moment works fine.

Thanks in advance for any help/advice you can give.

Steve Ford

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

3

> You can create just an INF file to satisfy the request for a driver.

However, although SCSI_PASS_THROUGH is still supported on Win2K, the
security has been tightened. Basically you have to open for generic-read

Am I right that non-admin users could use the SPT interface on NT4?
The ACL on \Device\ScsiPort%d seem to permit this.

Max

4

Yes, though that wasn’t the case on some Win2K Betas. There is even a
knowledge base article to the contrary. When you think about it, SPT
probably shouldn’t be available to non-admins, but it apparently broke too
many things to close the security hole completely.

Regards,
-jjf

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, November 13, 2000 2:08 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Do I need to write a driver for Win2K?

You can create just an INF file to satisfy the request for a driver.
However, although SCSI_PASS_THROUGH is still supported on Win2K, the
security has been tightened. Basically you have to open for generic-read

Am I right that non-admin users could use the SPT interface on NT4?
The ACL on \Device\ScsiPort%d seem to permit this.

Max

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

5

Thanks for the reply. I had already tried going down this route by taking
the umax sample INF from the DDK but I have obviously not got the INF file
correct yet as it didn’t work, in that the scsiscan driver doesn’t seem to
be loaded on boot up Windows doesn’t say that it has found new hardware
again. Is there anything I should or shouldn’t have in there to make it
work? Do you know of an example I could base my file on?

Thanks,
Steve

-----Original Message-----
Subject: RE: Do I need to write a driver for Win2K?
From: “Fitzpatrick, Joe”
Date: Mon, 13 Nov 2000 11:52:57 -0800
X-Message-Number: 7

You can create just an INF file to satisfy the request for a driver.
However, although SCSI_PASS_THROUGH is still supported on Win2K, the
security has been tightened. Basically you have to open for generic-read
and generic-write under Win2K. Depending upon how the system is setup,
average users may not have the appropriate security rights on the machine.

Good Luck,
-jjf

-----Original Message-----
From: Steve Ford [mailto:xxxxx@tecsa.com]
Sent: Monday, November 13, 2000 6:33 AM
To: NT Developers Interest List
Subject: [ntdev] Do I need to write a driver for Win2K?

I’m trying to find out what the best (in my case, this equates to the
easiest) route is to support Win2K for our SCSI scanner and application. The
situation is this…

We produce a specialist SCSI scanner and the application software to drive
it. Currently this is hosted on NT4 and the application drives the scanner
by means of SCSI_PASS_THROUGH ioctl calls using NT4s scsiscan.sys driver.
This has worked fine for the last 3 years. Having looked through the Win2K
DDK documentation, I see that SCSI_PASS_THROUGH is still supported and so
I’m assuming that if I can get Win2K to recognise our scanner, then I can
continue to drive it in the same way. When Win2K boots up, it sees our
scanner and tries to find a driver for it, which of course it doesn’t find
because we don’t have one.

Is there a way to tell Win2K to just use the class driver as we did with
NT4?
Will this work?

I would obviously prefer not to have to drive the scanner differently on NT4
and Win2K as what we have at the moment works fine.

Thanks in advance for any help/advice you can give.

Steve Ford

6

> Yes, though that wasn’t the case on some Win2K Betas. There is even a

knowledge base article to the contrary. When you think about it, SPT
probably shouldn’t be available to non-admins, but it apparently broke too

What about the non-admin user sending the FORMAT UNIT CDB from one of the
Terminal Server’s terminals? It will even leave no traces of it :slight_smile:

Max

7

>-----Original Message-----

From: Steve Ford
>To: NT Developers Interest List
>Date: 13 November 2000 20:40
>Subject: [ntdev] Do I need to write a driver for Win2K?

>I’m trying to find out what the best (in my case, this equates to the
>easiest) route is to support Win2K for our SCSI scanner and application.
The
>situation is this…
>
>We produce a specialist SCSI scanner and the application software to drive
>it. Currently this is hosted on NT4 and the application drives the scanner
>by means of SCSI_PASS_THROUGH ioctl calls using NT4s scsiscan.sys driver.
>This has worked fine for the last 3 years. Having looked through the Win2K
>DDK documentation, I see that SCSI_PASS_THROUGH is still supported and so
>I’m assuming that if I can get Win2K to recognise our scanner, then I can
>continue to drive it in the same way. When Win2K boots up, it sees our
>scanner and tries to find a driver for it, which of course it doesn’t find
>because we don’t have one.
>
>Is there a way to tell Win2K to just use the class driver as we did with
>NT4?
>Will this work?
>
>I would obviously prefer not to have to drive the scanner differently on
NT4
>and Win2K as what we have at the moment works fine.
>
>Thanks in advance for any help/advice you can give.
>
>Steve Ford
>
>

Maybe you need. Because of it is looks like problem of connection(return
codes)
between your scsi - card driver(by manufacturer) and scsiscan.sys.
You need to look for
object Device\Scaner%d (by WinObj or else), it should be at you systems
after booting if scaner connected.
(By the way what does return function which get scaner device handle for
DeviceIO?)
If not simplest way - try to replace Win2k scsiscan with NT 4 scsiscan, and
keep in mind SFC.