Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!web-1e.berkeley.edu!c60c-1ea
From: c60c-1ea@web-1e.berkeley.edu (Yen Yuanchi Hsieh)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Curious PAL problem report
Message-ID: <24198@agate.BERKELEY.EDU>
Date: 9 May 89 17:04:35 GMT
References: <15609@gryphon.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 30

In article <15609@gryphon.COM> keithd@gryphon.COM (Keith Doyle) writes:
>
>Just received a curious letter from someone in Europe reporting a
>PAL problem I've never heard of before.  Was wondering if anyone
>knows if it really is a problem, or if this guy just ought to take
>his machine to the shop.

 [ stuff about PAL problem deleted... ]

>Is this a known problem with PAL Amiga's, or is this guy's Amiga just
>out of whack?

Yes, this is a known problem.  I believe it was to be fixed in 1.4.  Something
about the checking routine was really flakey -- seems that every once in
awhile, the beam position was checked to see if it was in the PAL region or
not.  If it was, then PAL was enabled, oherwise it's ole NTSC time.
Of course, if you check at just the right times, you'll never see the beam
at >NTSC line positions, so PAL is not enabled.  At least that's the story
I've heard...

>And BTW, I never did find out if there's any reason not to keep REPORTMOUSE
>turned on on all windows all the time.

Don't know myself -- but I'm sure it's not even close to the overhead of,
say, the GIMMEZEROZERO windows, so I wouldn't worry about it.

-------------------------------------------------
David Navas		c60c-1ea@WEB.Berkeley.Edu
Ideas?  What ideas?  If I had any idea I would have
an idea I wouldn't have posted all of this nonsense.