Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: changes to XF86Config.eg
- To: tlug@example.com
- Subject: Re: changes to XF86Config.eg
- From: turnbull@example.com (Stephen J. Turnbull)
- Date: Sat, 11 May 96 20:27 JST
- In-Reply-To: <199605110320.MAA16310@example.com> (schweiz@example.com)
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Jim" == Jim Schweizer <schweiz@example.com> writes: Jim> If I comment that out and uncomment: Jim> # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Jim> Interlace Jim> do I run the risk of trashing the monitor? Can't say unless we know your monitor and its specs, video board and its specs. As long as you're using entries from the database that correspond *exactly* to your monitor and video board the risk is minimal. Try looking at the output from "X -probeonly". (This also can involve some risk.) How much risk? I personally have never heard of anyone blowing up a monitor from configuring X Windows. (I have heard a lot about fried monitors.... My brother used to blow up monitors on a weekly basis---but then, *he* was a monitor design engineer for DEC.... I'm trying to be humorous, in case it's not obvious!) -- Stephen John Turnbull University of Tsukuba Yaseppochi-Gumi Institute of Socio-Economic Planning http://turnbull.sk.tsukuba.ac.jp/ Tennodai 1-1-1, Tsukuba, 305 JAPAN turnbull@example.com
- References:
- changes to XF86Config.eg
- From: schweiz@example.com (Jim Schweizer)
Home | Main Index | Thread Index
- Prev by Date: changes to XF86Config.eg
- Next by Date: Ctrl+Alt+Keypad-Plus
- Prev by thread: changes to XF86Config.eg
- Next by thread: Ctrl+Alt+Keypad-Plus
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links