• windpunch@feddit.org
    link
    fedilink
    arrow-up
    36
    ·
    20 hours ago

    “There’s a problem with your USB storage device”

    *Continues to work just fine, just as if there is no problem*

  • garretble@lemmy.world
    link
    fedilink
    English
    arrow-up
    47
    ·
    21 hours ago

    Windows is great because if you plug your mouse into one USB port then maybe you move the mouse to another, it completely forgets that mouse ever existed and is like “setting up device!”

    Bro, you know what this is.

    • muhyb@programming.dev
      link
      fedilink
      arrow-up
      34
      ·
      21 hours ago

      It sure is great. If I remember correctly, there was a Windows 95 error saying “keyboard not found, press F2 to continue.”

      • macniel@feddit.org
        link
        fedilink
        arrow-up
        23
        ·
        19 hours ago

        No it wasn’t just win95 but also IBM DOS and BIOS.

        Keyboard not found, press F2 to continue asks the users to either plug in a keyboard and the press F2 on that one to continue or press F2 on an unrecognised keyboard so that the OS could pick it up.

        It would then reload the driver’s for the PS/2 keyboard and continue as normal.

    • thisbenzingring@lemmy.sdf.org
      link
      fedilink
      arrow-up
      17
      ·
      21 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.

      • garretble@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        20 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.

      • naeap@sopuli.xyz
        link
        fedilink
        arrow-up
        3
        ·
        17 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
          2
          ·
          17 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

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      20 hours ago

      That’s very unlikely to happen. Once the driver is installed via Windows update it doesn’t magically uninstall itself.