G
Guest
Hello,
Here are my drives (logical & physical) configruation in a generic Windows
XP image under development :
- C (HDD)
- D (CD/DVD-ROM)
- E SUBST of C:\Program files (for historic business purposes) that mustn't
be changed.
People will use USB Cameras and sticks so when U plug a USB device letter E
will automatically be affected and current E will go mad ;-)
I found the software (freeware ?) USBDLM
(http://www.uwe-sieber.de/usbdlm_e.html) that suits my need and allows
enforcement of a scope of drive letters that can/can not be affected to the
USB connection.
My question is : the developper of that great (and unique) might know how to
interceed USB insertion calls, and therefor use windows functions. Thus, I
couldn't find any clear solution that which, I guess, we are thousands of
users to share.
Is there any serious tip apart from using Disk Manager and that can be
applied to ANY type of USB storage devices so that drive letters affectable
can be handled ?
Thanks a lot to anyone that could provide a way to solve this real XP issue
without compromising system steadiness
Here are my drives (logical & physical) configruation in a generic Windows
XP image under development :
- C (HDD)
- D (CD/DVD-ROM)
- E SUBST of C:\Program files (for historic business purposes) that mustn't
be changed.
People will use USB Cameras and sticks so when U plug a USB device letter E
will automatically be affected and current E will go mad ;-)
I found the software (freeware ?) USBDLM
(http://www.uwe-sieber.de/usbdlm_e.html) that suits my need and allows
enforcement of a scope of drive letters that can/can not be affected to the
USB connection.
My question is : the developper of that great (and unique) might know how to
interceed USB insertion calls, and therefor use windows functions. Thus, I
couldn't find any clear solution that which, I guess, we are thousands of
users to share.
Is there any serious tip apart from using Disk Manager and that can be
applied to ANY type of USB storage devices so that drive letters affectable
can be handled ?
Thanks a lot to anyone that could provide a way to solve this real XP issue
without compromising system steadiness