🚀 go-pugleaf

In article <.116@ccs.carleton.ca>, @ccs.carleton.ca writes:
> 
> In article <1992Nov18.040449.20732@vpnet.chi.il.us> cgordon@vpnet.chi.il.us (gordon hlavenka) writes:
> 
> > mtl92205@dit.upm.es (Pablo Varela) writes:
> >>      I've tried truename, and what it seems to do it's giving
> >>you the full name of a file, that is, if you are in c:\windows, and 
> >>type truename win.com it will say c:\windows\win.com, and if you say 
> >>truname ..\bin\pkunzip.exe it will say c:\bin\pkunzip.exe.
> 
> >Hmmm...  I just shelled out and tried "truename pkunzip.exe".  It
> >returned "D:\TELIX\PKUNZIP.EXE" although pkunzip is actually in
> >C:\UTIL.  Next I tried "truename nosuch.fil" and got
> >"D:\TELIX\NOSUCH.FIL".  So I guess we can see why it's undocumented :-)
> 
> The problem here is that you have assumed that truename finds the 
> fully qualified name of an actual file. There are several versions of the 
> UNIX which program which will find the correct file.
> 
> Truename in this context, returns the FULLY QUALIFIED name of a file.
> Basically, it lets you know the file DOS would access given the string 
> provided. This does not imply that the file exists, simply what Drive:\
> directory\name.ext would be used. 
>  
> 
> 
Syntax: TrueName [Drive:] [\Directory] [Name.Ext]     [] = optional

Note: It does not always return Drive:\Directory\Name. If the Drive specified is network
      Drive, the return format is \\ServerName\VolumeName\Directory, but if you specified 
      a Name.Ext with no Directory and the current Directory for the network drive is  
      the root, then the return format is \\ServerName\VolumeName\\FileName.Ext

The DOS command CD accepts the format returned above.  Be careful though, if your current drive
is a local non-networked drive and you issue a CD \\ServerName\VolumeName\Directory command,
DOS will map the Networked drive to your local drive. 
By the way, after issuing the above command, we are unable to get back to the local Hard-
drive without re-booting!