home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!gossip.pyramid.com!pyramid!infmx!neptune!bradl
- From: bradl@neptune.informix.com (Brad Levy)
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: Truename (was undocumented dos)
- Message-ID: <1992Nov20.055341.5262@informix.com>
- Date: 20 Nov 92 05:53:41 GMT
- References: <1992Nov18.040449.20732@vpnet.chi.il.us> <.116@ccs.carleton.ca> <1992Nov19.144944.6624@den.mmc.com>
- Sender: news@informix.com (Usenet News)
- Organization: Informix Software, Inc.
- Lines: 41
-
-
- I've notice (dos 5, haven't tested w/others) that truename will also use
- a forward slash in the returned path/filename if the argument to truename is
- recognized as a device (i.e., lpt1, con, nul, clock$, ...)
-
- C:\>truename lpt1
- C:/LPT1
-
-
- Now, if E: and P: are both mapped to the same PCNFS server, (different
- mount points on the server), with P mounted first, I get the following
- interesting results:
-
- E:\>truename lpt1
-
- P:/LPT1
-
- E:\>truename xyz
-
- \\E\XYZ
-
- E:\>p:
-
- P:\>truename lpt1
-
- P:/LPT1
-
- P:\>truename xyz
-
- \\P\XYZ
-
-
- Note that the handling is different for devices, both in returning a
- drive-letter-and-colon instead of \\driveletter, and in not necessarily
- returning the same drive "letter" as the current drive. Perhaps this has
- to do with the SUBST behavior the originator of the thread on truename
- alluded to?
-
- -brad
-
- drive
-