From: Mark Bell (electrosoft_at_earthlink.net)
Date: Thu Feb 01 2001 - 17:20:44 EST
I've xcopy32'd well over 50 times, and I haven't encountered this well
documented
problem (I read it, compared registry readings, recounted the # of times
Windows
lost track of files, stepped through my registry, said, "oh well, It's only
a file
association! I can fix that myself or I can run nbg registry fixer!)). :)
If anyone wants a caveat
and good read on it, try:
http://navasgrp.home.att.net/tech/clone_copy.htm
I am curious as to who on the list has encountered a problem with Xcopy32 and
file name associations? But in reflection of Michael's words, be careful of
using
Xcopy32 unless you are potentially comfortable working with regedit, parsing
registries in a real dos session, or uncomfortable with DOS as a whole. If you
want the safe, easy way, go with one of the tried and tested cloning solutions.
I'm very cheap (er, frugal), and feel comfortable with the Windows registry and
DOS on all fronts, so it doesn't phase me. I welcome the day it happens....
BRING IT ON!!!! >;-)
Mark
At 10:15 AM 2/1/01 -0800, you wrote:
>Folks, there is a *big* problem with using XCOPY to clone a drive. It does
>not guarantee that you'll get the same short filename aliases on the new
>drive.
>
>Mark, you said you've used XCOPY a number of times successfully. You've been
>very lucky that you haven't gotten bit by the short filename problem. But
>keep at it and you will... <g>
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:56:49 EST