You're right about the network drivers, but on things like serial drivers, Windows is a fucking nightmare. Hell, I can't use some devices because FTDI drivers will brick the device if it decides its a knockoff of their chip. Getting anything working that isn't consumer grade is a shit show.

[–] Redredme@lemmy.world 6 points 1 year ago (1 children)

Serial drivers? Are we talking rs232? (Checks what tf ftdi is)

Ah yes. We really are talking about very old school stuff. It brings back memories.

This week I learned we have a waterslide connected through rs232 to a pi in our network. How's that for a IOT discovery. Working for a medium sized municipality really shows you all the bonkers solutions (and implementations) out there. If you can think a IT horror up, chances are good somebody really has created it and is using it commercially.

Back to your issue, which is more a Ftdi issue then a windows issue since they themselves create the crashing drivers. And I can see how an old school serial port, connected to a modern pc can result in all kinds of havoc when done wrong.

I see FTDI also have usb to rs232 solutions. That should work... Mostly. (as long as the solution doesn't go looking for an irq or other horror from the past.)

I'm really getting curious for what use case you're still using rs232. Most network gear these days is perfectly managed without it.

[–] ikidd@lemmy.world 1 points 1 year ago

USB to serial converters are what use these drivers and they're used all day long for IOT stuff