You're viewing a single thread.
Ah Slackware, the first time that I learned software could damage hardware. It has the option to also configure hsync on your CRT monitor, and if said monitor didn't correctly validate the range it would permanently fuck it up.
I learned that lesson as a 12 year old in the early 90's on an original IBM PC 5150 with a 5151 monochrome monitor, fucking with TSR's in DOS 3.1. It must've made the graphics card change timing modes and the monitor immediately blew a fuse. My dad then soldered in a fuseholder so the fuse in the monitor can be replaces as needed.
Out of fear of doing further damage, I did stay away from the particular TSRs that had any relation to changing video timing modes and it didn't happen again.
Haha, TSR, man, good old memories... Is there a famous TSR called sidekick? Chain of CD 09H... :)
So I'm not the only one who fried a monitor trying to get X11 working...
Really? I didn't know it was possible. How's that happened?
X11 used to require very cumbersome MANUAL configuration, where you would specify the exact parameters of your keyboard, mouse, monitor, and other peripherals. If you accidentally ended up overclocking your monitor it would melt. For at least a decade, it has been able to run with no configuration file at all, but in the 90s/early 2000s you had to produce a unique >75 line xorg.conf file for your specific hardware.
Thanks, that's terrifying and I'm glad that I never had to do it
God that brings back memories
Oh no, for sure! I did it with Debian in '98-99.
That certainly makes me feel better for letting the Magic Smoke out.
I fried a modern portable monitor just by booting x11 about 2 years ago
Definitely a hardware issue, not a software one.
Oh man, I completely forgot this happening to me lol.