home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- From: jaggy@purplet.demon.co.uk (Mike Jagdis)
- Path: sparky!uunet!pipex!demon!purplet!jaggy
- Subject: Help with ET4000 and ...etc
- Organization: FidoNet node 2:252/305 - The Purple Tentacle, Reading
- Date: Tue, 12 Jan 1993 07:00:00 +0000
- Message-ID: <38.2B534919@purplet.demon.co.uk>
- Sender: usenet@demon.co.uk
- Lines: 17
-
- gg> The values calculated by the spreadsheets for the timings
- gg> were well out when the specification and actual as measured on the
- gg> card output were compared.
-
- I assume you mean the sync timings and the pre and post-sync delays? These
- are probably where most people have problems. Some monitors seem to like
- shorter syncs than others, some longer. In particular interlaced modes often
- cause problems. Too long a horizontal sync period looses the
- "interlacedness" of the display in many cases. It would perhaps be better to
- have the sync timings set up according to one of the VESA modes initially. I
- just left what worked for me in there - which wasn't an interlaced set up.
-
- I'll release a new modegen.taz package in a couple of days anyway. I think
- the sc in there tries to write to text space and core dumps :-).
-
- Mike
-
-