archive.worldofdragon.org

I still think your problem is this code trying to output TXT2 using CR as a terminator instead of NULL (0):

LDA #CR
JSR OUTCH ; a newline on the screen
LDB #CH2SCR
LEAX TXT2,PCR
PSHS X,B,A
BSR PRINTL

Yes RAM ends at $7FFF in 32K mode.

There's, of course, nearly another 32K available in 64K mode.

I don't think there's really any need to have both a length byte and terminator for your strings, unless you have a special reason for doing that. It's usual just to have a 0 at the end as terminator. The confusion perhaps comes from the fact that the string output ROM routine at $90E5 expects X to ...

Yes, that's true.

Okay, moving onto the 'Example' listing, I think it's trying to output TXT2 using CR as a terminator instead of NULL. So presumably it runs off the end of the text and continues output until it finds the CR from the LDA #CR instruction.

Okay, a couple of thoughts from a quick glance: 1. I can't remember whether or not OUTCH ($800C) preserves the registers you're using (you need X, U and A preserved). Please check? 2. I didn't follow what GETLNE is doing with B. It didn't seem to be used until you decremented it. Maybe you want CLR ...

jedie wrote:From http://dragon32.info/info/memmap.html :

$8000-bfff BASIC ROM in 32K mode

But $BFFF-$8000 are 16383Bytes
The "d32.rom" file is 16384Bytes

Why?

Your maths is slightly faulty. The number of bytes from $8000 to $BFFF inclusive is calculated as 1+$BFFF-$8000.

jedie wrote:@Sarah: Can you upload your sources somewhere? Maybe it can help me.

tormod wrote:Are these sources something you can share with us?

Yep, okay... here you go:
viewtopic.php?f=7&t=4354

DRAGON CONVERT (DC) is a utility for converting files from WAV/VOC/BIN/BAS/DGN/CAS to CAS/DGN/BAS/WAV format. It runs under MS-DOS or Windows 95/98/NT and has recently celebrated its 20th anniversary! :lol: There were a couple of posts recently asking for the source code, so I've now published it h...

There's a hex editor in DREAMBUG although it's a bit clunky. PC-Dragon emulator has the facility built-in.

You can effectively PEEK anywhere although I/O requires prior setup. If you're simply interested in RAM and ROM then PEEKing any mapped address is straightforward.

No. The text is treated as text.