home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.linux:20464 comp.windows.x:20207
- Newsgroups: comp.os.linux,comp.windows.x,comp.sysv386
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!yoyo.cc.monash.edu.au!parry
- From: parry@yoyo.cc.monash.edu.au (Tom J Parry)
- Subject: Re: X / Enhanced VGA Local Bus ET4000
- Message-ID: <1992Dec15.042904.12809@monu6.cc.monash.edu.au>
- Followup-To: comp.os.linux,comp.windows.x,comp.sysv386
- Originator: parry@yoyo.cc.monash.edu.au
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Monash University, Melb., Australia.
- References: <1992Dec7.210844.17344@nevada.edu>
- Date: Tue, 15 Dec 1992 04:29:04 GMT
- Lines: 23
-
- FRANK NEEDHAM (fmn@nevada.edu) wrote:
- >It seems that when ordering my pc some weeks ago there was misunderstanding
- >between myself and the co. who sent me the pc. Thinking that a Tseng Labs
- >ET4000 card was being sent along with the pc, all seemed well. Well, it turns
- >out they sent me the Enhanced VGA et4000 local bus (I did know it was local
- >bus).
-
- I have a card similar to this ("EVgA et4000 local bus") and it works fine.
- CLOCK.EXE is useless for finding out the clocks, but by removing the Clocks:
- line (from the config file), X386 will try to find what clocks it can.
- Sometimes it won't find a couple of clocks, but if you run it a few times
- you'll eventually get them all. Put this line in your Config file and you
- wont have problems later detecting clocks at startup.
-
- >One more thing :-), the modegen.txt file mentions running 'startx.notcp 2>
- Use 'startx 2> whatever'
-
- As for localbus vs non-localbus, I don't know. Everything seems pretty fast
- on my 486/33 :)
-
- --
- Tom J Parry.
- Your reality is a figment of my imagination.
-