Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!agate!apple!oliveb!tymix!tardis!jms
From: jms@tardis.Tymnet.COM (Joe Smith)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Interlace and Multiscan Moniters
Message-ID: <532@tardis.Tymnet.COM>
Date: 22 Aug 89 03:18:25 GMT
References: <654@rhea.trl.oz>
Reply-To: jms@tardis.Tymnet.COM (Joe Smith)
Organization: McDonnell Douglas Field Service Co, San Jose CA
Lines: 20

In article <654@rhea.trl.oz> aduncan@rhea.trl.oz (Allan Duncan) writes:
>....  If you had been feeding composite sync to the monitor (as used
>by the 1080) there could have been interaction with the complicated
>vertical sync region (designed for cheap valve sync circuits when I was
>but a lad).  All I can offer is that the unit is iffy, OR it has
>significantly brighter output.  Flicker is strongly brightness dependant.

The problem as originally reported is probably a design in the monitor.
Some multisync monitors with RGB input can handle 262 lines in 1/60 second
yet refuse to do 262.5 lines per frame.

The place where Augnet meets has the opposite problem.  The large screen
monitor there has a composite input that gets all upset if the incoming
signal is not interlaced.  They have to use SetLace (or LaceTogl) to force
the interlace signal when showing 640x200 or 320x200 screens.
-- 
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com
McDonnell Douglas FSCO  | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21    | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"