Re: bug in Win-XP-Pro with flash-drive and subst

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes, I pretty much expected that the problem was not unique to SUBST.

To me, the question is 'do they ever plan to FIX it?'

(Ya gotta love M$...they have a reputation of declaring such things
a feature rather than a bug. It's only a bug if THEY say it is. Sigh.)

Dave


"Pavel" <Atin90@xxxxxxxxxxx> wrote in message
news:%23XdLm35QFHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
> So that you know, this is not a unique problem to SUBST. Same situation
> arises when any type of device, which uses a drive letter that is assigned
> trough the use of Disk manager. While such device is active there is a
> drive letter and no drive letter when such device is unplugged. If you now
> create a mapped drive that uses same drive letter and then enable (plug it
> in) the original device, only the mapped drive will be shown.
>
> --
> Pavel
>
>
> "David Cook" <someone@xxxxxxxxxxx> wrote in message
> news:RbGdnQd5cpzdRf_fRVn-1w@xxxxxxxxxxxxxx
>> There seems to be a bug in Win-XP Pro (SP2), when drive-letter
>> to be assigned to a hot-plugged flash-drive collides with the same-letter
>> assigned to a SUBSTituted drive.
>>
>> Steps to reproduce:
>>
>> (1)Hot-plug a flash-drive into a USB-port. Let's say the device
>> gets assigned the letter E: This works normally and the flash-drive
>> works fine. (My flash-drive happens to be a Lexar Media 'Jump-drive'
>> that is 128-MB in size.)
>>
>> (2)Un-plug that flash-drive, so that the letter E: is no longer visible
>> in the
>> file-explorer as an assigned drive letter.
>>
>> (3)Now create a cmd-script (e.g. named 'login.cmd') that contains the
>> command:
>> subst E: C:\
>> and create a shortcut for cmd-window. In the 'target' for that
>> cmd-window
>> shortcut, append the cmd-line switch:
>> /k login.cmd
>> so that this script gets run anytime that this cmd-window is launched.
>>
>> (4)Move that shortcut into the user's 'startup' group (so that now the E:
>> drive will get created (via the SUBST cmd) when the user logs in.
>>
>> (5)Now, once this logged-in user ever subsequently tries to insert this
>> flash-drive into a USB-port, the system will NOW no longer make the
>> flash-drive accessible. It seems to have 'remembered' E: so rather than
>> assign the next available drive-letter (e.g. F:) to the flash-drive, it
>> instead ERRONEOUSLY tries to re-claim E: as its drive-letter.
>> (Code-stream seems to execute partially...the drive E: seems to
>> erroneously get its 'type' changed from 'local drive' to 'removable
>> drive',
>> but the drive E: correctly retains its mapping to C:\ (since the SUBST
>> is still in effect).
>>
>> However, the flash-drive is NOW not accessible. I can find no workaround
>> or method to get the flash-drive to mount for that user. (Other than to
>> remove the SUBST and use some OTHER drive-letter for the SUBST.)
>> [Using a different-drive letter for the SUBST is not desireable, as other
>> external scripts on the groups development-server would have to be
>> changed.]
>>
>> [Is this earlier erroneously remembered claiming of drive E: being
>> remembered
>> in the registry somewhere? If so, then maybe deleting that registry
>> entry would workaround this problem?]
>>
>> Regards...
>>
>> Dave
>>
>
>


.

Relevant Pages

  • Re: bug in Win-XP-Pro with flash-drive and subst
    ... this is not a unique problem to SUBST. ... letter and no drive letter when such device is unplugged. ... > and create a shortcut for cmd-window. ...
    (microsoft.public.windowsxp.general)
  • Re: Conflict between Substd drive and USB storage devices
    ... I use subst to map the G: ... >assigns the drive letter that subst is using to the external device. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: DCOM objects not found & Sharing error on SUBST drive
    ... Thanks again, Roger. ... the sefvice is not using some hard coded drive letter. ... only on my development environment: I run and test several versions of the ... same system, and to swap versions I run it from a SUBST drive, and change ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Suspicious Undeletable File
    ... then you can use the SUBST command at a cmd prompt to get ... cd to the drive letter you selected to use and try deleting using ... > Chaos Shredder and Simple File Shredder programs. ...
    (microsoft.public.security)
  • Re: User immediatly logs off after entering username and password
    ... If the laptop is part of a network you can access it and modify the registry by one of the means mentioned in this article: ... Your problem might be caused by a boot drive letter change but I kind of doubt that that is the problem, nonetheless it's easy enough to verify and eliminate that possibility. ... As I already mentioned, I rather doubt that your problem is drive letter related, I think that this looks like yet another one of those pests that changes the userinit value at the Winlogon key in the registry. ...
    (microsoft.public.windowsxp.help_and_support)