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

Number   :  9144
Date     :  2004-11-05
Author   :  marekyarbrough
Subject  :  Re: Failure to copy to CD
Size(KB) :  3



Found that when I removed an old copy of the xxcopy executable from a 
directory under the directory that the batch file executes 
from ....problem went away (despite the xxcopy home directory being 
windows\system32

Thanks,
marek

--- In xxcopy@yahoogroups.com, "marekyarbrough"  
wrote:
> 
> In my case after months (if not years of successful burning), I 
have 
> the same error code 40. I have updated to the latest version of 
> XXCOPY, installed the /NX0 switch and disabled the anti-virus auto-
> protect. Still am getting the failure...any thing else to try?
> 
> Thanks,
> marek
> 
> 
> --- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:
> > Russell wrote:
> > >
> > > Kan, Thanks for the response.
> > > I added /EC and got this output:
> > >
> > > xxcopy "Weekly CDRW backup 20041026.zip" p:\ /V /EC
> > >
> > > XXCOPY == Freeware == Ver 2.85.8 (c)1995-2004 Pixelab,
> > >
> > > ------------------------------------------------------------
> > > D:\backup\historic backups\Weekly CDRW backup CDRW backup
> > > 20041026.zip 586,843
> > > ------------------------------------------------------------
> > > Directories processed = 1
> > > Total data in bytes = 586,843
> > > Action speed (MB/min) = 15.65
> > > Files copied = 1
> > > Exit code =0 (No error, Successful operation)
> > >
> > 
> > 
> > Russell:
> > 
> > At first, my guess was that your problem was that XXCOPY
> > did not find the file specified by the command line.
> > Now, with more details provided, a different picture
> > emerged.
> > 
> > From the XXCOPY status lines at the end, we can see that
> > as far as XXCOPY was concerned, the file-copy operation
> > had been successful. It is therefore, the responsibility
> > of the "file system" --- the packet-writing utility that
> > physically records the information on the media and
> > makes all the necessary bookkeeping chores on the media.
> > 
> > If your observation that XCOPY is successful and XXCOPY
> > is not can be repeated, then, we have to look into the
> > difference between XCOPY and XXCOPY.
> > 
> > One thing XXCOPY does differently is the SFN-preservation
> > feature. You may try adding the /NX0 switch that
> > unconditionally disables the futile SFN-preservation
> > operation on a CD-RW. (XXCOPY by default, checks whether
> > the destination volume is In-CD or DirectCD --- two
> > popular packet writing products, and automatically
> > disables the /NX feature.) Adding the /NX0 ensures
> > that the messy /NX operation (that repeatedly creates,
> > renames and deletes files at the destination directory)
> > will not take place.
> > 
> > I think that one important thing to remember when operating
> > a packet-write utility is to make sure that the buffered
> > data are properly flushed to the media and the write
> > session successfully completed before you remove the media
> > (or turn off the computer).
> > 
> > If your system runs an AntiVirus tool on a continual
> > basis, I suggest that you turn it off that might
> > interfere with file-write on the CD (we have seen a case
> > where a stupid AntiVirus opens the file that was created
> > on a volume (including CD-RW) immediately after the newly
> > created file is closed and try to scan for a possible virus).
> > 
> > At this moment, I just can't think of anything else
> > that might solve your problem. Let me add that we have
> > received a number of reports that packet-writing tools
> > are not that reliable (or, "temperamental" and difficult
> > to tame).
> > 
> > Kan Yabumoto



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