Maybe because it already exists. The Volume{GUI} mapping to unique id
already exists and unique id is same as previous time.
I don’t know why the volume would not be mounted again.
Harish
From: Haibo [mailto:xxxxx@hotmail.com]
Sent: Thursday, May 07, 2009 1:31 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Question about
IOCTL_MOUNTMGR_VOLUME_ARRIVAL_NOTIFICATION
No one knows?
Regards
Haibo
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Haibo
Sent: Wednesday, May 06, 2009 10:51 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Question about
IOCTL_MOUNTMGR_VOLUME_ARRIVAL_NOTIFICATION
Hi all:
I send IOCTL_MOUNTMGR_VOLUME_ARRIVAL_NOTIFICATION to mountmgr
to mount a new volume, it woks well and a drive letter is assigned. Then
I use IOCTL_MOUNTMGR_DELETE_POINTS (NULL, NULL, “\Device\MyVol”) to
remove all sym links and SUCCESS is returned. But when I call
IOCTL_MOUNTMGR_VOLUME_ARRIVAL_NOTIFICATION to mount it again the volume
is not mounted. I notice that the volume name Volume{GUID} is not
generated. Who knows why?
Regards
Haibo
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer