Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!comp.vuw.ac.nz!canterbury!chem194
From: chem194@csc.canterbury.ac.nz (John Davis)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: I got  problem with overscan*interlace*PAL
Message-ID: <1991Jun3.135118.944@csc.canterbury.ac.nz>
Date: 3 Jun 91 13:51:18 +1200
References: <1991Jun2.183144.22881@daimi.aau.dk>
Organization: Chem Dept, U of Cant, ChCh NZ
Lines: 25

In article <1991Jun2.183144.22881@daimi.aau.dk>, pilgrim@daimi.aau.dk (Jakob G}rdsted) writes:

> I use a PAL a500. Both of these programs fail on one type
> of pictures. That is, interlaced, 4colour overscan pictures.
> It seems like, when one tries this, that the machine acts like
> the display is NTSC.

If you mean that the display actually _truncates_ around the 400 line
mark on the screen (i.e. ALL windows disappear beneath there, as opposed to 
only the backdrop picture being chopped off, with windows etc lower down
the screen still visible) then it could be the reasonably well known
bug relating to overscaned, 16 colour hires PAL screens. To find out,
while the screen is truncated, load preferences and use the centering
control in prefs to slowly move the screen left - you should find
that at some point the screen will suddenly start displaying full
depth again (I got caught with this running extreme overscan and 
Jrcomm in 16 colour mode).
 
The solution is to leave your preferences set with the screen far enough
to the left that the chop-off doesn't happen... 
 
-----------------------------------------------------------
| o      John Davis - CHEM194@csc.canterbury.ac.nz       o |
| o    (Depart)mental Programmer,Chemistry Department    o |
| o  University of Canterbury, Christchurch, New Zealand o |