Path: utzoo!utgpu!watmath!iuvax!cica!tut.cis.ohio-state.edu!ukma!phoenix
From: phoenix@ms.uky.edu (R'ykandar Korra'ti)
Newsgroups: comp.sys.cbm
Subject: Re: Desterm 128
Message-ID: <13259@s.ms.uky.edu>
Date: 16 Nov 89 19:13:17 GMT
References: <13190@s.ms.uky.edu> <46400044@uxf.cso.uiuc.edu>
Reply-To: phoenix@ms.uky.edu (R'ykandar Korra'ti)
Organization: El'n'tk National Spaceport, Mission Control
Lines: 23

In article <46400044@uxf.cso.uiuc.edu> djn341@uxf.cso.uiuc.edu writes:
>Well,
>   I don't know if a good monitor will make that much of a difference,
>considering that it trying to cram 50 lines into the VDC's 200 vertical pixel
>resolution.
     Um; I don't think so. It puts the VDC into interlace mode, wherein you
have 400 lines of resolution. That's still 8 pixels vertical per character.
     A higher-persistance monitor capable of dealing with an interlaced signal
would solve the problem right away. I think Commodore's is called the A2002
(don't quote me on that) and it's manufactured for the Amiga. It's a high-
persistance colour monitor and the results, I've been told from people who
have them, are quite nice.
     BTW, do not assume that a high-priced multiscan will like interlaced
video modes. Many very specifically do NOT. Make sure that the one you buy
likes interlace - the Mitsubiti Diamondscan comes to mind as a good choice.
Many multisync monitors see the difference in vertical retrace times as being
an error on the part of the display card and "correct" it for you - thus
landing the second set of lines right on top of the first. This "feature" is
great if you've got a cruddy display card; terrable if you use interlaced
video.
-- 
| R'ykandar Korra'ti, Editor, LOW ORBIT | phoenix@ms.uky.edu | CIS 72406,370 |
| Elfinkind, Unite! | phoenix@ukma.bitnet | PLink: Skywise | QLink: Bearclaw |