Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcrware!jejones
From: jejones@mcrware.UUCP (James Jones)
Newsgroups: comp.os.os9
Subject: Re: Can't execute "J" - Error #000: 216
Message-ID: <6918@mcrware.UUCP>
Date: 15 Jun 91 14:55:18 GMT
References: <1991Jun14.202821.20308@unhd.unh.edu>
Reply-To: jejones@mcrware.UUCP (James Jones)
Organization: Microware Systems Corp., Des Moines, Iowa
Lines: 18

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.

Check the attributes of the files you're trying to execute.  The "can't
execute 'J'" message is from the shell, which, after trying other possibil-
ities, is trying to run the executable as a shell script!  (Dump the file
and see what the first byte looks like. :-)  You should set the execute
attributes of the file and try again.

	James Jones