changing USB volume letter

[mauro]

Hi, I've made an USB stick detectable-handlable on OS2 W 4.52 (Virtualbox guest machine) with DFsee following the precious instructions received here.
Now I realized that the choosen drive letter (G) conflicts with the Shared Folder drive wich is G as well.  When plugged in, the USB volume functionality hangs after being automatically shifted to H letter, it remains locked and often make OS2 WPS not responding as well, so a letter change to a still unassigned drive letter appears to be the solution.
Can you suggest a way to just re-assign the USB volume letter avoiding the whole volume creation process in DFsee, that would wipe all data in it ?
Thank you

[Neil Waldhauer]

You can assign a drive letter without losing data by using Logical Volume Management (Simple) in the setup folder.

I think you can assign "None" and get the drive mounted with the next available letter.

I'm not sure how the assigned letter works for old Warp 4 systems, but I recall that it seems to ignore LVM and just mount the next available drive letter.

[mauro]

You can assign a drive letter without losing data by using Logical Volume Management (Simple) in the setup folder.

I think you can assign "None" and get the drive mounted with the next available letter.

I'm not sure how the assigned letter works for old Warp 4 systems, but I recall that it seems to ignore LVM and just mount the next available drive letter.

thank you Neil, I'll try.
I believed could also use DFsee as well but eventually needed some hint

[Lars]

DFSee: "change LVM info" and then set '*' (without the '') as the drive letter. That equivalents to driveletter = None = the next available drive letter.

That is how I set up ALL my USB sticks and drives/partitions in order to avoid a driveletter conflict.

As to my USBMSD.ADD that can also mount "large floppy" formatted USB sticks: it also always sets the drive letter of the "fake" volume that it creates (for the 'large floppy' formatted USB stick) to '*' so that it will never conflict with any already used drive letters.

[mauro]

done, thanks both of you.
Tell you the truth, some issue still persists and it is not a Shared Folder conflict matter, since I've kept it turned off while testing the USB functionality.
After opened the USB volume and worked with its contents, even only subfolders opening/closing, then the system shut-down often fails, I've to force the guest machine shut down from the VBox menu. Restarting it, the USB volume cannot be used, I've to do the CHKDSK /F to have it working again. It seems like WPS goes in trouble after having browsed the USB volume, even if everything appears ok during its use.

[ivan]

Just a thought, you did eject the usb stick before you removed it?  If you didn't that will cause the chkdsk problem you are seeing.

[mauro]

….mmmmh….. have to check this 

[mauro]

Just a thought, you did eject the usb stick before you removed it?  If you didn't that will cause the chkdsk problem you are seeing.

right, that was what needed.
Sorry   

[Valery Sedletski]

Also, you can try a shared folder "drive letter pinning" feature:

Just create a vboxfs.cfg file in your \os2\boot directory, with the following contents:

exch            e:
os2f             f:
valerius       m:

etc. So, format is "<shared_folder_name>     <drive_letter>:".
So, all specified shared folders will take a specified drive letter. So, you could assign them the way they will not conflict.