[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  4332
Date     :  2003-04-17
Author   :  Garry Deane
Subject  :  Re: copy failed.
Size(KB) :  1


--- In xxcopy@yahoogroups.com, anders thoresson  wrote:
> Strange thing is that not a single one of the files that
> xxcopy fails to copy has been touched in weeks. I'm trying
> to copy from a NTFS harddrive to a FAT32 ZIP drive under
> Windows XP Professional. Here is my log:
>=20


> Warning: Failed timestamp (J:\d\documents and settings\anna\mina=20
> dokument\1. Unga Nyheter\Produktion\3.Faktamaterial\1.=20
> Nyhetsfakta - UN\V=E4rlden)

> Warning: Failed timestamp (J:\d\documents and settings\anna\mina=20
> dokument\1. Unga Nyheter\Produktion\3.Faktamaterial\H=F6gtider)

> Warning: Failed timestamp (J:\d\documents and settings\anna\mina=20
> dokument\1. Unga Nyheter\=D6vrigt)


Since xxcopy works when copying from/to the HDD and both xxcopy and=20
explorer fail when copying to the Zip drive, it suggests the problem=20
is with the ZIP disk driver. This is just a shot in the dark but 5 of=20
the 7 failed copies were to directories being created with names=20
which include unicode characters "=E4 =F6 =D6". Maybe the Zip disk driver=20
isn't able to handle these correctly and the directories aren't being=20
created or are being created with an un-accented character.=20
Thereafter you get the "Failed timestamp" and "Copy failed" messages=20
from Xxcopy.

You could check whether these directories actually exist on the Zip=20
drive. If not, do other directories with unicode characters exist.=20
Also, can you create the directories using an MD command and/or copy=20
the files using a COPY command. If you can't do this with basic=20
commands, it points to a problem with the Zip disk driver. Your only=20
solution may be to get an updated driver.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.