Re: NTSC VIC-II timing

From: earth1dome1 <earth1dome1_at_yahoo.com>
Date: Thu, 22 Jun 2017 11:59:13 -0700
Message-ID: <8bdkisbx45asiu3ebefmmm7s.1498157953427@email.android.com>
Ntsc fixing?


Sent from my T-Mobile 4G LTE Device-------- Original message --------From: silverdr@wfmh.org.pl Date: 6/22/2017  7:28 AM  (GMT-08:00) To: cbm-hackers@musoftware.de Subject: Re: NTSC VIC-II timing 

> On 2017-06-21, at 18:37, Spiro Trikaliotis <ml-cbmhackers@trikaliotis.net> wrote:
> 
> Hello,
> 
> * On Wed, Jun 21, 2017 at 06:35:24PM +0200 silverdr@wfmh.org.pl wrote:
> 
>> I understand (and know, in fact). But it seems I wasn't entirely
>> clear. The sentence should be read as: "I can't envision [myself
>> writing] a commercial product (game f.e.) that would just break
>> because the machine has a different but still valid VIC chip inside".
>> Not that I am writing one now ;-) but the old habits never die...
> 
> But now, we know of all these variants, so we can take them into
> account. Back in the days, I suspect most people did not know about
> these differences.

Didn't notice yesterday.. Very valid point, indeed. I guess that even the higher profile products, which employed un-officially-documented features / tricks could be affected by the "democoding style" as Marko liked to point out. Meaning more or less "patching back and forth until it works on my particular machine because I don't know how and why it actually works" :-)

-- 
SD! - http://e4aws.silverdr.com/


       Message was sent through the cbm-hackers mailing list


       Message was sent through the cbm-hackers mailing list
Received on 2017-06-22 19:03:21

Archive generated by hypermail 2.2.0.