Archived from groups: microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers (
More info?)
Walter,
Very simply, I'm just trying to undo the problems caused by deleting that
key.
Perhaps under most circumstances it can be deleted and it will rebuild, but
this is not what has happened here.
So I would like to get back to being able to boot from the first partition
(where the OS is) on the Seagate. The second partition is marked active at
the moment.
As for the wider picture, I had sorted out a method of cloning that worked
as long as I rigidly followed the steps I mentioned earlier. Otherwise I
never managed to boot the clone. I assumed that deleting that key would
answer that particular issue
Thanks,
Dave
"Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
news:uVL6CuPSFHA.3788@tk2msftngp13.phx.gbl...
> The partition structure is a bit weird. You have a logical with what
> appears to be a single volume followed by a couple of standard bootable
> primaries. In fact, the second partition is currently flagged as active.
>> MBR Partition Information (HD0):
>> +====+====+=============+====+=============+===========+===========+
>> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
>> MBR Partition Information (HD0) Continued:
>> +====+====+=============+====+=============+===========+===========+
>> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>
> The boot strap code would have to be in the second partition. That
> includes boot.ini, ntldr, ntdetect.com. The arc statement for that
> partition will be tricky, that depends on from where you're loading the
> OS. If you're loading the OS from the same partition, using the current
> partition and volume tables, the arc statement should read
>
>> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
>
> although the partition number might need be three depending on how things
> are counted (and I get really fuzzy on how the boot strap code counts
> logical partitions and volumes; I avoid placing logicals in front of
> non-logical volumes like the plague).
>
> Exactly what are you attempting to accomplish? One thing that sticks out
> is to move the logical higher in the partition table and drop the bootable
> primary in front of that.
>
> --
> Walter Clayton
> Any technology distinguishable from magic is insufficiently advanced.
>
>
> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
> news:426bb863$0$337$cc9e4d1f@news.dial.pipex.com...
>> The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
>> missing. I don't know if that's because I'm now bootiing from the other
>> drive.
>>
>> boot.ini from the Maxtor drive I'm now using - SATA 2
>>
>> [boot loader]
>> timeout=30
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
>> Edition" /fastdetect /NoExecute=OptOut
>>
>>
>> PARTINFO 1.09
>> Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.
>>
>> Run date: 04/24/2005 16:06
>>
>> ====================================================================
>> MBR Partition Information (HD0):
>> +====+====+=============+====+=============+===========+===========+
>> | 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
>> +====+====+=============+====+=============+===========+===========+
>> Volume Information
>> +----+----+-------------+----+-------------+-----------+-----------+
>> | 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
>> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> MBR Partition Information (HD0) Continued:
>> +====+====+=============+====+=============+===========+===========+
>> | 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
>> | 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> +====+====+=============+====+=============+===========+===========+
>> BOOT SECTOR INFORMATION
>> -------------------------------------------------------------------------------
>> File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
>> Jump: EB 52 90
>> OEM Name: NTFS
>> Bytes Per Sec: 512
>> Sec Per Clust: 8
>> Res Sectors: 0
>> Zero 1: 0x0
>> Zero 2: 0x0
>> NA 1: 0x0
>> Media: 0xF8
>> Zero 3: 0x0
>> Sec Per Track: 63
>> Heads: 255
>> Hidden Secs: 63
>> NA 2: 0x0
>> NA 3: 0x800080
>> Total Sectors: 0x04E1AF2A
>> MFT LCN: 0x0C0000
>> MFT Mirr LCN: 0x04E1AF2
>> Clust Per FRS: 0xF6
>> Clust Per IBlock: 0x1
>> Volume SN: 0x22F802A6F8027875
>> Checksum: 0x0
>> Boot Flag: 0xAA55
>> -------------------------------------------------------------------------------
>> File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
>> Jump: EB 52 90
>> OEM Name: NTFS
>> Bytes Per Sec: 512
>> Sec Per Clust: 8
>> Res Sectors: 0
>> Zero 1: 0x0
>> Zero 2: 0x0
>> NA 1: 0x0
>> Media: 0xF8
>> Zero 3: 0x0
>> Sec Per Track: 63
>> Heads: 255
>> Hidden Secs: 81915435
>> NA 2: 0x0
>> NA 3: 0x800080
>> Total Sectors: 0x0F065F8A
>> MFT LCN: 0x0C0000
>> MFT Mirr LCN: 0x0F065F8
>> Clust Per FRS: 0xF6
>> Clust Per IBlock: 0x1
>> Volume SN: 0xD400C167C150E2
>> Checksum: 0x0
>> Boot Flag: 0xAA55
>> -------------------------------------------------------------------------------
>> File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
>> Jump: EB 52 90
>> OEM Name: NTFS
>> Bytes Per Sec: 512
>> Sec Per Clust: 8
>> Res Sectors: 0
>> Zero 1: 0x0
>> Zero 2: 0x0
>> NA 1: 0x0
>> Media: 0xF8
>> Zero 3: 0x0
>> Sec Per Track: 63
>> Heads: 255
>> Hidden Secs: 333991350
>> NA 2: 0x0
>> NA 3: 0x800080
>> Total Sectors: 0x0F065F8A
>> MFT LCN: 0x0C0000
>> MFT Mirr LCN: 0x0F065F8
>> Clust Per FRS: 0xF6
>> Clust Per IBlock: 0x1
>> Volume SN: 0xA478DD6678DD382E
>> Checksum: 0x0
>> Boot Flag: 0xAA55
>> -------------------------------------------------------------------------------
>> ====================================================================
>> MBR Partition Information (HD1):
>> +====+====+=============+====+=============+===========+===========+
>> | 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
>> | 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> | 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> | 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
>> +====+====+=============+====+=============+===========+===========+
>> BOOT SECTOR INFORMATION
>> -------------------------------------------------------------------------------
>> File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
>> Jump: EB 52 90
>> OEM Name: NTFS
>> Bytes Per Sec: 512
>> Sec Per Clust: 8
>> Res Sectors: 0
>> Zero 1: 0x0
>> Zero 2: 0x0
>> NA 1: 0x0
>> Media: 0xF8
>> Zero 3: 0x0
>> Sec Per Track: 63
>> Heads: 255
>> Hidden Secs: 63
>> NA 2: 0x0
>> NA 3: 0x800080
>> Total Sectors: 0x024C1258
>> MFT LCN: 0x0B42FF
>> MFT Mirr LCN: 0x03D54EA
>> Clust Per FRS: 0xF6
>> Clust Per IBlock: 0x1
>> Volume SN: 0x4228D79E28D78EF3
>> Checksum: 0x0
>> Boot Flag: 0xAA55
>> -------------------------------------------------------------------------------
>>
>>
>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
>> news:426bb50b$0$335$cc9e4d1f@news.dial.pipex.com...
>>> Thanks Walter,
>>>
>>> I'll do it now, but in the meantime, I'm only up and running on my
>>> second hard drive, the Maxtor. The Seagate which has the problem is
>>> inaccessable. I don't know if that affects things. Let me know if it
>>> does.
>>>
>>> Dave
>>>
>>>
>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
>>> news:O3ISJHNSFHA.1236@TK2MSFTNGP14.phx.gbl...
>>>>I assume you're up and running on the problematic platform? If so, go to
>>>>http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
>>>>and run partinfW (yes, that W not O) from a command prompt as follows:
>>>>
>>>> partinfw >partinfo.txt
>>>> start notepad partinfo.txt
>>>>
>>>> Then copy and paste the contents back here. Also, do
>>>> start->run->c:\boot.ini and copy and paste the contents of boot.ini
>>>> back here as well.
>>>>
>>>>
>>>> I think I know what your issue is now and it's going to revolve around
>>>> boot.ini and the mbr code and now that I've taken a really fast look at
>>>> Acronis, it may be the tool isn't the right tool for what you're
>>>> attempting. Or you may be using it wrong.
>>>>
>>>> --
>>>> Walter Clayton
>>>> Any technology distinguishable from magic is insufficiently advanced.
>>>>
>>>>
>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
>>>> news:426b9144$0$354$cc9e4d1f@news.dial.pipex.com...
>>>>> Walter, HELP! ! !
>>>>>
>>>>> I deleted that key as suggested, HKLM\system\mounteddevices (except
>>>>> default
>>>>> value).
>>>>> Before restoring the clone onto the other drive I decided to just
>>>>> check the
>>>>> values in the key after rebooting and supposedly rebuilding.
>>>>>
>>>>> After entering my password at the log in screen, it immediately
>>>>> reverts to
>>>>> logging off . . .
>>>>> I have tried everything I can think of, safe mode, boot disk but can't
>>>>> log
>>>>> on any more.
>>>>>
>>>>> I then tried restoring the saved cloned partition to the other drive
>>>>> and got
>>>>> NTLDR is missing. So now I don't have any bootable drives.Back to
>>>>> Acronis
>>>>> boot CD to restore an earlier clone that worked and restored. The
>>>>> first
>>>>> partition, E: on the Maxtor was greyed out so I couldn't access it. I
>>>>> eventually used MaxBlast to repartition and then Acronis restore
>>>>> worked, and
>>>>> I'm now back to using an earlier saved clone that I've restored on the
>>>>> Maxtor. I haven't touched the Seagate C: so if there's a way of
>>>>> accessing
>>>>> and putting back this registry key (which I stupidly didn't feel the
>>>>> need to
>>>>> save) maybe I can get back to normal.
>>>>>
>>>>> I swear once this is over, I won't touch any of this software for a
>>>>> long,
>>>>> long time. There are just too many issues and problems here. Restoring
>>>>> all
>>>>> my programs in an emergency pales to insignificance compared with the
>>>>> time
>>>>> and hassle spent so far.
>>>>>
>>>>> Thanks in anticipation,
>>>>>
>>>>> Dave
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Walter Clayton" <w-claytonNO@SPmvpsAM.org>
>>>>> Newsgroups:
>>>>> microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
>>>>> Sent: Sunday, April 24, 2005 1:28 AM
>>>>> Subject: Re: error loading os
>>>>>
>>>>>
>>>>>> Yes it will get rebuilt and yes, if that's not deleted then cloning
>>>>>> just the partition image itself can cause some less than desirable
>>>>>> results. In fact if you check
>>>>>> HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
>>>>>> MS back up / restore tools don't restore that key.
>>>>>>
>>>>>> --
>>>>>> Walter Clayton
>>>>>> Any technology distinguishable from magic is insufficiently advanced.
>>>>>>
>>>>>>
>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
>>>>>> news:426ad507$0$261$cc9e4d1f@news.dial.pipex.com...
>>>>>>> Presumably XP will just rebuild this from scratch again? Do you
>>>>>>> think that is what stopped the clone booting when it almost got to
>>>>>>> the login screen and then reverted to a plain blue screen with
>>>>>>> cursor?
>>>>>>>
>>>>>>> Dave
>>>>>>> "Walter Clayton" <w-claytonNO@SPmvpsAM.org> wrote in message
>>>>>>> news:uYWfr46RFHA.3712@TK2MSFTNGP10.phx.gbl...
>>>>>>>> Prior to the clone, delete all but the default value from
>>>>>>>> HKLM\system\mounteddevices.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Walter Clayton
>>>>>>>> Any technology distinguishable from magic is insufficiently
>>>>>>>> advanced.
>>>>>>>>
>>>>>>>>
>>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
>>>>>>>> news:4268bb5e$0$300$cc9e4d1f@news.dial.pipex.com...
>>>>>>>>> OK, we're making some progress here. I can now make and restore a
>>>>>>>>> clone copy in Acronis 8.0.
>>>>>>>>>
>>>>>>>>> I need to follow these steps EXACTLY.
>>>>>>>>>
>>>>>>>>> 1. Don't format or give a drive letter to the recipient drive
>>>>>>>>> (Maxtor first partition here)
>>>>>>>>> 2. Use Acronis from boot CD not XP
>>>>>>>>> 3. Swap SATA cables before rebooting so Maxtor drive is now on
>>>>>>>>> same cable as original Seagate
>>>>>>>>>
>>>>>>>>> And this is the killer - if I don't do one of these and the
>>>>>>>>> cloning process fails, than it will ALWAYS fail UNTIL I do a disk
>>>>>>>>> copy with Acronis. This overwrites my entire drive and it's not
>>>>>>>>> entirely convenient to ship out 100GB of data to somewhere else.
>>>>>>>>> (Andrew mentions earlier in the thread a method using recovery
>>>>>>>>> console which I'll try if I need to in future.) And bizarrely this
>>>>>>>>> not only clones the drive correctly, but it puts it back to normal
>>>>>>>>> such that I can now successfully clone a partition.
>>>>>>>>>
>>>>>>>>> So, what on earth is going on here? Why did the boot sector get
>>>>>>>>> screwed up ( I assume that's what it was) and why did none of the
>>>>>>>>> standard fixes for this type of problem not work - fixboot
>>>>>>>>> /fixmbr?
>>>>>>>>>
>>>>>>>>> I gather at least some of this is caused by me using SATA drives.
>>>>>>>>> Perhaps there will be no such problems with Ghost 10.0 and Acronis
>>>>>>>>> 9.0?
>>>>>>>>>
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "David Cockram" <david.cockram@dsl.pipex.com> wrote in message
>>>>>>>>> news:42680ba0$0$362$cc9e4d1f@news.dial.pipex.com...
>>>>>>>>>> Hi,
>>>>>>>>>> I have 2 SATA drives, and I've been struggling to do a simple
>>>>>>>>>> clone of my Seagate C: partiton to a Maxtor F: partition.
>>>>>>>>>> I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
>>>>>>>>>> software. In most cases I got as far as a login screen and it
>>>>>>>>>> reverted to a plain blue screen with cursor. I always remove
>>>>>>>>>> Seagate before trying to boot with the cloned Maxtor. The only
>>>>>>>>>> thing that did consistently work was Acronis Migrate Easy, but
>>>>>>>>>> the problem is that you need to copy the entire disk. That means
>>>>>>>>>> overwriting the other Maxtor partitions. But it proves that it
>>>>>>>>>> did work. Now why did it, and not the others?
>>>>>>>>>>
>>>>>>>>>> Now whilst playing around with all this I noticed that I was
>>>>>>>>>> getting 'error loading os' when trying to boot. When I went back
>>>>>>>>>> to Acronis, that was also giving this message, and not even
>>>>>>>>>> attempting to boot as it had previosly done. I tried using
>>>>>>>>>> sysprep with the same result.
>>>>>>>>>>
>>>>>>>>>> Then I tried removing partitions completely from the Maxtor,
>>>>>>>>>> using fdisk and dos to format, using Max Blast to format, using
>>>>>>>>>> the
>>>>>>>>>> XP repair tool, fixmbr, fixboot. You name it I tried it I think.
>>>>>>>>>>
>>>>>>>>>> So I then thought I'd see if I could install XP on this drive.
>>>>>>>>>> No, I get the same message when it gets to the booting from disk
>>>>>>>>>> stage.
>>>>>>>>>>
>>>>>>>>>> Firstly, any ideas what could have caused this, and secondly do I
>>>>>>>>>> need to do a low level format to get this drive back to normal
>>>>>>>>>> shipping condition. If so, could someone tell me how, and what
>>>>>>>>>> software to use, as I've done this before.
>>>>>>>>>>
>>>>>>>>>> I've now done a fair bit of reading about cloning. For a lot of
>>>>>>>>>> people it seems to be a completely painless process using Ghost
>>>>>>>>>> or Acronis. For many others including me, it just doesn't seem to
>>>>>>>>>> work, and I've seen the same issues reported over and over with
>>>>>>>>>> no workable solutions.
>>>>>>>>>>
>>>>>>>>>> Ah well, I'll get there in the end. Maybe sooner with your help.
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Dave Cockram
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>