#Copy protection
5 messages in this thread
Yes, I found that out experimentally!
Now, the OTHER problem is having enuf DISK space! The listing from Argoterm is
over 300k long…Awesome.
Now, all I have to do is figure out why my assembled versions crash. Your
program has been very interesting as a tutorial on how to interface with DOS,
etc.
Now if we could only speed up the character output call…….
-Larry-
* Replies:
8648, 8652
Larry-
I think if I patched ArgoTerm to read 4 bytes at a time from the serial port,
and print as many bytes to the console as were returned, then that should speed
it up enough to cope with 2400 baud ! ( I hope!?)
Main problem is that the OS Text routines prefer large chunks of bytes to
print, rather than doing them on an individual basis (setup time for blitter
etc… ALso problems with Italics and Kerning if characters are done
individually!)
— Jez.
Larry-
I've never listed out ArgoTerm from the assembler so I didnt realise it was so
big!
re: Crashes. Check FUNCDEF.I, and make sure that it isnt being included
twice. I uwsed Assem v1.0… what are u using!?
— Jez.
* Replies:
8674, 8696
Jez-
I tried BOTH 1.0 and 1.1. (The assembler is 10.178 in both, but Alink
got promoted from 2.20 to 2.30).
I wanted to see an assembler listing to try to figure out what all got
hauled in (including maybe two funcdefs). I thought at first that Assem was
SLOW! Nope! it is dealing with macro expansions within macro expansions
within….. and 10 levels of includes to boot. Must sizzle with a single source
file!
I think that one of the reasons that the listing output is so big is
that tabs are expanded (I think…).
I know it costs about as much time for a string output DOS call as for
a single character… still stupid, tho. Someone will find a lower-level call
that works, I hope.
Regards to Merrie Olde Englande,
-La- (Awash on the pacific coast)
Jez…
It occurs to me that if you were to use your own (constant sized character
set), and just Blitted the characters to the screen, that it would be much
quicker than anything that could be achieved by Intuition and/or DOS.
Re: crashes
Can't quite figure it, as your code looks pretty clean. As to increasing stack
size or workspace size, I think the problem is not so much with that as with
the assembler somehow generating far too much stuff in storage. I was having
that sort of problem only when including <The entire Universe.i) or when
getting a lot of errors.
Regards, Larry.