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

Number   :  5335
Date     :  2003-08-16
Author   :  Garry Deane
Subject  :  Re: "Insufficient memory"
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "Colin Culpitt-Smith"  
wrote:
> Can anyone help with this please?
> 
> I have successfully used XXCOPY under Win98SE to clone my
> boot drive (HD1) to a slave drive (HD2). I then reformatted
> HD1, & tried to copy HD2 back to HD1, using XXCOPY16 under
> true Dos. This was part of an experiment to find a fix for
> the long filename problem! More of this later, as I'm sure
> I have a fix!
> 
> All seemd to go well, until XXCOPY16 aborted with the
> error message, "Insufficient memory (Job too large) Cannot
> continue". On checking HD1, I found that only some of the
> folders/files had been copied. I ran XXCOPY16 again, & more
> folders/files were copied, but it aborted with the same error
> message as before.
> 
> I have a modern 2gHz CPU with 512mB of memory, so why does
> XXCOPY16 fail?
> 
> I tried using various XXCOPY16 switches:- /clone, /bu, &
> /c/e/h/k/r/y/pb - but all had the same result.
> 
> I'm now at a loss as to how to get XXCOPY16 to run normally.
> Can anyone advise please?

In real DOS, Xxcopy16 operates in what's left of a 1Mb memory
space after memory is used for the OS and reserved for screen
memory, BIOS and such. Unless you have enabled the use of
extended memory and optimised the use of upper memory, DOS
programs will usually only have about 550kb-600kb to work with.
Since xxcopy16 occupies about 240kb, there's probably only about
350kb of memory left for xxcopy data.

Whilst you could improve this with some tweaking, it's probably
not going to do that much good. The simplest thing at this stage
is simply to continue running xxcopy16 repeatedly until it gets
the job done. If you use:

xxcopy16 d:\ e:\ /bu

it will get a bit more done each time and eventually get there.
If you want, you could create a small batch file as follows:

@echo off
:loop
xxcopy16 d:\ e:\ /bu
if not errorlevel 100 goto loop

Just set it running, watch it for a few cycles then take a walk.

It's probably a moot point now (although maybe not) but you
should have made your HD2 a bootable drive. If the contents of
that drive are an exact copy of HD1, you could boot to HD2 and
copy the contents back to HD1 within windows. This negates the
memory issue because the full amount of physical and virtual
memory is used. http://www.xxcopy.com/xxcopy10.htm explains
how to make a second hard drive into a bootable drive.

Garry



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