🚀 go-pugleaf

=-=-=-=-=-=-=-=-=-= line eater poison :-) =-=-=-=-=-=-=-=-=-=-=-=-=


     I'm having some trouble getting STUSQ to do the right thing...
I used Kermit to get the uuencoded file off a Vax and ran it through
the ST uudecoder provided by franco@indiana.CSNET.  When I try to run
STUSQ it appears to load, but then exits normally.  This happens using
both CLI and the Desktop.  I tried the SID68K debugging tool to see if
I could see where it was going and all I got was "Bus Error at 00049B50".
SID68K itself runs OK, but I get the Bus Error when trying to read STUSQ.

     So, I thought I'd try DUMP'ing STUSQ to see if there were any ASCII
strings, just to check that the uudecode worked...  Here's a few of the
strings I saw flash past:

     cstrlen    f_open    f_close    f_read    f_write    f_lseek
     gemalign   f_lseek failed       gemfread

     You tried to write a read-only file!

     Open needs 2 arguments - name and more

     process-command-line

     This implementation is nearly FORTH-83 standard, but it lacks
     mass storage and uses 32-bit stacks

     68000 Forth 83 - Atari 520 version


     From this I think it's fair to assume that the uudecoder is working
fine, but for some reason STUSQ won't load and/or run.  I have a 520ST
with TOS in RAM, monochrome monitor, twin single-sided disks and 512K of
RAM.  I am not currently using any RamDisk, so there should be enough
spare RAM.  Also, I have used ST uudecode on other things that worked...

     Does anyone have any bright ideas ??  Do I need any particular TOS
or other environment ??  Is STUSQ supposed to start with 120 zero words ??


     All help gratefully received,

     Ralph Mitchell