Xref: utzoo comp.sys.ibm.pc:38311 comp.emacs:7214
Path: utzoo!utgpu!watmath!iuvax!pur-ee!mentor.cc.purdue.edu!j.cc.purdue.edu!nwd
From: nwd@j.cc.purdue.edu (Daniel Lawrence)
Newsgroups: comp.sys.ibm.pc,comp.emacs
Subject: Re: Micro-Emacs & PC Lan 1.30 Conflict?
Summary: uEMACS Networks
Keywords: uEMACS Networks
Message-ID: <10405@j.cc.purdue.edu>
Date: 16 Nov 89 22:23:06 GMT
References: <1989Nov16.153204.10926@chinet.chi.il.us>
Reply-To: nwd@j.cc.purdue.edu (Daniel Lawrence)
Followup-To: comp.sys.ibm.pc
Organization: Purdue University
Lines: 54

In article <1989Nov16.153204.10926@chinet.chi.il.us> megabyte@chinet.chi.il.us (Dr. Megabyte) writes:
>Help! I've been happily using pc micro emacs version 3.9 for years now
>on my IBM pc, but now we have installed IBM PC Lan V1.30 and everytime
>I run emacs I get a 
>
>Net 803:  Network Path Not Found
>Abort, Retry, Fail?
>
>error.  This is weird! emacs.exe and emacs.rc are located in my c:\lcmds
>directory which is in my PATH statement.  To boot, there are no network
>directories in my PATH.

	At the time this occurs, MicroEMACS is probably searching all
the directories on the path looking for a startup file.  Try playing
with your path and see if you can isolate it to a particular device or
directory.  I suspect that it will have something to do with one of the
network drives.

>Now, this only happens when I run PC LAN 1.3 Extended Services.  When I'm
>running as a stand alone PC, micro-emacs works fine.  When I run under
>PC LAN base services, I can run micro-emacs fine, but when I run the
>extended services, I get the error message.
>
>Here is the kicker: Of course, I get my 'C;\' prompt back when I pick
>'Abort', I get the same message again when I 'Retry', but when I
>'Fail' emacs goes on and runs as if nothing had happened!!

	When you hit fail, DOS returns a failure on the open, emacs
assums it can't get a startup file there... and on it goes.

>Now, I guess I could just hit an 'f' everytime I run emacs and learn
>to live with it, but I can't help but feel something can and should
>be done about it.

	agreed, this sounds ugly.

>Does anyone have a fix for this or at least some ideas on why I might
>be getting this error? Any help would ne appreciated.

	Also some networks, NETWARE v2.0 and below, mis implimented the
DOS $4B EXEC call... it ended up trashing the STACK, thus emacs hung
whenever it went to execute things.  I fixed this in 3.10 with a special
define and some assembly code to save/restore the stack around the call.

>Mark E. Sunderlin: IRS Technocrat in Winchester, VA 

	I am not sure exactly what this can be, but if you will assist
by answering the hords of questions I am likely to ask, I will try to
help you hunt it down.

			Daniel Lawrence  voice: (317) 742-5153
					  arpa:	dan@midas.mgmt.purdue.edu
				The Programmer's Room 
				Fido: 1:201/10 - (317) 742-5533