Override disk.sys in Win2000

Hi All,

I want to use my driver in place of disk.sys for certain type of optical
disks, based on Vendor/Product ID information. Am using SetupDI API’s like
SetupCopyOEMInf, UpdateDriverForPlugAndPlayDevices for changing the disk.sys
service to my own service(swati_opt.sys) on my optical disk.

The problem is PnP enumeration, which always chooses disk.sys for PDOs that
are enumerated as type GenericDisk, ScsiDisk, etc. Whenever PnP detects the
device it always loads disk.sys first then unloads disk.sys and loads any
other driver.

Has anyone else tried this before? Any solution to this problem? Please
help…

Thanks in Advance.
Regards,
Swati

On Thu, 28 Oct 2004 19:40:43 +0530, Swati Chawdhary wrote:

I guess I fail to see the problem. If your driver is ultimately being
loaded and used why does it matter? Is there something specific you’re
trying to do when the device is initially detected by PnP? Once your
device configuration is complete the system should use your driver for the
device on subsequent reboots.

Bob

Hi All,

I want to use my driver in place of disk.sys for certain type of optical
disks, based on Vendor/Product ID information. Am using SetupDI API’s like
SetupCopyOEMInf, UpdateDriverForPlugAndPlayDevices for changing the disk.sys
service to my own service(swati_opt.sys) on my optical disk.

The problem is PnP enumeration, which always chooses disk.sys for PDOs that
are enumerated as type GenericDisk, ScsiDisk, etc. Whenever PnP detects the
device it always loads disk.sys first then unloads disk.sys and loads any
other driver.

Has anyone else tried this before? Any solution to this problem? Please
help…

Thanks in Advance.
Regards,
Swati

Why not you can use your own class GUID for the device
so that your driver will be loaded instead of disk
class driver?

— Swati Chawdhary wrote:

> Hi All,
>
> I want to use my driver in place of disk.sys for
> certain type of optical
> disks, based on Vendor/Product ID information. Am
> using SetupDI API’s like
> SetupCopyOEMInf, UpdateDriverForPlugAndPlayDevices
> for changing the disk.sys
> service to my own service(swati_opt.sys) on my
> optical disk.
>
> The problem is PnP enumeration, which always chooses
> disk.sys for PDOs that
> are enumerated as type GenericDisk, ScsiDisk, etc.
> Whenever PnP detects the
> device it always loads disk.sys first then unloads
> disk.sys and loads any
> other driver.
>
> Has anyone else tried this before? Any solution to
> this problem? Please
> help…
>
> Thanks in Advance.
> Regards,
> Swati
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail

Bob,

You are correct that once our device configuration is complete the system
uses our driver only for our optical device on subsequent reboots. The
problem is when the device is detected for the first time and disk.sys
loads, it takes control of our optical disk, and the system crashes
immediately with a BLUE SCREEN :frowning:

Rgds,
Swati

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Robert Stankey
Sent: Friday, October 29, 2004 12:26 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Override disk.sys in Win2000

On Thu, 28 Oct 2004 19:40:43 +0530, Swati Chawdhary wrote:

I guess I fail to see the problem. If your driver is ultimately being
loaded and used why does it matter? Is there something specific you’re
trying to do when the device is initially detected by PnP? Once your
device configuration is complete the system should use your driver for the
device on subsequent reboots.

Bob

Hi All,

I want to use my driver in place of disk.sys for certain type of optical
disks, based on Vendor/Product ID information. Am using SetupDI API’s like
SetupCopyOEMInf, UpdateDriverForPlugAndPlayDevices for changing the
disk.sys
service to my own service(swati_opt.sys) on my optical disk.

The problem is PnP enumeration, which always chooses disk.sys for PDOs
that
are enumerated as type GenericDisk, ScsiDisk, etc. Whenever PnP detects
the
device it always loads disk.sys first then unloads disk.sys and loads any
other driver.

Has anyone else tried this before? Any solution to this problem? Please
help…

Thanks in Advance.
Regards,
Swati


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

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

Sorry for expressing a maybe both already considered and somewhat
impossible opinion, but here goes:

So, if your device really need a different driver than the default one,
maybe you should make sure that the default disk.sys doesn’t at all
communicate with your device, by making it have a PnP profile which
prevents the PnP system from associating disk.sys with your device.

