home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!udecc.engr.udayton.edu!blackbird.afit.af.mil!dsacg3.dsac.dla.mil!dcsc.dla.mil!cp01395
- From: cp01395@dcsc.dla.mil (Duane L. Rezac)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: PCNFS won't allow certain files names to be copyed
- Message-ID: <1539@dcsc.dla.mil>
- Date: 20 Jul 92 12:08:50 GMT
- References: <1992Jul16.225358.14393@trl.oz.au>
- Organization: Defense Construction Supply Center, Columbus
- Lines: 31
-
- From article <1992Jul16.225358.14393@trl.oz.au>, by rick@medici.trl.OZ.AU (Rick Coxhill):
- > We have PC/NFS version 4.0.
- >
- > Using the file manager in windows 3.1 or in DOS I cannot copy DOS
- > files with names of the form xxxx.~xx from a local drive
- > to a networked drive. Copying between local drives is OK.
- >
- > File names of this form are created in Turbo C++ for Windows.
- >
- >
- > Email: r.coxhill@trl.OZ.AU Tel: 61 3 253 6249 Fax: 61 3 253 6173
- > Rick Coxhill. Telecom Australia Research Labs. Clayton. Vic. Australia
-
- Some programs send blanks to fill in the unused filenane characters
- (i.e if x=space, they will send xxxxxfoo.bat instead of foo.bat)
- PC-NFS will choke on this unless you use the /s option on pcnfs.sys.
- this tells PC-NFS to send embedded blanks that are in a file name
- instead of truncating them. (Harvard graphics is an example of a
- program that will do this - it can not find it's support files if
- they are on a mounted drive unless the /s flag is used. )
-
-
-
-
-
- Duane L. Rezac
- --
- +-----------------------+---------------------------------------------------+
- | Duane L. Rezac |These views are my own, and NOT representitive of my place|
- | drezac@dcsc.dla.mil of Employment. |
- +-----------------------+---------------------------------------------------+
-