home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!think.com!spool.mu.edu!agate!doc.ic.ac.uk!uknet!mcsun!sunic!aun.uninett.no!nuug!ifi.uio.no!nilsco
- From: nilsco@ifi.uio.no (Nils Liaaen Corneliusen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: PAL or NTSC, how to c
- Message-ID: <1992Nov5.113159.13205@ifi.uio.no>
- Date: 5 Nov 92 11:31:59 GMT
- References: <110.193.uupcb@ssr.com> <1908@lysator.liu.se> <1992Nov5.095622.9939@ifi.uio.no>
- Sender: nilsco@ifi.uio.no (Nils Liaaen Corneliusen)
- Organization: Dept. of Informatics, University of Oslo, Norway
- Lines: 19
- Nntp-Posting-Host: kolsaas.ifi.uio.no
- Originator: nilsco@kolsaas.ifi.uio.no
-
-
- In article <1992Nov5.095622.9939@ifi.uio.no>, olavka@ifi.uio.no (Olav Lur}s Kalgraf) writes:
- > This offset is VBLANKFREQUENCY, but there is a small catch with using
- > this byte. It does NOT change EVER. Even if you change from PAL to NTSC
- > using the screenmode prefs program. You can use this byte to determine
- > the clocking of the CIA's =) but little else. :(
-
- So what is the point in having and offset called PowerSupplyFrequency that
- in most cases would be just the same? If you set NTSC in the bootmenu on
- A4000 what does it say then?
-
- Anyway, why should that setting change? It occurs a bit strange that data
- concerning screenmodes should be put in execbase. There must be an easier
- to determine the mode of the wb screen...
-
- ------------------------------------------------------------
- INCLUDE "disclaimer.i" snail-mail:
- Nils Corneliusen Heyerdahls vei 17
- internet: nilsco@ifi.uio.no OSLO, Norway
-