Path: utzoo!utgpu!water!watmath!clyde!mcdchg!chinet!saj
From: saj@chinet.UUCP (Stephen Jacobs)
Newsgroups: comp.sys.atari.st
Subject: Re: Damaged moriabin.arc header
Summary: I'm surprised to hear that
Message-ID: <6644@chinet.UUCP>
Date: 21 Sep 88 14:44:59 GMT
References: <14436@agate.BERKELEY.EDU> <598@stag.UUCP>
Organization: Chinet - Chicago Public Access UNIX
Lines: 28

In article <598@stag.UUCP>, trb@stag.UUCP ( Todd Burkey ) writes:
> It uudecoded fine here, but I've noticed two problems with it so
> far...first, it hangs quite often on me (both when I use if from the
> desk top and when I run it from gulam). I haven't made it out of the
> bartering stages yet (it always hangs when I am moving between the
> first screens buildings). No bombs, just nothing happening (except
> hearing the keyclicks) as I press keys. The other problem is just one
> of implementation. The command line options are lower case only, so
> you really can't run moria as a '.ttp' file. The reason being that the
> desktop uppercases all your text that you type. The workaround for
> this is to simply write a little wrapper program that pexec's the
> moria code with the appropriate command tail. This wrapper can also
> set the SHELL variable at the the same time.

I've played this version of moria for probably about a hundred hours without
a real keyboard lockup.  There was a problem when I did a "."
move while confused, but it cleared itself in a few seconds.  The program is
so large that I wonder if there might be too much already in your machine's
memory when you load it.  I generally have a hard disk interface and a clock
setter in the auto folder, foldr100, FATSPEED, and the control panel.  ST
curses is a stack hog, but the program was compiled with LOTS of stack space
to allow for that.
   The case problem was a really dumb oversight.  It should only interfere
with the use of the rogue key layout and consulting the highscores file,
though.  TOS ignores upper and lower case in filenames.  If this bothers
people enough, maybe someone (maybe me?) could come up with a binary patch.
In my experience, there's rarely a sequence of 20 op-codes that can't be
shortened enough to squeeze in 2 more.