Yes, you understood the problem correctly, the device belongs to the
category of removable devices.
But we do have persistent drive letters for CD/DVD etc, right? and they too
are in the removable category.
My file system driver(which actually is just a kernel interface, having no
underlying device) creates the device object by specifying the device type
as FILE_DEVICE_DISK_FILE_SYSTEM. This device object is later used to create
the drive letter, via Definedosdevices.
Thanks,
Swati
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Kiran Joshi
Sent: Tuesday, August 17, 2004 2:41 PM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Updating an FSD to use the Mount Manager interface
I am not sure whether I understand your problem correctly, but what I
understand is that you have removable device and you want to make drive
letter persistent for such a device, which I feel is conceptually wrong.
Besides what is the type of device object that you are creating ?
-Kiran
“Swati” wrote in message news:xxxxx@ntfsd…
> Hello everyone…
>
> can somebody pls help me with this PDO issue…
>
> Rgds,
> Swati
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Swati
> Sent: Tuesday, August 10, 2004 2:13 PM
> To: Windows File Systems Devs Interest List
> Subject: RE: [ntfsd] Updating an FSD to use the Mount Manager interface
>
>
>
> Hello Maxim,
>
> Actually I’m manipulating a file system driver (which actually is a kernel
> interface to the O.S that was written for a jukebox) to support standalone
> removable drives now. The communication mechanism in the existing code is
> very different from how windows file systems are written. There is no
> concept of a stack. Any operation on the mounted disk is intercepted by
the
> file system driver and sent to the user land (where the real file systems
> are) via some communication mechanism, which finally issues SCSI commands
to
> the jukebox SCSI class driver.
>
> The drive creation right now is via Definedosdevices and so it’s not
> persistent. I read in the archive that it’s possible to make the drive
> letter persistent without actually having a PDO…
>
> Please suggest!
>
> Thanks,
> Swati
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> Sent: Friday, August 06, 2004 6:23 PM
> To: Windows File Systems Devs Interest List
> Subject: Re: [ntfsd] Updating an FSD to use the Mount Manager interface
>
>
> Sorry, but what is your FSD? On-disk FSD? Then you already have a disk
> device below you.
>
> Or is it the redirector? Then why Mount Manager? redirectors have
> nothing
> to do with the Mount Manager.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> ----- Original Message -----
> From: “Swati”
> To: “Windows File Systems Devs Interest List”
> Sent: Friday, August 06, 2004 4:21 PM
> Subject: RE: [ntfsd] Updating an FSD to use the Mount Manager interface
>
>
> > Hello Maxim,
> >
> > As you mentioned, I have used IoReportDetectedDevice to create the
Virtual
> > PDO. And then to interface with the Mount Manager, I have registerd
using
> > IoRegisterDeviceInterface using the MOUNTDEV_MOUNTED_DEVICE_GUID
> identifier.
> > Also I have supported the IOCTL_MOUNTDEV_QUERY_DEVICE_NAME and
> > IOCTL_MOUNTDEV_QUERY_UNIQUE_ID in my driver.
> >
> > But what I found is, the above mentioned IOCTLs are not being called by
> the
> > Mount manager (by putting debug prints).Can anybody please tell me why
is
> it
> > happening?
> >
> > The driver gets loaded at boot time and I am getting the “Found new
> Hardware
> > Wizard” at startup. It is trying to install an “Unknown” Device, but
> doesn’t
> > find the driver to install. Why is it so?
> >
> > Any help is appreciated!
> >
> > Thanks,
> > Swati Chawdhary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Swati
> > Sent: Thursday, August 05, 2004 6:48 PM
> > To: Windows File Systems Devs Interest List
> > Subject: RE: [ntfsd] Updating an FSD to use the Mount Manager interface
> >
> >
> > Thanks Maxim.
> >
> > I was successfully able to create a valid virtual PDO from my legacy fsd
> > driver(however, the Add new hardware wizard came after the PDO was
> created),
> > now i’m writing the code to respond to the IOCTLs sent by the Mount
> > Manager(as the drive was not registered with the mount manager).
> >
> > Rgds,
> > Swati Chawdhary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> > Sent: Wednesday, August 04, 2004 8:05 PM
> > To: Windows File Systems Devs Interest List
> > Subject: Re: [ntfsd] Updating an FSD to use the Mount Manager interface
> >
> >
> > IoReportDetectedDevice with lots of NULLs and zeroes in parameters
> will
> > create the Virtual PDO.
> >
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > xxxxx@storagecraft.com
> > http://www.storagecraft.com
> >
> > ----- Original Message -----
> > From: “Swati”
> > To: “Windows File Systems Devs Interest List”
> > Sent: Wednesday, August 04, 2004 6:29 PM
> > Subject: [ntfsd] Updating an FSD to use the Mount Manager interface
> >
> >
> > > Hello Everybody,
> > >
> > > I’m updating an FSD to use the Mount Manager interface for drive
letters
> > > rather than hammering a symbolic link
> > > into \??.
> > >
> > > Is there any way to interface with the Mount Manager via
> > > IoRegisterDeviceInterface() without having a PDO?
> > > As an alternative question, is there any way a legacy driver can
> generate
> > a
> > > PDO (other than IoReportDetectedDevice)?
> > >
> > > A similar query was answered by the list, that one need’s to create a
> > > “Virtual PDO” and has to handle the several mount-related IOCTLs that
> the
> > > Mount Manager will send on the device object.
> > >
> > > What is a Virtual PDO? How to create it? I tried passing my device
> object
> > to
> > > IoRegisterDeviceInterfac to register it, it returns with an error that
> the
> > > deviceObject is not a valid PDO pointer.
> > >
> > > Please help!
> > >
> > > Thanks,
> > > Swati Chawdhary
> > >
> > >
> > > —
> > > Questions? First check the IFS FAQ at
> > https://www.osronline.com/article.cfm?id=17
> > >
> > > You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> > —
> > Questions? First check the IFS FAQ at
> > https://www.osronline.com/article.cfm?id=17
> >
> > You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> > —
> > Questions? First check the IFS FAQ at
> > https://www.osronline.com/article.cfm?id=17
> >
> > You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> > —
> > Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
> >
> > You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@tataelxsi.co.in
To unsubscribe send a blank email to xxxxx@lists.osr.com