Xref: utzoo alt.msdos.programmer:1164 comp.lang.pascal:3040 comp.protocols.nfs:690
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!jarthur!uci-ics!gateway
From: milne@ICS.UCI.EDU (Alastair Milne)
Newsgroups: alt.msdos.programmer,comp.lang.pascal,comp.protocols.nfs
Subject: Turbo Pascal 5.0 and network drives
Message-ID: <9002052041.aa16803@ICS.UCI.EDU>
Date: 6 Feb 90 04:43:19 GMT
Lines: 25


   We are using Turbo Pascal 5.0 in a setup where some of the search paths
   for units (.TPU files) and include files include PC-NFS remote drives.
   While this arrangement works for the most part perfectly well, there 
   is a specific circumstance where Turbo seems unable to see the remote 
   drives: when a unit is listed in a USES statement whose name is over 8 
   characters long, or when, in positioning the source to the line where 
   an execution break has just occurred, the source file belongs to a unit
   whose name is over 8 characters.

   When this happens on a local drive, Turbo correctly truncates the name 
   to 8 characters, adds the .TPU or .PAS extension, and finds it among 
   the given directories.  But when the file it needs is on a remote drive,
   it does not find the right directory to search.

   These same searches work fine when the name is shorter than 8 characters.

   Has anybody else seen this?  Does anybody know why it happens, or (bette)
   how to fix it?  Duplicating these units on all the individual machines
   would not be a pleasant solution.


   Thanks for any help,

   Alastair Milne