UPGRADING REPAIRING PCs

134
Because the only hidden files such a system would have were probably
the operating system boot files (already installed) and the
Windows 3.1 permanent swap file (which could be re-created after
restarting Windows), this “free” data transfer routine worked well
for many people.
After the original drive was removed from the system, the new
drive would be jumpered as master and assigned C:. You would
need to run FDISK from a floppy and set the primary partition on
the new C: drive as Active. Then, exit FDISK and the drive would
boot.
Drive Migration for Windows 9x/Me Users
Windows 9x and Me have complicated the once simple act of data
transfer to a new system by their frequent use of hidden files and
folders (such as \Windows\Inf, where Windows hardware drivers
are stored). The extensive use of hidden files was a major reason for
a greatly enhanced version of XCOPY, known as XCOPY32, to be
included in Windows 9x and Me.
Note
Chapter 4—SCSI and IDE Hard Drives and Optical Drives
XCOPY32 is automatically used in place of XCOPY when XCOPY
is started within a DOS session under Windows. XCOPY32, as
the name implies, must be run within Windows.
XCOPY32 for Windows 9x Data Transfer
Compared to the classic XCOPY, XCOPY32 can copy hidden files;
preserve file attributes such as system, hidden, read-only, and
archive; automatically create folders; and is compatible with long
filenames. Thus, using it to duplicate an existing drive is possible,
but with these cautions:
• The XCOPY32 command is much more complex.
• Errors might occur during the copy process because of
Windows’ use of temporary files during normal operation,
but XCOPY32 can be forced to continue.
This command line calls XCOPY32 and transfers all files and folders
with their original attributes intact from the original drive (C:)
to the new drive (D:). This command must be run from an MS-DOS
session under Windows 9x or Me:
xcopy32 c:\. d:\/s/c/h/e/r/k