4 May
2014
4 May
'14
08:33
В Sat, 03 May 2014 07:40:21 -0400 James Knottпишет: > Felix Miata wrote: > > As is normal for him, James has provided limited information about > > what he did, e.g. his meaning of his words "move" and "installing". > > It's entirely unclear whether he cloned with a true cloner, or used a > > partitioner to create partitions which he created filesystems on then > > copied to, or some mix of functions, or whether anything was done to > > ensure the new HD had anything in it other than what's in its last 66 > > bytes. I've seen no clear indication of whether his failure to boot > > Windows on the new HD happens while the old remains attached or not, > > and whether external case is USB2, USB3 or eSATA. What disk identifier > > did he change, and where did he make the change? > After installing the new drive: > 1. Restored to "factory" with the restore DVDs > 2. Removed Windows partition and used dd to bring over original > 3. Booted Windows and used the Windows partition tool to resize to > desired size and then ran chkdsk > 4. Created extended partion > 5. Created new swap > 6. Used GParted to copy & resize Please upload somewhere partition boot block (the very first block of partition that is expected to be Windows boot partition). Windows encodes absolute position of "stage1.5" bootloader (that is the one which is located in unused sectors before file system starts. At least, that is how I read PBT code. When you "resized and moved" you could well break it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org