I would say that your just lucky. NT “likes” to remember disks across
reboots. You should always use the same id if the disk is the same. If
the disk size changes, then you have to decide; is this the same disk, just
bigger (note: basic disks can be extended in windows 2000) or is this a new
disk with a different format? I use UUID’s to uniquely identify the disks,
I can’t remember what I use to uniquely identify virtual Cdroms (iso files).
–Mark
-----Original Message-----
From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
Sent: Monday, July 02, 2001 9:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Virtual disk with a bus enumerator (SRB_FUNCTION_- -
CLAIM_DEVICE) ?
BTW, the signature comes back as part of the IOCTL_STORAGE_QUERY_PROPERTY
StorageDeviceProperty call. Be sure that each of your disks has a unique
ID, i.e signature…
I just generate for device ID the string with the index of the device.
Like
“StarDisk %d on StarPort Controller”. So the disk numbers are unique. But
they are not across boots. And the disks with the same names can have
different sizes if they are created/destroyed. I mean I can create
“StarDisk 0” with 10 megabytes in size, use it, destroy and create
“StarDisk 0” with 100 megabytes in size. It works for me now… Is this OK
or I’m just lucky?
You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi,
Will it be a good idea just create random name for every disk drive
inserted to the system? Do not care was this disk inserted before or no?
Where do you supply your UUIDs? In drive or vendor name when you’re
reporting to IOCTL_STORAGE_QUERY_PROPERTY( DeviceProperty ) I guesss?
Regards,
Anton
On 07/03/01, “Mark Cariddi ” wrote:
> I would say that your just lucky. NT “likes” to remember disks across
> reboots. You should always use the same id if the disk is the same. If
> the disk size changes, then you have to decide; is this the same disk, just
> bigger (note: basic disks can be extended in windows 2000) or is this a new
> disk with a different format? I use UUID’s to uniquely identify the disks,
> I can’t remember what I use to uniquely identify virtual Cdroms (iso files).
>
> --Mark
>
>
>
> -----Original Message-----
> From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
>
> Sent: Monday, July 02, 2001 9:00 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Virtual disk with a bus enumerator (SRB_FUNCTION_- -
> CLAIM_DEVICE) ?
>
>
> > BTW, the signature comes back as part of the IOCTL_STORAGE_QUERY_PROPERTY
> > StorageDeviceProperty call. Be sure that each of your disks has a unique
> > ID, i.e signature…
>
> I just generate for device ID the string with the index of the device.
> Like
> “StarDisk %d on StarPort Controller”. So the disk numbers are unique. But
> they are not across boots. And the disks with the same names can have
> different sizes if they are created/destroyed. I mean I can create
> “StarDisk 0” with 10 megabytes in size, use it, destroy and create
> “StarDisk 0” with 100 megabytes in size. It works for me now… Is this OK
> or I’m just lucky?
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@osr.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com