while i doubt it will actually work, if it does, it would be quite hilarious in my opinion. there’s probably, hopefully, safeguards that prevent such a thing from working and i likely have the syntax wrong, i haven’t used windows in years.
There are USB headers, PCI(-E) slots, SATA and some older ones. To get storage devices working on each one you will need a different driver.
Windows disabled autorun for USB sticks before win10.
Also if you list the devices on Linux they will show up as sd(a, b, c…) for SSDs, hd(a, b, c…) for HDDs and nvmen(0,1,2…) for NVMe drives. So yes the OS must be able to differentiate.
Windows assigning letters is just weird IMO.
Also to my knowledge the floppy would show up as disk A on Windows.
just in case someone sticks it in a working drive, add a file to the floppy named
and add the following to it with a text editor:
[autorun] open=Microsoft.Media.Player.exe icon=icon.icowhile i doubt it will actually work, if it does, it would be quite hilarious in my opinion. there’s probably, hopefully, safeguards that prevent such a thing from working and i likely have the syntax wrong, i haven’t used windows in years.
I don’t think autorun worked with floppy disks, only with CDs and USB units.
I don’t think the OS was sophisticated enough to tell the difference… A drive letter is a drive letter…
There are USB headers, PCI(-E) slots, SATA and some older ones. To get storage devices working on each one you will need a different driver.
Windows disabled autorun for USB sticks before win10.
Also if you list the devices on Linux they will show up as sd(a, b, c…) for SSDs, hd(a, b, c…) for HDDs and nvmen(0,1,2…) for NVMe drives. So yes the OS must be able to differentiate.
Windows assigning letters is just weird IMO.
Also to my knowledge the floppy would show up as disk A on Windows.
Have I just experienced youngsplaining?