Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!pshuang From: pshuang@athena.mit.edu (Ping-Shun Huang) Newsgroups: comp.lang.pascal Subject: Re: (TP6.0) Compiled source can't read NFS-network files - WHY? Message-ID: Date: 21 Jun 91 19:27:40 GMT References: <1991Jun14.122203.4946@cs.ruu.nl> Sender: news@athena.mit.edu (News system) Organization: Massachusetts Institute of Technology Lines: 22 In-Reply-To: jschippe@cs.ruu.nl's message of 14 Jun 91 12:22:03 GMT In article <1991Jun14.122203.4946@cs.ruu.nl> jschippe@cs.ruu.nl (Jeroen Schipper) writes: > Upon getting a valid filename, and attempting to read: > error 5 @ 0000:108E > (when given a non-existant file, I'm told rather nicely that fact) > Upon being told to "print" to a filename on a network drive: > error 6 @ 0000:9DC0 It would help us to help you if you would use the addresses the user gave you and track down which lines of source code they correspond to. Also, Turbo Pascal provides an opportunity for your program to do its own I/O error checking (via the "$I" switch); for robustness you should trap such errors and give the user another chance to enter another filename in any case. In any case, error 5 would indicate that the user's DOS is not setting the correct permissions for access to network files, and error 6 suggests that the file handle is corrupt. -- Above text where applicable is (c) Copyleft 1991, all rights deserved by: UNIX:/etc/ping instantiated (Ping Huang) [INTERNET: pshuang@athena.mit.edu]