Path: utzoo!utgpu!news-server.csri.toronto.edu!qucis!cox
From: cox@qucis.queensu.CA (Donald Cox)
Newsgroups: comp.os.minix
Subject: emacs not executable
Message-ID: <1107@qusunb.queensu.CA>
Date: 9 Mar 91 15:19:47 GMT
Distribution: na
Organization: Queen's University, Kingston
Lines: 29

Hello! I've got a problem.  I recently upgraded from standard MINIX for the
PC version 1.5, straight from PH, to 386-MINIX. Thank you very much Bruce
Evans, even though you probably won't see this.  I used John Nall's tutorial.
It went like a charm.   Thank you very very much John!  Everything seems
to have gone well with the upgrade.  My problem is with emacs.  I got it
from plains (thank you very much Glen Overby for maintaining this treasure-
trove of taty treats).  I also got 16bcompress and it suffered a similar fate.

I have a Compaq Deskpro 386 with 2Meg memory, a 200MByte IDE drive, and no
complaints, so far.  I'll describe the situation with emacs.  I had binary set
when I ftped it from plains to the local system, and also set when I kermitted
it from the system to my machine.  The file uncompressed and untared fine.
ctags and etags run great.  When I try to run emacs I get one of two messages:
if I just type 'emacs' I get a response 'emacs not found'.  Other executables
are in the same directory and they are found.  If I use an absolute path like
'/usr/local/bin/emacs' I get the response 'emacs: cannnot execute'.  I've
tried chmoding it, chowning it, and chmeming it with no succes.  I've got
about 700 Kbytes memory free.  In my experimenting I've come to the conclusion
that someone is not looking at emacs as executable, contrary to what I am 
trying to tell it.  I get a similar responses if I chmod -x one of the working
programs.  I ran the like program described in John's tutorial, and it says it
is 386able.  As I've said, I had similar problems with 16bcompress?  Any ideas?
Any suggestions?  Oh I dearly love my emacs and would like to get it on my
home machine.  Besides, it is a good excuse for more memory :-)