Also tested with 152 Exp.
Wanderer & magellan don't actively crash, just silently.
But when you disable the usb sticks from vbox, the usb stack also removes them from aros (incl. requester). So that part *is* working.

Poseidon in fact does distinguish between identical USB devices (there is a field called clone-count, that increases for duplicate devices which is also part of the internal ID-string). This ID-string is used by the massstorage.class (AFAIR) to assign the entities and configs.

It also bumps the mount names on A68k at least. Amiga DOS file systems did distinguish multiple instances when the Volume name is identical, but I've got no idea what the issue is on AROS.

Smashing! x303

I haven't tried that yet, thx for the heads up.

Wierd, if i boot from pendrive and insert the 'same' pendrive then no error occurs. Poseidon simply 'mounts' it, but there is simply no way to access the 2nd pendrive.

The error you got seems a little more damaging :/

Looks like the usb driver only looks at the name and not for a unique id number. If I connect 2 usb sticks with the same name (with vbox), after 'mounting' the second one, wanderer crashes. See pic.

Attach file:

---

  (0.00 KB)

Hi,

Now that i have acumulated some pendrives, i am starting to notice that AROS is incapable of distinguishing the same pendrives (in brand and model-type).

The 'problems' that arise from that are probably obvious and becomes a pita when both devices are using the exact same volume names. For instance when i want to copy something from a nightly onto another nightly (but of different date) then there is currently no way to be able to do that (when i use two pendrives of same model/type).

The info command also does not seem to notice the difference.

Is there a 'workaround' for this particular issue (other then telling me to use another brand/type pendrive or use another type of device) ?