Some of you may already have noticed that with multiple USB drives connected, the one that is recognized by uLE as the main mass: drive is not the same one as that accessed by older applications, which can only use a single drive. That drive will usually be one which uLE recognizes as mass1: (possibly higher number if you use a USB hub).

The reason for this is that the order of the USB device list received by USBHDFSD from the USBD module is different when these modules are loaded without a delay between them, compared to when they are loaded with a long delay between them. Most applications using USB do not have any such delay, but uLE by default does, as it loads USBD early for the USB keyboard support (by default enabled) and loads the USBHDFSD only when the user attempts to access a USB storage device (this method is needed for compatibility reasons).

The effect of this different drive order mapping may be that programs launched from mass: by uLE and needing to access files in their launch folder will be unable to do so, simply because the mass: drive they can access is a different physical device than the mass: drive that uLE launched the program from...

The developer of the multi-drive support for USBHDFSD, known as 'radad', is currently working on improvements that should make the drive mapping order independent of any delays, and also keep it compatible with the "mass:" mapping of old applications with embedded single-drive USB_mass drivers. And when this driver is available I plan to make a new uLE release to include it.

But if any of you need compatible mass: mapping directly, this can be achieved simply by changing the configuration flag "Configure"/"Startup Settings..."/"USB Keyboard Used:" from the default "ON" state to "OFF", and then save settings as usual. This will make the mass: drive mapping compatible to old applications in future uLE boot sessions. And the only drawback is that you can not then use a USB keyboard.

Best regards: dlanor