RE: RE: Re: RE: RE: RE:*** Vista RTM *** Writing to raw disk sectors (Unsigned Mail)

NTDEV
1

Actually what is going to be needed is an “altitude” rating system for storage stack device drivers…

Just curious, does your driver directly write to the disk or do you send it “down the stack” ?

–

EA

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-277105-
xxxxx@lists.osr.com] On Behalf Of xxxxx@stg.com
Sent: jeudi 1 février 2007 19:28
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] RE: Re: RE: RE: RE:*** Vista RTM *** Writing to raw
disk sectors (Unsigned Mail)

Edouard A. said:
> Another theory would be that you would have to be below the partition
manager,

This idea works for a sample driver that I hacked up.
When I insert my driver before PartMgr in UpperFilters for Disk.sys, my
IRP_MJ_WRITE requests succeed.
When I append my driver after PartMgr in UpperFilters for Disk.sys, my
IRP_MJ_WRITE requests fail.

In XP & 2K, IRP_MJ_WRITE requests always succeeded, no matter what
order you are placed in UpperFilters.

Next, I need to see if loading below PartMgr causes other unexpected
problems for my driver. I’m sure that always pre-pending to
UpperFilters can potentially cause incompatibilities between my driver
and others though. How are other people handling the order they insert
themselves in UpperFilters for Disk.sys?

Thanks,
–Steve

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

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer