Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: NTSC vs. PAL screen checking (Was Re: JRComm....)
Message-ID: <24510@usc.edu>
Date: 4 May 90 17:27:06 GMT
References: <892@tau.sm.luth.se> <3396@bingvaxu.cc.binghamton.edu> <1177@tmiuv0.uucp>
Sender: news@usc.edu
Organization: Felsina Software, Los Angeles, CA
Lines: 20

In article <1177@tmiuv0.uucp> rick@tmiuv0.uucp writes:
>Besides, I think this thread got started by a flame on JRComm's lack of PAL
>support.  I think Jack answered reasonably by stating that JRComm is a terminal
>emulator, and 90% of the terminals out there use 80 or 132 character wide
>screens, 24 or 25 lines high.  In those cases, I'm not certain that the
>additional screen height in PAL mode would be of much use.  But then again,
>I'm in the States.  Must be my North American bias showing again. 8-)

It makes a LOT of sense even if you have just NTSC. How about when you go
interlace?  You can have 48 lines instead of 24!  How about when you use
morerows?  You can get 30 or 60 lines on NTSC.  And if you have an A3000
(or flicker fixer) they'll all be rock solid. And what if you have an A2024
or Viking 1?  It is quite easy to check the screen size AND the current
window size.  A-Talk III recomputes the max cols/rows even in workbench
on the fly, and reset the terminal to those sizes.  It is really very simple.

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=