[comp.sys.atari.st] Latest version of STadel

usenet@TSfR.UUCP (usenet) (08/24/88)

In article <1110@atari.UUCP> kbad@atari.UUCP (Ken Badertscher) writes:
>in article <920@lakesys.UUCP>, rich@lakesys.UUCP (Rich Dankert) says:
>> [commentary about STadel bombing with Mega roms] <<
> Hmm, that's odd. I've tested ALL of the STadel 3.xx release
  versions on all* versions of the roms <

    Evil spirits, I'm afraid.  When my ST was alive, I only tested
against my configuration; when my ST was dying, I didn't have a
keyboard or monitor and needed to play with the system attached to
/dev/tty01 (the serial port) [let me tell you how much fun it is
trying to debug a BBS when the OS doesn't have a stderr defined];
and now that the ST is dead (another motherboard on the heap of
dead computers killed by my proximity) I can only do debugging when
I borrow a ST and port the code over from my PC clone.

    The most common 3.3 ST bombfactories seem to be if you are
blanking string fields out in your ctdlcnfg.sys by doing "" -
`#shell ""' seems to be a good offender for that - or if you are
#define'ing TIMEOUT and/or HOUROUT.  Killing those things should*
cut down bombing quite a bit.

    [Don't reply to me here, please - my Usenet access is spotty
these days, due to 3.3a/3.3b debugging and my inherent laziness
about everything except citadel. If you can get onto the STadel
network (the STadel: room) or Bix (js.online/stadel), I'll be able
to reliably answer questions and put out brushfires. Calling Pell
will probably work, too.]

   -david parsons                                  | Not opinions; I
   -orc@pell.citadel (US 504 588 1258 3-2400 baud) | speak -TRUTH-