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

Number   :  9106
Date     :  2004-11-01
Author   :  Kan Yabumoto
Subject  :  Re: XXCLONE Failure to boot 1st time
Size(KB) :  1



John wrote:
>
> Testing xxclone on XP Pro:-
> 1. Installed new 2nd IDE drive as slave.
> 2. Initialised new drive single ptn NTFS (200gb).
> 3. XXclone (full clone) drive 0 (160gb FAT32) to new
> drive 1 -reported finished OK and bootable.
> 4. Swapped slave and master jumpers on drives.
> 5. Tried reboot - got message agter POST "Press any key to boot"
> .. press a key and repeats ad infinitum.
> 6. Swapped drive jumpers back.
> 7. Used XXclone to reset MBR on new drive.
> 8. Swapped jumpers again and rebooted with just new drive
> installed.
> 9. This time came up with "this is 1st boot after xxclone op "
> etc. and XP Pro working.
> 10. Installed orginal drive back in and working OK too.
>
> Not sure what went wrong 1st time - or is this expected?
>

With recent versions of XXCLONE, we made the default behavior
of XXCLONE a little bit conservative by not re-initializing
the MBR, BootSector, and/or BOOT.INI unconditionally. This is
because a relatively small group of users have their non-standard
setup that should not be changed. The current scheme will
undoubtedly make more inconveniences as John experienced. But,
the old scheme of initializing the three key items unconditionally
would cause more serious problems to those who get adversely
affected. I wish XXCLONE could do a better job in determining
when or when not to re-initialize the key data objects but
that's not very easy.

Kan Yabumoto



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