Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!ucsd!sdcc6!sdcc19!zz1he
From: zz1he@sdcc19.ucsd.EDU (Heather Ebey)
Newsgroups: comp.sys.ibm.pc
Subject: Turbo C and network
Keywords: nfs network tc
Message-ID: <212@sdcc19.ucsd.EDU>
Date: 29 Jul 88 22:21:08 GMT
Distribution: na
Organization: University of California, San Diego
Lines: 33

This is a continuation of the problem, with more details.
I have Sperry PC/IT's running MS-DOS 3.1 and 3.2 with PC-NFS 3.0.
connected to a NFS server on a Celerity.

I tried tc from the remote drive E:, using the tc menu (Change 
directory, then Load and then tried just Load with the complete 
path e:\tmp\hello.c) and even "tc hello.c" from the directory 
where hello.c exists.

Also, I loaded the entire Turbo C package to drive E: and tried it
from there.  It happily reads in any file that exists on drive C:,
no matter where I start tc, and no matter where tc.exe lives, drive
C: or drive E:.  I've seen it display e:noname.c in the edit box,
then give me the usual messages:

  "Critical Error, Disk is not ready in drive E. Retry or Abort"
   followed by,
  "Error: Invalid drive or directory. Press ESC."

I press ESC, THEN IT LOADS THE FILE "E:NONAME.C", if it exists, 
and completely ignores the file which I requested.

The same thing happens on four different Sperry's.  Each has a
different environment.

Any ideas?

	--Heather

-----------------INTERNET: hebey@ucsd.edu--------------------
Heather Ebey (ACC MicroLab Manager)  Voice:  (619) 534-2448
UCSD, Academic Computing Center, C-010, La Jolla, CA. 92093
-----------------BITNET:  hebey@ucsd.bitnet------------------