Thanks, this essentially ended up working for me. I changed the IF MODE=KERNEL
part to have the baseaddr $a000, changed the first 2 words to be Startup just as
in the CART mode, and removed the ORG $a483 for KERNEL mode. That has worked
just fine for me so far.



________________________________
From: mdzron <list.ron@...>
To: synthcart@yahoogroups.com
Sent: Tuesday, June 2, 2009 1:42:34 AM
Subject: [synthcart] Re: Building cynthcart for basic rom is too big





Someone told me he how was able to build a BASIC ROM replace (using DASM),
though I didn't verify I'll just post his suggestions:

first of all, the KERNEL (or KERNAL?!? ;) compile didn't seem to work at all
(lots of FF in the build). His workaround is to do a CART build but modify the
addresses to reflect the BASIC ROM runtime.

MODE equ CART;

RAMCOPY equ 0 ;KERNAL boot routine already does it for the BASIC ROM area

IF MODE=CART
BASEADDR equ $A000

; 5 byte cartridge startup code !DELETE or COMMENT OUT, we don't look for CBM80
here....
; byte $C3, $C2, $CD, $38, $30

; IF MODE=!DISK change to:
IF MODE=DISK ;to avoid double init

As I wrote in the beginning, I did not verify yet, but I know he successfully
built a ROM replacement like this. Maybe you'll find out...

--- In synthcart@yahoogrou ps.com, "synacknet" <synacknet@. ..> wrote:
>
> I was attempting to build cynthcart 1.2.4 for a basic rom replacement,
> and I noticed building with: dasm cynth1_2_4.asm -f3 fails due to the
> trailing ORG $bfff being a backward reference since the image is too large.
> I noticed the following:
> IF MODE=KERNEL
> BASEADDR equ $8000
>
> I changed that to $a000 since everything between $8000 and $a000 would
> be filler in this case. This brings the size down to ~9237 bytes, still too
big.
> Since the bulk of the code + tuning data is after $a483 for the basic idle
loop
> entry point, it can't fit in 8k. The solution is likely to rearrange some
things to
> utilize the unused space prior to $a483. I was just wondering if this a known
> problem, or if I'm just plain doing something wrong before I jump into it.
>
> Thanks.
>







[Non-text portions of this message have been removed]