Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!cernvax!chx400!urz.unibas.ch!balmer
From: balmer@urz.unibas.ch
Newsgroups: comp.os.os9
Subject: Re: Can't execute "J" - Error #000: 216
Message-ID: <1991Jun15.165142.1642@urz.unibas.ch>
Date: 15 Jun 91 15:51:42 GMT
References: <1991Jun14.202821.20308@unhd.unh.edu>
Organization: University of Basel, Switzerland
Lines: 21

In article <1991Jun14.202821.20308@unhd.unh.edu>, ram@kepler.unh.edu (Richard A Messner) writes:
> I have encountered the above error ('Can't execute "J" - Error #000:216')
> several times when trying to execute precompiled binaries for OSK.  There
> is no specific binary that gives this problem.  They all seem to do it unless
> they have been compiled on my machine (for example, the binary for C-Kermit
> on smilodon.cs.wisc.edu causes this error).   Does anyone know what the problem
> is?  I can't find a file named J anywhere in the standard directories.
> 
> The system in question is a Motorola MVME-133A-20  running Professional
> OS-9/68020 version 2.2.  Thanks.

You have to place the executable file in your default execution directory
(you max change this with the chx command) or set the directory, in which
your binary resides, in the environment variable PATH. You could alternally
load the file with load -d filename prior to execution.

J is the first byte of all OS-9 executables, dump a few and you'll see..

- Marc

BTW: Error 216 means "File not found"