3 ms·
This warning was probably obsolete even when the FAQ was written (in 1995), though. Multisync monitors were already pretty standard at that point, and they coul
by duskwuff 7y ago
This warning was probably obsolete even when the FAQ was written (in 1995), though. Multisync monitors were already pretty standard at that point, and they could usually recognize an out-of-range input and display a warning on screen.
It's possible that someone damaged a really old single-scan monitor with a bad XFree86 configuration, but I wouldn't be surprised if this were just a rumor which got propagated through warnings in FAQs.
- anthk 7y agoIt was possible. I did it by hand with a Windows 98 machine, the OS adverted me on trying to set up the resolution to 800x600. A pitched buzz began and the CRT I was using in some sort of academy bugged off with some burnish smell. No smoke, but you noticed it a bit. The screen had a SVGA resolution by default, so it may have been from 1995 or so.
- dfox 7y agoAny VGA monitor is inherently multisync, which does not imply that it is capable of detecting that horizontal scan is too fast to be safe. The mechanism by which damage occurs involve the fact that essentially everything inside the monitor is synchronized with horizontal scan, including HV power supply for the CRT (usually even the main SMPS is synchronized with horizontal scan to reduce switching noise). And efficiency of both horizontal scan circuitry and the HV power supply depends on the incoming frequency and it is perfectly possible that some frequency (usually, but not necessarily higher than indended) will cause over voltage somewhere. I have destroyed one small monochrome VGA monitor (the kind used in late 90's on cash registers) by just blindly switching the output to some SVGA mode, it even involved quite loud bang from inside of it.
- milesvp 7y agoI killed a vga monitor ~2000 trying to install redhat on a machine with an old monitor. Made me really paranoid every time I tried to install X for the next few years.
- 72deluxe 7y agoAs a burst of nostalgia, do you remember using Linuxconf on that machine? I kinda miss the early GTK+ and GNOME1 days, whilst I fumbled with fvwm under RedHat (before the Fedora split).
- milesvp 7y agoI don’t think I knew enough at the time to remember. Linuxconf sounds familiar though, I’m sure I used it at some point.
- 72deluxe 7y agoI was poor and using a secondhand "due to be thrown out" IBM 12" display (which despite being 12" had a colossal black border around the actual image on the screen, making the usable area even smaller than 12") and had a 486 DX2 whilst everyone else had Pentiums. I remember fumbling around to get my abysmal graphics card working under XFree86 whilst groping around magazines for appropriate commands and setting the configuration to various bad values that caused that monitor to make hellish screaming noises as I attempted to set it to a resolution and frequency higher than it could ever go. I should have read the warning.