Re: PET Kernal 'load' routine & CC65 question

From: Steve Gray <sjgray_at_rogers.com>
Date: Wed, 14 Oct 2020 19:08:18 -0400
Message-Id: <BBD63C3E-DCFA-48D7-8A17-2F673F20574B_at_rogers.com>
Here is some interesting info comparing kernal jump tables etc:

https://www.pagetable.com/?p=926

Steve


> On Oct 14, 2020, at 4:48 PM, Ethan Dicks <ethan.dicks_at_gmail.com> wrote:
> 
>> On Tue, Oct 13, 2020 at 11:22 PM André Fachat <afachat_at_gmx.de> wrote:
>> Am 14. Oktober 2020 02:11:40 schrieb vtgearhead <snhirsch_at_gmail.com>:
>>> ...there is some confusion about use
>>> of 'cbm_load()' on a PET.  The CC65 sources fail to import the Kernal LOAD
>>> entry point ($FFD5) and the way it's being excluded makes me wonder if this
>>> is deliberate: All models but PET have it available.
>>> 
>>> Since the entry point is there,
>> 
>> No it isn't. At least not what you'd expect.
>> 
>> Follow the source, you'll see that it calls BASIC to actually parse the parameters.
> 
> This sort of thing has come up before...
> 
> From: rhialto_at_mbfys.kun.nl (Olaf Seibert)
> Newsgroups: comp.sys.cbm
> Subject: Re: CBM PET 3032 information wanted
> Date: 5 Sep 1995 13:07:44 GMT
> 
> In <421bvb$3ij_at_tuegate.tue.nl> martijnb_at_stack.urc.tue.nl (Martijn van
> Buul) writes:
>> 2) A kernal jumptable (the jumptable from the C64 (from the Programmers
>>  Guide) isn't the same. I can't find SETFLS, SETNAM etc., needed to open a
>>  file)
> 
> The top part of the jumptable is mostly the same, but I don't think
> SETNAM and SETLFS are in that part. There are also other differences
> that are quite annoying (meaning: they corrected some earlier design
> mistakes in the VIC kernel). For instance, LOAD and SAVE are meant
> to be called from BASIC. The first thing they do is  use BASIC routines
> to fetch the file name and device number. To use them from ML you must
> either set up CHRGET correctly or jump directly into ROM (where exactly
> differs with each ROM version :-( ). OPEN however should be usable.
> 
Received on 2020-10-15 02:00:03

Archive generated by hypermail 2.3.0.