[Coco] Run .BIN directly in Coco3 emulator?

William Astle lost at l-w.ca
Sat Apr 12 02:30:10 EDT 2014

BTW, you can just do "EXEC&H4000" (or EXEC16384 if you don't want to 
deal with the & bit) - no need to mess with pokes or USR.

If the execution address is not present in the generated .bin file, it 
means you have found a bug in the AS6809/ASLINK programs or you're doing 
something that confuses them.

On 14-04-11 11:01 PM, Mark McDougall wrote:
> On 12/04/2014 12:55 AM, Richard Goedeken wrote:
>> http://www.chipple.net/coco/file2dsk/
> I've been successful in using this software to create a DSK image with
> my file - again, thanks!
> However, my .BIN file doesn't seem to have a valid EXEC address?!?
> I'm using the AS6809 assembler. I *definitely* don't want to switch to
> another assembler because I'm also developing the same software in Z80
> in parallel using the ASZ80 assembler and it's *much* simpler to work
> with two compatible assemblers. The other advantage is that ASLINK is
> able to output COCO .BIN files.
> Perhaps Boisy can answer this...
> I specify the execution address via the .end directive and the .LST file
> displays the correct address. However after loading into MESS and using
> PEEK(157/8) it is 0. Also a hex dump of the .BIN file suggests there is
> no EXEC address.
> The other weird thing is that all the blocks in the .BIN file are $003B
> in length, when it's a single, contiguous block of code/data. Is that a
> peculiarity of the implementation in ASLINK?
> As a workaround atm I can either POKE 157 with 64 and EXEC, or
> DEFUSR0=&H4000 and then A=DEFUSR(0) but either way it's a PITA,
> especially since I first have to enable full keyboard emulation in MESS
> each time...
> Any tips would be appreciated!
> Regards,

More information about the Coco mailing list