Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven.umd.edu!wam.umd.edu!ignatz
From: ignatz@wam.umd.edu (Mark J. Sienkiewicz)
Newsgroups: comp.os.os9
Subject: Re: Can't execute "J" - Error #000: 216
Message-ID: <1991Jun21.154206.3297@wam.umd.edu>
Date: 21 Jun 91 15:42:06 GMT
References: <1991Jun14.202821.20308@unhd.unh.edu> <1991Jun15.001249.5963@ncsu.edu> <YcLJfnq00WCpEQLFMd@andrew.cmu.edu>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 15
Nntp-Posting-Host: avw

In article <YcLJfnq00WCpEQLFMd@andrew.cmu.edu> ww0n+@andrew.cmu.edu (Walter Lloyd Wimer III) writes:
>Hmmmm. . . .   Someone should write a real executable program named "J"
>which sits in the execution directory and prints out an appropriate
>error message when invoked. . . .  ;-)

Actually, this usually happens because the OS9 shell didn't want
load the executable in the first place.  (Usually, it is not executable
or something like that.)  You should have the "J\374" (the real name
it was looking for) figure out what file it was invoked from and
EXECUTE the file as an object module.

I figure this is possible, but I don't have time to work on it.  Anyone
care to try this?

Mark.