#$%#@## True Image
in [Computers]
|
From: Whatcher? on 26 Oct 2006 18:02 "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?
From: The Old Bloke on 26 Oct 2006 18:14 "Rod Speed" <rod.speed.aaa(a)gmail.com> wrote in message news:4qchk7Fmj7toU1(a)individual.net... > The Old Bloke <le0pard32(a)gmail.com> wrote: > >> Yes, I agree that I must be something wrong with my use when it works >> for others. But there are very few options to set when you choose to >> clone. > >> Maybe it is something to do with my hardware AMD 4800 dual, 2G RAM. I >> used to have different problems (unrelated to TI) before I realised that >> the AMD4800 had its own driver. I had never heard of a CPU driver >> before. > > Shouldnt be relevant, the problem appears to be that the rather complex > NT/2K/XP boot process isnt being setup properly on the clone. > > That process is even more complicated with a clone, because > XP can get very confused indeed if it can see the original on > the first boot of the clone after the clone has been made. > > Are you unplugging the original before you first boot the clone ? > Thats absolutely essential, XP gets very confused if you dont. > >> Colin, do you partition and format before cloning? > > No, there is no need to do that and in fact its completely > pointless because all that is overwritten by the clone process. > >> Can't remember the wording, but there is an option to remove the >> partition? > > No there isnt. ============ *Fired up TI again, and I am at a dialogue box where I have two selections *"Delete partitions on the destiation HD" and "No, I do not want to delete partitions" *The box is titled "You have chosen a destination HD that already contains some partitions" In my case one 400G partition. =============== > >> (I can't check this at the moment as I have only my trusty C: cabled in.) > >> By Googling I can see that other people have had similar problems. Varied >> solutions such as running Win98 fdisk /mbr, etc. I think I've >> tried them all. Getting confused, no, shitty, with the whole thing! > >> Any feedback on state you new HD is in before you clone? Partitioned, >> etc. > > I never bother to do anything special. > >> I have seen systems get totally stuffed when boot sees two bootable >> HDs but I have been careful not to let this happen. > >> On the cloned disk I can see a correct boot.ini and the ntldr files. What >> does make a NTFS HD bootable? > > Its a surprisingly complex process, involving the MBR, ntldr and boot.ini > > Its that complex because its designed to allow ntldr and the very > early boot phase to happen off a drive that isnt the one being booted, > even tho most just have one physical drive involved in the boot. > > I think its most likely that you have the bios virus protection enabled > and that that is preventing TI from updating the MBR etc on the clone. > The bios stops it from being updated. Just turning virus protection > off on the bios should fix that. > > If it isnt that, ask acronis directly about the problem, you just paid for > V10. > > >> "Colin" <a(a)b.c.d> wrote in message >> news:HT%%g.53417$rP1.28646(a)news-server.bigpond.net.au... >>> No idea what you are doing but ---- >>> >>> On Sunday I bought a WD 250Gb SATA drive and cloned my WD 200 Gb >>> PATA onto it ( 2 partitions ) with TI 9 Build 2323 >>> >>> Went like clockwork and quick too. >>> >>> Shut itself down before telling me to pull the old drive out. >>> >>> Totally painless. >>> >>> I regularly image the C: partition and have never had a problem >>> restoring it. >>> >>> I don't think it's TI - buggered if I know what though. >>> >>> Colin >>> >>> "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? > >
From: Colin on 26 Oct 2006 18:23 "The Old Bloke" <le0pard32(a)gmail.com> wrote in message news:hra0h.53583$rP1.12397(a)news-server.bigpond.net.au... > > *Fired up TI again, and I am at a dialogue box where I have two selections > > *"Delete partitions on the destiation HD" and "No, I do not want to > delete partitions" > > *The box is titled "You have chosen a destination HD that already contains > some partitions" In my case one 400G partition. > > =============== Yep, that's the bit you get if you pre format the drive I told it to "Delete" and it then goes on to let you set sizes It seemed like it wanted to blow the partitions away as it's first preference. Very straight forward after that LOL this time Colin
From: The Old Bloke on 26 Oct 2006 18:26 "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
From: Rod Speed on 26 Oct 2006 20:28
The Old Bloke <le0pard32(a)gmail.com> wrote > Rod Speed <rod.speed.aaa(a)gmail.com> wrote >> The Old Bloke <le0pard32(a)gmail.com> wrote >>> Yes, I agree that I must be something wrong with my use when it >>> works for others. But there are very few options to set when you >>> choose to clone. >>> Maybe it is something to do with my hardware AMD 4800 dual, 2G RAM. >>> I used to have different problems (unrelated to TI) before I >>> realised that the AMD4800 had its own driver. I had never heard of >>> a CPU driver before. >> Shouldnt be relevant, the problem appears to be that the rather >> complex NT/2K/XP boot process isnt being setup properly on the clone. >> That process is even more complicated with a clone, because >> XP can get very confused indeed if it can see the original on >> the first boot of the clone after the clone has been made. >> Are you unplugging the original before you first boot the clone ? >> Thats absolutely essential, XP gets very confused if you dont. >>> Colin, do you partition and format before cloning? >> No, there is no need to do that and in fact its completely >> pointless because all that is overwritten by the clone process. >>> Can't remember the wording, but there is an option to remove the >>> partition? >> No there isnt. > ============ > *Fired up TI again, and I am at a dialogue box where I have two selections > *"Delete partitions on the destiation HD" and "No, I do not want to delete partitions" That is just a less than ideally worded confirmation that you are happy to overwrite whatever is on the destination physical drive. > *The box is titled "You have chosen a destination HD that already > contains some partitions" In my case one 400G partition. > =============== >>> (I can't check this at the moment as I have only my trusty C: >>> cabled in.) >> >>> By Googling I can see that other people have had similar problems. >>> Varied solutions such as running Win98 fdisk /mbr, etc. I think >>> I've tried them all. Getting confused, no, shitty, with the whole thing! >> >>> Any feedback on state you new HD is in before you clone? >>> Partitioned, etc. >> >> I never bother to do anything special. >> >>> I have seen systems get totally stuffed when boot sees two bootable >>> HDs but I have been careful not to let this happen. >> >>> On the cloned disk I can see a correct boot.ini and the ntldr >>> files. What does make a NTFS HD bootable? >> >> Its a surprisingly complex process, involving the MBR, ntldr and >> boot.ini Its that complex because its designed to allow ntldr and the very >> early boot phase to happen off a drive that isnt the one being >> booted, even tho most just have one physical drive involved in the >> boot. I think its most likely that you have the bios virus protection >> enabled and that that is preventing TI from updating the MBR etc on >> the clone. The bios stops it from being updated. Just turning virus >> protection off on the bios should fix that. >> >> If it isnt that, ask acronis directly about the problem, you just >> paid for V10. >> >> >>> "Colin" <a(a)b.c.d> wrote in message >>> news:HT%%g.53417$rP1.28646(a)news-server.bigpond.net.au... >>>> No idea what you are doing but ---- >>>> >>>> On Sunday I bought a WD 250Gb SATA drive and cloned my WD 200 Gb >>>> PATA onto it ( 2 partitions ) with TI 9 Build 2323 >>>> >>>> Went like clockwork and quick too. >>>> >>>> Shut itself down before telling me to pull the old drive out. >>>> >>>> Totally painless. >>>> >>>> I regularly image the C: partition and have never had a problem >>>> restoring it. >>>> >>>> I don't think it's TI - buggered if I know what though. >>>> >>>> Colin >>>> >>>> "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? |