Ha! Nice. I knew somebody'd pick that up. I was in a hurry when I wrote
the email and just ran it in Chipmunk to get some output. Chipmunk won't
let you peek, so I replaced peek(i) with a random character. It's the
same format, just different data. Thanks for the note.
It takes about 3 secs per line. I have some ideas based on folks
suggestions that I'll head off on. I'll also post the code separately.
Thanks,
Will
On 10/26/22 2:50 AM, MikeS wrote:
How slow is 'sooooo slllloooowww' ?
I wrote a little program and it takes about a second per line, listing
to the screen; haven't tried listing to the printer or the com port.
Scrolling is notoriously slow on the M100 but I believe there's a way
to speed it up a bit.
Doesn't really seem out of line for a short run but if I needed a
large block in a hurry I think I'd use a PC.
BTW, is that sample actually in the M100 somewhere? Not at 0000 in
mine ;-)
m
----- Original Message -----
*From:* Will Senn <mailto:[email protected]>
*To:* Model 100 Discussion <mailto:[email protected]>
*Sent:* Tuesday, October 25, 2022 9:32 PM
*Subject:* [M100] BASIC slowness
OMG. I wrote my banner doing it's read of rom for character maps
and sure, it takes a while to print a banner out using print
statements, but it's bearable. But, my memory dumper is gosh awful
slow. I have a subroutine to convert hex to dec, one to convert
dec to hex, and one to pad strings given a length and character.
My code calls the dec to hex conversion routine as it loops
through a set of decimal addresses (destined for peeks). It then
calls peek and the pad routine to print lines of the form:
0000: 36 B6 21 17 46 00 6A 06 6.!.F.j.
0008: B5 F0 3D 2E 51 E3 A6 26 ..=.Q..&
But, ooohhh sooooo slllloooowww!
I figure I can inline the conversion routines or write them in
machine code and CALL them which will speed them up, but I'm not
sure about the padding stuff. I can probably do them in machine
code, and I'll definitely try that, but in the meantime, is there
a trick to fast output I'm missing?
Regards,
Will
