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

Number   :  7920
Date     :  2004-05-19
Author   :  Kan Yabumoto
Subject  :  Re: Disk not bootable
Size(KB) :  2



brayshaw36 wrote:
>
> When I use XXCLONE version 0.21.2 to copy a 20Gb Maxtor disk
> (which was originally created by XXCLONE) onto an ExcelStor
> Model 340 40Gb disk the target disk is not bootable.
> Both disks are connected via IDE, BIOS reports as expected,
> both are Fat32.
>
> Fdisk confirms active Fat32 partition of 39+Gb for target disk.
>
> Have tried XXCLONE several times and ensured firewall and virus
> software is disabled.
>
> I have used W2K Disk management to confirm that the disk is
> Basic not Dynamic.
>
> I have also used XXCLONE option to make target disk bootable
> and copy registry but disk still does not boot.
>
> The boot failure results in a message saying run Scanreg
> but W2k will not even load enough code to allow this to happen.
> Lots of error message occur when attempting to run in
> Command Prompt Mode including one which says cannot find Win.com
>
> After running XXCLONE the target (40Gb) disk looks fine - W2K
> recognises the disk as 40Gb and appears to have all the
> directories and files copied OK.

I suggest that you try

xxclone C: D: /BACKUP0 /BC7

This ensures that the MBR and the boot sector will be
initialized (you may have to edit the \BOOT.INI file
manually).

I'm a little confused that you even use FDISK. I hope
you are not mixing up between WinME and Win2K. I believe
most win2K users do not use FDISK because the DiskMgmt.MSC
utility has almost everything in it (FDISK and FORMAT
functionality).

If you used FDISK, you should at least use /BC3 feature
so that the bootsector is correctly initialized by XCLONE
at least once. The use of FDISK leaves a Win9X/ME compatible
bootsector (I don't think FDISK is even distributed with
Win2K/XP).

In the upcoming version of XXCLONE, we will try to support
Win9X where the contents of the bootsector will be carefully
examined and if it is for Win9X boot, it will perform
necessary initialization step.

Have you tried to create a boot diskette inside XXCLONE
and tried to boot into the target volume from the diskette?

If my theory is correct (that your bootsector is for Win9X
boot which looks for IO.SYS as the first file to load),
re-initializing the bootsector with the one for NT/2K/XP
which loads NTLDR first will correct the problem.

Kan Yabumoto



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