Of course, I’m by no means an expert on file system and disk drivers. But
not knowing things have never stopped me from expressing an opinion :wink:


Mats

xxxxx@lists.osr.com wrote on 10/29/2004 12:17:38 PM:

Bob,

You are correct that once our device configuration is complete the system
uses our driver only for our optical device on subsequent reboots. The
problem is when the device is detected for the first time and disk.sys
loads, it takes control of our optical disk, and the system crashes
immediately with a BLUE SCREEN :frowning:

Rgds,
Swati

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Robert Stankey
Sent: Friday, October 29, 2004 12:26 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Override disk.sys in Win2000

On Thu, 28 Oct 2004 19:40:43 +0530, Swati Chawdhary wrote:

I guess I fail to see the problem. If your driver is ultimately being
loaded and used why does it matter? Is there something specific you’re
trying to do when the device is initially detected by PnP? Once your
device configuration is complete the system should use your driver for
the
device on subsequent reboots.

Bob

> Hi All,
>
> I want to use my driver in place of disk.sys for certain type of
optical
> disks, based on Vendor/Product ID information. Am using SetupDI API’s
like
> SetupCopyOEMInf, UpdateDriverForPlugAndPlayDevices for changing the
disk.sys
> service to my own service(swati_opt.sys) on my optical disk.
>
> The problem is PnP enumeration, which always chooses disk.sys for PDOs
that
> are enumerated as type GenericDisk, ScsiDisk, etc. Whenever PnP detects
the
> device it always loads disk.sys first then unloads disk.sys and loads
any
> other driver.
>
> Has anyone else tried this before? Any solution to this problem? Please
> help…
>
> Thanks in Advance.
> Regards,
> Swati


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

You are currently subscribed to ntdev as: xxxxx@tataelxsi.co.in
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@3dlabs.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

ForwardSourceID:NT000065DE

Disk should be able to run just about any direct access device,
including worm devices. If you’re experiencing a crash then there’s
either a bug that needs fixed or your device shouldn’t be reporting
itself as a direct-access device.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Swati Chawdhary
Sent: Friday, October 29, 2004 4:18 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Override disk.sys in Win2000

Bob,

You are correct that once our device configuration is
complete the system uses our driver only for our optical
device on subsequent reboots. The problem is when the device
is detected for the first time and disk.sys loads, it takes
control of our optical disk, and the system crashes
immediately with a BLUE SCREEN :frowning:

Rgds,
Swati

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Robert Stankey
Sent: Friday, October 29, 2004 12:26 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Override disk.sys in Win2000

On Thu, 28 Oct 2004 19:40:43 +0530, Swati Chawdhary wrote:

I guess I fail to see the problem. If your driver is
ultimately being loaded and used why does it matter? Is
there something specific you’re trying to do when the device
is initially detected by PnP? Once your device configuration
is complete the system should use your driver for the device
on subsequent reboots.

Bob

> Hi All,
>
> I want to use my driver in place of disk.sys for certain type of
> optical disks, based on Vendor/Product ID information. Am using
> SetupDI API’s like SetupCopyOEMInf,
UpdateDriverForPlugAndPlayDevices
> for changing the
disk.sys
> service to my own service(swati_opt.sys) on my optical disk.
>
> The problem is PnP enumeration, which always chooses
disk.sys for PDOs
that
> are enumerated as type GenericDisk, ScsiDisk, etc. Whenever PnP
> detects
the
> device it always loads disk.sys first then unloads disk.sys
and loads
> any other driver.
>
> Has anyone else tried this before? Any solution to this problem?
> Please help…
>
> Thanks in Advance.
> Regards,
> Swati


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

You are currently subscribed to ntdev as:
xxxxx@tataelxsi.co.in 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@windows.microsoft.com To unsubscribe send a blank
email to xxxxx@lists.osr.com

On Fri, 29 Oct 2004 16:47:38 +0530, Swati Chawdhary wrote:

Swati,

Can you tell us what the exact bugcheck message is?

Robert,

Actually, the media in the drive is not supported by windows file
system(basically the sector size), we are having our own class driver and
want somehow to prevent disk.sys from loading in the very first instance.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Robert Stankey
Sent: Wednesday, November 03, 2004 2:43 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Override disk.sys in Win2000

On Fri, 29 Oct 2004 16:47:38 +0530, Swati Chawdhary wrote:

Swati,

Can you tell us what the exact bugcheck message is?


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

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