Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!sdcc6!sdcc19!zz1he From: zz1he@sdcc19.ucsd.EDU (Heather Ebey) Newsgroups: comp.sys.ibm.pc Subject: Turbo C and network Keywords: c network Message-ID: <211@sdcc19.ucsd.EDU> Date: 28 Jul 88 15:55:38 GMT Distribution: na Organization: University of California, San Diego Lines: 36 I am having a problem running Turbo C ver. 1.5 under PC-NFS 3.0a; tc, the Turbo C integrated environment does not recognize the remote drive, E:, which is on the server. Per Borland, Lee in Technical Services (408)438-5300, the ability to load source code from a remote drive was not written into TC. This makes it real difficult to use in a lab environment. We purchased a copy of Turbo C for each PC and loaded it on drive C:. Students are supposed to keep their homework assignments on drive E:. Drive E: is a remote drive on the server, which is the the particular user's private, password protected directory. The Turbo C integrated environment will recognize the remote drive, E:, but it will not load or save files to the remote drive. NFS shows a steady blip for about a minute (this means it is attempting to access something on the server) and then something (TC?) displays the message "Critical Error, Disk is not ready in drive E. Retry or Abort" Retry just repeats the same. Abort displays the message "Error: Invalit drive or directory. Press ESC." This problem exists even if I start tc from drive E:. One of the faculty was experimenting with all variations of this problem and crashed two harddisks. In view of this, I think I'll have to take tc out of the microlab. Too bad, it is such a nice learning environment. Has anyone seen this problem? Is there a solution? A patch? Heather Ebey UCSD, ACC MicroLab Manager -----------------INTERNET: hebey@ucsd.edu-------------------- Heather Ebey Voice: (619) 534-2448 UCSD, Academic Computing Center, C-010, La Jolla, CA. 92093 -----------------BITNET: hebey@ucsd.bitnet------------------