#$%#@## True Image
in [Computers]
|
From: Rod Speed on 26 Oct 2006 20:34 lynx <none(a)nothere.com> wrote: > lynx wrote: > >> The Old Bloke wrote: >> >>> "Whatcher?" <t.4.2(a)2.4.t> wrote in message >>> news:45413080$0$4672$61c65585(a)un-2park-reader-01.sydney.pipenetworks.com.au... >>> >>> >>>> "The Old Bloke" <le0pard32(a)gmail.com> wrote in message >>>> news:FD%%g.53403$rP1.16199(a)news-server.bigpond.net.au... >>>> >>>>> I have always had a problem with TI in the clone mode. The clone >>>>> always seems to run OK but the cloned HD will not boot. >>>>> >>>>> So yesterday I tried it again. All the C: files transferred. The >>>>> boot.ini looks OK but when I try to boot from the cloned HD I get >>>>> the message "Error loading operating system" >>>>> >>>>> The new drive is a Samsung SATA 400G HD, and the current C: is >>>>> SATA 300G. I looked thru the Acronis site and found the >>>>> suggestion that the problem could be cured by creating a rescue >>>>> CD and booting and running the software from that CD. The cloned >>>>> drive still wouldn't boot. My BIOS has the latest update. >>>>> >>>>> Maybe it was a problem with V9, so I forked out more money and got >>>>> V10. Still not bootable. >>>>> >>>>> So maybe the 400G was too large for something. I had a spare 200G >>>>> SATA drive, so I cloned to that. Same error message when I tried >>>>> to boot. >>>>> >>>>> I have had this problem before with TI9. That time I found >>>>> something with Google that made the HD bootable, but I can't >>>>> relocate that. :-( >>>>> >>>>> I booted from the XP CD and ran Fixmbr. That program tells me >>>>> something to the effect that the MBR is invalid (can't remember >>>>> the exact wording), and gives me the option to fix it. I say >>>>> yes, but the HD still won't boot. Run Fixmbr again and it tells >>>>> me that the MBR is invalid! >>>>> >>>>> I have posted on the TI forum, but so far I have only had >>>>> suggestions that I have already tried. >>>>> >>>>> Any help? >>>>> >>>>> >>>> You forgot fixboot as well. >>>> >>>> Did you make the partition active? >>>> >>> >>> I neglected to say so, but I did run fixboot as well. The partition >>> is active, according to Disk Management, and it does contain the >>> 150G of files, just won't boot. I'm close to backing up your way. But it should bloody work! >>> Seems to for most people, but Google >>> shows that some others have this problem. Almost time to start an >>> artificial reef with my PC >>> >>> >> >> Have you tried doing the clone with the new drive unpartitioned? >> >> > > also.. I don't use this prog, so don't know it. I use Ghost. But can > you run it in DOS mode? REason I ask is becuase in my case Ghost > works fine when booted from a floppy, but if run it from within Win > XP, it hangs when the system reboots, and then not only is the clone > not created, but the original drive wont boot! I then have to run a > prog called GhReboot.exe to fix it. Thats an entirely different issue that is specific to Ghost. Ghost plays silly buggers with the bootable partition, basically so it can be initiated in Win and can reboot into DOS and do its work at the DOS level. When its work is finished, it cleans up that special bootable partition it creates so it can boot into DOS to do the work. When what Ghost attempts to do at the DOS level fails, it never gets a chance to clean up that special bootable DOS partition and restore the original bootable partition. GhReboot.exe just does that cleanup manually.
From: Rod Speed on 26 Oct 2006 23:11 Cerberus <styx.sentinel.PAY(a)FERRYMAN.gmail.com> wrote > Rod Speed <rod.speed.aaa(a)gmail.com> wrote >> The Old Bloke <le0pard32(a)gmail.com> wrote >>> I have always had a problem with TI in the clone mode. The >>> clone always seems to run OK but the cloned HD will not boot. >>> So yesterday I tried it again. All the C: files transferred. >>> The boot.ini looks OK but when I try to boot from the cloned >>> HD I get the message "Error loading operating system" >> The boot.ini is only a very minor component of the rather complex >> NT/2K/XP boot process, essentially just some config data that >> ntldr uses to decide what to offer the user menu wise etc. > boot.ini is far from a minor component Rod, Wrong. > and it does far more than provide basic data for a boot menu. Wrong. > boot.ini contains the ARC pathnames that > identify the location of the boot partition(s). In theory, yes. In practice when there is only one copy of the OS to boot from, the detail in the boot.ini is essentially irrelevant with a clone which did work fine in the original. > These pathnames identify the type of controller, the controller number, > the disk number and the partition number for any given installation in > the boot menu. They are crucial in identifying the target partition to boot. Not with a clone where the original boots fine. > The OP's problem is quite possibly related to the ARC pathnames > in his boot.ini not marrying up to the logical location of the partition > he is trying to boot. This is not at all uncommon in cloning operations > especially when cloning SCSI to IDE. Pity he isnt doing that. > The OP should ensure that his cloned disk is mounted in the > same position on the same adapter as the original disk. That isnt necessary. In fact XP will still boot fine if you move the drive on the controller. So it isnt as black and white as you claim. And he has said that fixboot makes no difference, so that cant be the problem, because that does fix up the boot.ini if that is necessary.
From: Rod Speed on 26 Oct 2006 23:16 lynx <none(a)nothere.com> wrote: > Rod Speed wrote: > >> lynx <none(a)nothere.com> wrote: >> >>> lynx wrote: >>> >>>> The Old Bloke wrote: >>>> >>>>> "Whatcher?" <t.4.2(a)2.4.t> wrote in message >>>>> news:45413080$0$4672$61c65585(a)un-2park-reader-01.sydney.pipenetworks.com.au... >>>>> >>>>>> "The Old Bloke" <le0pard32(a)gmail.com> wrote in message >>>>>> news:FD%%g.53403$rP1.16199(a)news-server.bigpond.net.au... >>>>>> >>>>>>> I have always had a problem with TI in the clone mode. The >>>>>>> clone always seems to run OK but the cloned HD will not boot. >>>>>>> >>>>>>> So yesterday I tried it again. All the C: files transferred. The boot.ini looks OK but when >>>>>>> I try to boot from the cloned HD >>>>>>> I get the message "Error loading operating system" >>>>>>> >>>>>>> The new drive is a Samsung SATA 400G HD, and the current C: is >>>>>>> SATA 300G. I looked thru the Acronis site and found the >>>>>>> suggestion that the problem could be cured by creating a rescue >>>>>>> CD and booting and running the software from that CD. The >>>>>>> cloned drive still wouldn't boot. My BIOS has the latest >>>>>>> update. Maybe it was a problem with V9, so I forked out more money and >>>>>>> got V10. Still not bootable. >>>>>>> >>>>>>> So maybe the 400G was too large for something. I had a spare >>>>>>> 200G SATA drive, so I cloned to that. Same error message when >>>>>>> I tried to boot. >>>>>>> >>>>>>> I have had this problem before with TI9. That time I found >>>>>>> something with Google that made the HD bootable, but I can't >>>>>>> relocate that. :-( >>>>>>> >>>>>>> I booted from the XP CD and ran Fixmbr. That program tells me >>>>>>> something to the effect that the MBR is invalid (can't remember >>>>>>> the exact wording), and gives me the option to fix it. I say >>>>>>> yes, but the HD still won't boot. Run Fixmbr again and it tells >>>>>>> me that the MBR is invalid! >>>>>>> >>>>>>> I have posted on the TI forum, but so far I have only had >>>>>>> suggestions that I have already tried. >>>>>>> >>>>>>> Any help? >>>>>>> >>>>>> You forgot fixboot as well. >>>>>> >>>>>> Did you make the partition active? >>>>>> >>>>>> >>>>> I neglected to say so, but I did run fixboot as well. The >>>>> partition is active, according to Disk Management, and it does contain the >>>>> 150G of files, just won't boot. I'm close to backing up your >>>>> way. But it should bloody work! Seems to for most people, but >>>>> Google shows that some others have this problem. Almost time to start an >>>>> artificial reef with my PC >>>>> >>>>> >>>>> >>>> Have you tried doing the clone with the new drive unpartitioned? >>>> >>>> >>>> >>> also.. I don't use this prog, so don't know it. I use Ghost. But can >>> you run it in DOS mode? Reason I ask is becuase in my case Ghost >>> works fine when booted from a floppy, but if run it from within Win >>> XP, it hangs when the system reboots, and then not only is the clone >>> not created, but the original drive wont boot! I then have to run a >>> prog called GhReboot.exe to fix it. >>> >> >> Thats an entirely different issue that is specific to Ghost. >> >> Ghost plays silly buggers with the bootable partition, basically so >> it can be initiated in Win and can reboot into DOS and do its work >> at the DOS level. When its work is finished, it cleans up that special bootable >> partition it creates so it can boot into DOS to do the work. >> >> When what Ghost attempts to do at the DOS level fails, >> it never gets a chance to clean up that special bootable >> DOS partition and restore the original bootable partition. >> >> GhReboot.exe just does that cleanup manually. > So any idea why it won't run when initiated from windoze but works fine from a DOS floppy boot? How can you run it from Win when the problem is that it cant boot to win ? If you are actually booting a different drive so you can run win, likely because win wont let it molest the partition table. Thats what it does. You can see the special partition that it uses for the boot to dos after the ghost op fails, and you can manually fix it yourself too instead of running GhReboot.exe if you know what you are doing. Or if you are running it from win on the system that does boot fine, its not supposed to do anything there, because you can obviously boot win fine, the special dos boot partition clearly isnt in the partition table.
From: Rod Speed on 26 Oct 2006 23:17 Cerberus <styx.sentinel.PAY(a)FERRYMAN.gmail.com> wrote: > lynx <none(a)nothere.com> wrote: > >> Rod Speed wrote: > >>> Thats an entirely different issue that is specific to Ghost. >>> >>> Ghost plays silly buggers with the bootable partition, basically so >>> it can be initiated in Win and can reboot into DOS and do its work >>> at the DOS level. >>> >>> When its work is finished, it cleans up that special bootable >>> partition it creates so it can boot into DOS to do the work. >>> >>> When what Ghost attempts to do at the DOS level fails, it never >>> gets a chance to clean up that special bootable DOS partition and >>> restore the original bootable partition. >>> >>> GhReboot.exe just does that cleanup manually. >> >> So any idea why it won't run when initiated from windoze but works >> fine from a DOS floppy boot? > > HAL is the root cause of most of these limitations and workarounds. Nope, it just uses a special boot partition for the boot to dos. > http://www.google.com.au/search?q=windows+HAL
From: The Old Bloke on 27 Oct 2006 01:38
"The Old Bloke" <le0pard32(a)gmail.com> wrote in message news:FD%%g.53403$rP1.16199(a)news-server.bigpond.net.au... >I have always had a problem with TI in the clone mode. The clone always >seems to run OK but the cloned HD will not boot. > > So yesterday I tried it again. All the C: files transferred. The > boot.ini looks OK but when I try to boot from the cloned HD I get the > message "Error loading operating system" > > The new drive is a Samsung SATA 400G HD, and the current C: is SATA 300G. > I looked thru the Acronis site and found the suggestion that the problem > could be cured by creating a rescue CD and booting and running the > software from that CD. The cloned drive still wouldn't boot. My BIOS has > the latest update. > > Maybe it was a problem with V9, so I forked out more money and got V10. > Still not bootable. > > So maybe the 400G was too large for something. I had a spare 200G SATA > drive, so I cloned to that. Same error message when I tried to boot. > > I have had this problem before with TI9. That time I found something with > Google that made the HD bootable, but I can't relocate that. :-( > > I booted from the XP CD and ran Fixmbr. That program tells me something > to the effect that the MBR is invalid (can't remember the exact wording), > and gives me the option to fix it. I say yes, but the HD still won't > boot. Run Fixmbr again and it tells me that the MBR is invalid! > > I have posted on the TI forum, but so far I have only had suggestions that > I have already tried. > > Any help? > > To all the good people that have helped me. I have now had success. Success! The only thing I did differently was to remove the partition from the new Samsung. ie made it unallocated space. It went beautifully. As soon as it shut down I removed the new Samsung and booted from the old C: (because it would be a major problem if I lost it, tho I do have good backups). Then I shutdown the PC, changed drives to the cloned Samsung and booted. Initially in the early parts of the boot, it said that TI was examining the partitions, and then proceeded to complete a successful boot. I am writing this message from the new Samsung-booted OS. For my PC it seems that I have to start with an unpartitioned HD. This may also be the case with Ghost 10, but I have not tried it. Thanks from a happy chappie |