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

Number   :  9112
Date     :  2004-11-02
Author   :  John
Subject  :  Re: XXCLONE Failure to boot 1st time
Size(KB) :  2


Kan and Dan,

Thanks for your explanations.

Using the GUI I just assumed initial Clone would automatically include the
MBR etc. operations. - guess I should read the release notes more carefully
;-)

Using the GUI I did actually try to select both the Full Clone *and* Repair
options together (so that I could mark MBR to be reset on Full Clone!) -
these button options are mutually exclusive so obviously I could not select
both. What I did not realise is that the resetting of MBR etc. check options
can be selected independently of the Repair button option. Just MHO but the
way GUI presents these options it can give impression that the MBR reset
etc. options are just sub-options of the Repair function.

John


----- Original Message ----- 
From: "Kan Yabumoto" 
To: 
Sent: Monday, November 01, 2004 11:02 PM
Subject: Re: [xxcopy] XXCLONE Failure to boot 1st time


>
>
> 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
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>



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