Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!ucbvax!ucsd!dog.ee.lbl.gov!lbl.gov!jnmoyne
From: jnmoyne@lbl.gov (Jean-Noel MOYNE)
Newsgroups: comp.sys.amiga.tech
Subject: Re: 2.0 File Requestor/NTSC Questions
Message-ID: <8727@dog.ee.lbl.gov>
Date: 20 Dec 90 01:48:42 GMT
Organization: Lawrence Berkeley Laboratory
Lines: 26
X-Local-Date: Wed, 19 Dec 90 17:48:42 PST
References:<1990Dec17.033055.3516@marlin.jcu.edu.au> <16641@cbmvax.commodore.com> <1990Dec19.094324.3621@marlin.jcu.edu.au> <16673@cbmvax.commodore.com>


       Maybe what the original question was: what happens on the screen of 
the NTSC user when the program opens a screen in PAL mode. Well it's 
simple, to experiment it yourself, open a non interlaced screen of 256+56 
lines high, you'll get an overscan screen, and miss a part of it .. but 
it's harmless.

      This 1.2/1.3 bug is harmless too, but rather annoying, because since 
the original CLI window opens only with 200 lines, you can't see it until 
you've done all your startup-sequence and so ... when you're using 
floppies the reboot time beeing long, you don't like it. The best fix 
against it is to write a small program: test the flag in GfxBase, and if 
it's not PAL reset the machine, and the place this program at the 
beginning of the startup-sequence.

       One funny thing I noticed: when you're on a PAL machine which has 
booted in NTSC mode, if you open and display a PAL picture, you can see 
that the Amiga opens the screen less than 256 lines, it opens it high 
enough for what it thinks is more than overscan and stops here. (i.e. 
it'll open something like 240 lines ... maybe 232 (or 232+1 (-:)

          JNM

--
These are my own ideas (not LBL's)
jnmoyne@lbl.gov ... but it's allready written at the top of this.