On Mon, 26 Jul 2004 07:16:49 -0700, "Peter Poulimenakos"
put finger to keyboard and composed:


-----Original Message-----
On Thu, 22 Jul 2004 13:04:42 -0700, "Peter Poulimenakos"
put finger to keyboard and composed:

I am receiving the following error when I try to use
the
xcopy32 command to copy files to a network drive:

'The system cannot find the file specified.'

Now the files it's having a problem with all have a
space
before the filename. ex: " Combined Invoice_NAFTA
Cert.dbf" when I view them in explorer. But when
Xcopy32
tries to copy the above mentioned file it shows the
file
its trying to copy as "_Combined Invoice_NAFTA
Cert.dbf"... And hence can't find the file.

Is there a way to correct this behavior?

The first character in the filename is not a space. To
see what it
really is, drop into a DOS window and execute the
following:

dir *.dbf /b dirlist
debug DIRLIST
-d 100
-d
...
-q

or

dir *.dbf /b dirlist
edit /64 dirlist

Move the cursor over the hidden character and check its
decimal ASCII
"value" at the bottom of the screen.

How are you invoking the Xcopy/Xcopy32 command, ie what
is the exact
syntax? FYI, in a Win DOS box, the Xcopy command
automatically invokes
Xcopy32.

FWIW, I have no trouble creating a filename with a
leading space and
then using Xcopy (or Xcopy32) to make a copy of it. The
following
commands work as expected in a Windows DOS box.

rem " junk1" ------ creates a zero byte file
xcopy " junk1" " junk2"


- Franc Zabkar
--
Please remove one 's' from my address when replying by
email.
.



Hi Guy and thanks for the replies,

I havent had a chance to try out your DOS command (dir
*.dbf /b dirlist) just yet, ...

This procedure takes about one minute and may help explain why your
two PCs behave differently. At the very least, if we knew the byte
value(s) of the leading character(s) we may at least be able to
reproduce your problem on our machines.

but below is the command
I'm using to copy the files:

xcopy32 c:\fedext~1\*.* z:\fedex_trade /a/d/s/y

I've also used the /k/c witches without any success as
well... I've used this command on several 98se PCs with
success copying files with 'spaces' at the begining of
the file name, it's just this one PC that is giving me
trouble (98se as well).

Below is a DOS level directory dump comparison between
two PCs where the files copied successfully and my
problem PC.

Good PC: (as in the 'spaced' files will copy)
Volume in drive C is WIN98-2
Volume Serial Number is 0675-17E7
Directory of C:\FedEx Trade Networks Forms

HELP-N~1 FOF 50,228 25/07/02 18:25 Help-NAFTA
Certificate.fof

ÿCOMBI~1 DBF 13,914 29/01/03 10:11 ÿCombined
Invoice_NAFTA Cert.dbf


Problem PC: (as in the 'spaced' files will not copy)
Volume in drive C has no label
Volume Serial Number is 6D59-1A1C
Directory of C:\FedEx Trade Networks Forms

HELP-N~1 FOF 50,228 07-25-02 6:25p Help-NAFTA
Certificate.fof

_COMBI~1 DBF 13,914 01-29-03 10:11a _Combined
Invoice_NAFTA Cert.dbf

I notice that the two PCs use different date and time formats. Could
this be significant?

Are the filenames generated by the software, or are they created
manually? My newsreader sees the leading character in the first dir
listing as a lower case y with an "umlaut", whereas the leading
character in the second listing is an underscore. The fact that these
two characters are different is puzzling. Did you transcribe either
listing by hand, or did the same software generate two different
leading characters? In any case, I'm puzzled why there should there be
any non-ASCII leading characters at all.

This may be a red herring, but the ALT 0255 combination (numeric
keypad) displays the aforementioned lower case y when executed in a
Windows app such as Wordpad, while ALT 255 produces an ASCII
underscore (= ALT 095).


- Franc Zabkar
--
Please remove one 's' from my address when replying by email.