xcopy "insufficient memory" (Win XP)
St_Z
entire Documents and Settings folder using xcopy. I've been successful in
actually creating the required script, but when running it i get an
"insufficient memory" error after about 750MB of data. Is there anyway I
can stop xcopy trying to cache the whole lot before writing it?
Better still, I would be interested in getting hold of any program that will
back up (and compress) my Windows, Program Files, Documents and Settings and
root folders from a DOS prompt, retaining all attributes and most
importantly long file names. Anyone know of an app that can do this? I am
fed up of reinstalling windows every few months and would prefer the easy
approach of simply renaming these system folders and restoring them from a
backup without getting sharing violations!
Any help greatly appreciated, thanks :)
Paul
Ted Davis
Since MS chose with NT to make the system essentially impossible to
backup while it's running, backups are often done by imaging the
entire drive. A common approach is to create three partitions on the
drive: an NTFS partition for the OS and major applications, another
NTFS partition for user files (files that *can* be copied while the
system is in use), and a DOS partition for the image and zip archives,
and the imaging software. A DOS boot floppy is used to boot the
system with the DOS partition visible, and something like Ghost is
used to make or restore the image of the boot partition - the other
files are managed with Winzip or something similar from inside
Windows. The boot disk is often made with DOS 7 so that FAT32 can be
used for the image artition. Using images of working systems also
solves the repair problem (Windows tends to get tired and needs to be
reinstalled at intervals) - just restore the system partition to a
known working state.
T.E.D. (tda...@gearbox.maem.umr.edu - e-mail must contain "T.E.D." or my .sig in the body)
St_Z
news:7uj7ouc32tda2jc4b...@4ax.com...
Thanks for the info Ted. I am happy to use an imaging program like Norton
Ghost (and have done in the past), but I have a further 50GB of data (aside
from these three system folders) that I don't want to back up. All I want
to be able to do is to go to a command prompt (not a DOS box), rename the
folders to WIN.OLD, DOCS.OLD and PROGS.OLD, then restore the backed up
folders, thus returning the OS to the exact state it was when I backed it up
without having to completely wipe my hard drive by restoring an image. I
have tried Xcopy and Winzip's command line add-on but neither was
successful. I have searched for hours on the internet for a program that
will do it, but no luck anywhere :(
Any more ideas?
Paul
Ted Davis
<iamthe...@bigfoot.com> wrote:
>"Ted Davis" <tda...@fidnet.com> wrote in message
>news:7uj7ouc32tda2jc4b...@4ax.com...
>> On Sat, 14 Sep 2002 22:07:02 +0000 (UTC), "St_Z"
>> <iamthe...@bigfoot.com> wrote:
>>
<snip>
>Thanks for the info Ted. I am happy to use an imaging program like Norton
>Ghost (and have done in the past), but I have a further 50GB of data (aside
>from these three system folders) that I don't want to back up. All I want
>to be able to do is to go to a command prompt (not a DOS box), rename the
>folders to WIN.OLD, DOCS.OLD and PROGS.OLD, then restore the backed up
>folders, thus returning the OS to the exact state it was when I backed it up
>without having to completely wipe my hard drive by restoring an image. I
>have tried Xcopy and Winzip's command line add-on but neither was
>successful. I have searched for hours on the internet for a program that
>will do it, but no luck anywhere :(
>
>Any more ideas?
Well, I have found a scheme that allows copying open files across a
network but it is the sort of thing my boss told me to "document the
hell out of": mount the space on a Linux box as an smbfs mount, then
export it through NFS and remount the NFS share from localhost as a
Samba share, which can then be mapped on the original machine and
copied from. I haven't tried that exact pattern: the task is to make
files in the working directory for a networked DOS 6.22 system
readable even though the DOS system has them open - we are currently
using a Netware server, but we have to give up all netware on campus
due to a combination of financial woes and a misguided drive to make
the entire university a purely Microsoft shop, regardless of the (very
high) cost and (very severe) losses in functionality and performance.
Linux is still tolerated, though support for HP-UX has been dropped,
and support for Solaris and Macs has been cut back.