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

Number   :  4386
Date     :  2003-04-20
Author   :  Kan Yabumoto
Subject  :  Re: (unknown)
Size(KB) :  2



Mike:

I say a lot of things to a lot of people and I can't keep track
unless you remind me what I said to you (it seems getting worse
every year as we age :-)

Anyway, let me guess what I said and give you a suggestion.

Apparently you are doing a large-scale copy operation using
XXCOPY16. This is based upon our experience that although
the "out-of-memory" message could happen in both XXCOPY and
XXCOPY16, the chance of seeing the message from XXCOPY (32-bit)
in a typical Windows computer is negligibly small while
XXCOPY16 lives in the 640 KB world (about several hundred
times smaller memory space), the out-of-memory condition
is an issue (and increasingly so). It is only recently
that we started to notice more and more people started
to observe the condition --- when XXCOPY16 was invented,
typical volume contained only few hundred MM (few thousand
files at most).

Anyway, we have to write a better program to reduce the
memory usage so that only the absolute-minimum will be
allocated (we can certainly do better than this). On
the other hand, even if we cut down the memory usage into
one quarter or even less, it will be inevitable that
the users will see the same error condition when the
job size become 100 times larger (that is an inevitability
according to Moore's Law).

The cure for this is write a command line as an incremental
backup (add /BI to the command line).

xxcopy16 \src\ \dst\ /bi /s

Whenever you encounter the "out-of-memory" condition, you
can run the same command immediately after. The subsequent
run will skip the files that have been successfully copied
in the fist run. That is, although you may result in
an "out-of-memory condition, a substantial progress will be
made every time.

Kan Yabumoto
==========================================================

At 2003-04-19 20:21, you wrote:
>i did what you told me and after 1 gb it stopped saying that the job was to
>large and then says invalid command.com enter correct name of comand
>interpreter (eg, c:\command.com). i needed to send a total of 19 gb to my 80
>gb second hard drive is there anyway to finish the job or make it go all the
>way through and what should i enter for the invalid comm?
>
>thanks for your help



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