#M2Sprint-Startup
5 messages in this thread
I just installed M2Sprint 1.0. When the install program finished, there was
an M2Sprint-Startup file in my S: directory. The first line was '.key ""'. That
didn't look legal to me, and sure eneough, I got a "bad arg" error when it
tried to execute. I deleted the line and it seemed to execute OK.
Also, I think you should set the default stacksize to something larger than
4K, or at least put a prominent warning in the manual that even trivial
programs will guru unless the user increases the stack size. 4K won't even run
a Byte Sieve benchmark without crashing.
The .key thing is odd, it works here. Mayb eit's ARP, maybe it's 1.3. Which OS
version are you using?
As for the stack size, it al depends on how you write your programs. If you
allocate all you variables locally, then everything gets put on the stack, and
you will indeed crash rapidly. When you've got large arrays, it is much better
practice to allocate them globally, or using AllocMem. Witness all the demo
programs and the support tools, they all run fine on about 2K of stack, so it's
nothing inherent to the language.
Anyway, I'll check out the .key thing. Thanks.
I've checked out the .key thing. It works fine under AmigaDOS 1.3, but faisl
under ASH (the ARP shell). The bug has already been reported to the author of
ASH.
"The .key thing?" What is this, the Bush administration? I thought it was a
script "trick" to allow the script to run only if there is a t: directory. My
memory is fuzzy on this. The issue came up when I first got TxEd. -Art
I think the .key was a leftover from earlier installation scripts I was working
on, which required user input, al though I seem to recall a valid reason for
putting it there, but I'm not certain. In any case, it works on normal CLI and
AmigaSHell, but ARP doesn't like it.