• thisbenzingring@lemmy.sdf.org
    link
    fedilink
    arrow-up
    14
    ·
    6 hours ago

    well technically… USB initialization isn’t that simple, when you change which port it’s plugged into, it’s numerated under that new memory space, so from the computers perspective, it’s a different number, it’s a different device.

    • naeap@sopuli.xyz
      link
      fedilink
      arrow-up
      2
      ·
      2 hours ago

      Usually you have a vendor and a device id to identify the connected device on the bus

      You’re right though, that in every different port it will get its own memory allocated an so on (at least I also believe that), but that’s no reason to not identify the already known device

      • thisbenzingring@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        there are a couple IDs in the device manager, if you look closely you will see where it changes, and then search the registry for that string and you will find how crazy Windows can be with USB hardware. Actually stripping out those ID’s is a huge pain. I only know because of having to make legacy hardware work for work

        it was worse with USB1 and old drivers wouldn’t unload so then when you unplugged them and plugged them back in, sometimes they wouldn’t work unless you rebooted. Windows is stupid

    • garretble@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      5 hours ago

      Is that just obfuscated on other platforms (like MacOS)? I don’t think I’ve ever had a Mac get “confused” by a device by changing its port.