[Coco] mess questions

[Lothan]

I haven't tried getting into the debugger, so I can't answer this question.
This may require enabling the debugger in the source code and recompiling.

I understand why the keyboard is mapped the way it is, but it drives me nuts
sometimes too. You can change the keyboard mapping by editing
systems\dragon.c and recompiling. Look for the section that starts with
INPUT_PORTS_START(coco) or INPUT_PORTS_START(coco3). You may want to do this
with MESS 0.95b source code because it is easier to interpret and edit than
previous versions.

I do this by using the OS9.EXE tool in Windows to copy files to and from
virtual disks, but it's limited to 8.3 filenames. It works fine with FAT,
FAT32, and NTFS partitions, but you must feed it short filenames.

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of John R. Hogerhuis
Sent: Thursday, April 28, 2005 1:17 AM
To: CoCoList for Color Computer Enthusiasts
Subject: [Coco] mess questions

OK, trying to use MESS under Linux, hopefully someone can answer:

a) how do I get into the debugger? Is this part of xmess by default or
do I need to recompile? The User Interface menu shows Toggle Debugger on
F5 but that doesn't seem to do anything
b) How do I fix the ridiculous keyboard mapping to PC style (I know *why
* it is the way it is, I just want to know how to fix it...)
c) Quick easy way to load cross compiled machine language programs into
mess? I'm trying to create a ROM-based Forth interpreter which takes
full advantage of the Coco 3... starting with a port of CamelForth 6809
(that part should be easy, I've already done it for the Tandy WP-2 Z80
CamelForth).

Thanks,

-- John.


-- 
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco