If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
FIXMBR redux
I think this leads back to my discussions with, and
advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie |
Ads |
#2
|
|||
|
|||
FIXMBR redux
boot from your cd and go to recovery console from there, I
assume it recognises the new clone as the OS when you search for it via RC use fixmbr and fixboot I had a similar problem and this has resolved them for me good luck Geoff "William B. Lurie" wrote in message ... I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie |
#3
|
|||
|
|||
FIXMBR redux
Tried that, Geoff. Cannot get to Recovery Console. I put in the XP-CD,
rebooted. It gave me choice of going to XP or to RC. I chose RC, and instead of finding it on the hard drive (where it was on the drive I did the Image of), or on the CD, it stopped with message "file missing or corrupt system32/hal.dll ......Please install a copy of that file." Of course, it didn't tell me how to install it, even assuming I can find in on the CD, where, if I find it, I expect it to be a ".dl_" file and not .dll.. Bill L. Geoffw wrote: boot from your cd and go to recovery console from there, I assume it recognises the new clone as the OS when you search for it via RC use fixmbr and fixboot I had a similar problem and this has resolved them for me good luck Geoff "William B. Lurie" wrote in message ... I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie -- William B. Lurie |
#4
|
|||
|
|||
FIXMBR redux
William B. Lurie said in :
I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie Although PartitionMagic is great at managing partitions, it doesn't let you save the contents of the MBR. Neither does DriveImage since it creates image filesets for the partition and doesn't include the MBR. You mentioned a "keep the MBR" option. Is this something new in their latest version 7? I have DriveImage 2002 (and prior versions) and that was not an option. If PartitionMagic or DriveImage really don't include the MBR in whatever version you have, and if you were looking to copy the MBR from the source drive to the cloned drive, use mbrutil from Powerquest. Go to: ftp://ftp.symantec.com/public/englis.../pq/utilities/ and download head.zip. You can also use tools like MBRtool (http://www.diydatarecovery.nl/~tkuurstra/mbrtool.htm). If you know the bootstrap program is larger than 460 bytes and usurps the unused portion of track 0 then be sure to save the entire track 0 rather than just the MBR section (sector 0). Some multiboot managers will use the rest of track 0 for their code or for an extended partition table (if they support more than 4 partitions). You could save the MBR or track 0 onto a floppy and then use the mbrutil or MBRtool to restore it onto the cloned drive. With the message regarding hal.dll missing, did you perchance change the power saving settings in the BIOS from ACPI to APM or visa versa? Have you tried running the Repair function from the install CD? You can configure the timeout for the boot menu. System applet in Control Panel, Advanced, Startup and Recovery button, -- __________________________________________________ __________ *** Post replies to newsgroup. Share with others. *** Email domain = ".com" *AND* append "=NEWS=" to Subject. __________________________________________________ __________ |
#5
|
|||
|
|||
FIXMBR redux
Michael, it is my suspicion that the "restore MBR"
feature of PowerQuest's Drive Image 7 is not compatible with the bootup procedure which I have, namely, on *every* bootup it gives the choice of going to XP in normal manner, or going to Recovery Console. I don't think I have any alternative to de-energizing the RC option on boot-up. Of course I'd like to do that on the clone without disturbing the Master Drive, but I wouldn't know how to get there. If you agree, and can tell me, I'd like to do that first, namely, get back to a pure system. Failing that, I'd say, tell me how to disable RC altogether on my Master Drive, figuring we can put it back again if and when we need it. William B. Lurie wrote: I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie -- William B. Lurie |
#6
|
|||
|
|||
FIXMBR redux
*Vanguard* wrote:
William B. Lurie said in : I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie Although PartitionMagic is great at managing partitions, it doesn't let you save the contents of the MBR. Neither does DriveImage since it creates image filesets for the partition and doesn't include the MBR. You mentioned a "keep the MBR" option. Is this something new in their latest version 7? I have DriveImage 2002 (and prior versions) and that was not an option. If PartitionMagic or DriveImage really don't include the MBR in whatever version you have, and if you were looking to copy the MBR from the source drive to the cloned drive, use mbrutil from Powerquest. Go to: ftp://ftp.symantec.com/public/englis.../pq/utilities/ and download head.zip. You can also use tools like MBRtool (http://www.diydatarecovery.nl/~tkuurstra/mbrtool.htm). If you know the bootstrap program is larger than 460 bytes and usurps the unused portion of track 0 then be sure to save the entire track 0 rather than just the MBR section (sector 0). Some multiboot managers will use the rest of track 0 for their code or for an extended partition table (if they support more than 4 partitions). You could save the MBR or track 0 onto a floppy and then use the mbrutil or MBRtool to restore it onto the cloned drive. With the message regarding hal.dll missing, did you perchance change the power saving settings in the BIOS from ACPI to APM or visa versa? Have you tried running the Repair function from the install CD? You can configure the timeout for the boot menu. System applet in Control Panel, Advanced, Startup and Recovery button, Thanks for all the goodies, Vang......I'll answer one specifically: Drive Inage 7.0.x , in restoring the original hard drive (or partition if you will, I guess), asks if you want to restore the original MBR, . I changed no power settings or anything else, and, frankly, I feel I'll be getting in deeper than I want to, if I do all the MBR manipulations you suggest. I want a straightforward tool: I have my Master Hard Drive, with my Master XP OS complete in one partition. I use Drive Image 7 to make an Image (not 'copy', I learned) which I store on a different (slave) hard drive. Then I use Drive Image's PQRE to take that Image and recreate a clone of the original XP, complete, bootable, exact, fully interchangeable, on still another hard drive. If an when the Master Drive fails (as it must, one of these days), I can just sway in the clone. And I don't mind doing those two simple steps at the beginning of every month.....if it would work!!!! -- William B. Lurie |
#7
|
|||
|
|||
FIXMBR redux
On Tue, 01 Jun 2004 06:50:13 -0400, William B. Lurie wrote:
I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie Something about your saga keeps nagging at the back of my mind but I can't put my finger on it. When you create an exact image to second drive, the target purpose is to be able to yank a non-functioning drive and drop the imaged drive into place. (A restorable image is something different. It's usually compressed and can be restored to any drive that is large enough to hold the uncompressed image.) Have you tried booting with only the imaged drive placed as master on the main controller? At this point, those recovery console fix it thingies should be able to help with rebuilding the bootconfig and boot record. Or, if PM will restore it, give that a try. Or are you trying to maintain two bootable drives and trying to switch between two separate XP installations? If this is what you're doing and XP's boot manager is failing to handle this, you might want to try a third party boot manager. I no longer use Drive Image, stopped with Drive Image 6. The newer version may offer alternatives that I'm not aware of - meaning that the above may not apply. For a drive to boot, there are some requirements. There has to be an active partition, for one. On that partition the boot records and files have to be available to get past the initial boot strap and let it move on to the actual loading of the operating system. I don't know the answer to your problem, William. Just typing some thoughts "out loud" that may or may not help. It sounds like you're so close to getting this to work but a step is missing. Just can't put my finger on which step and since I don't use Drive Image can't give specific advice. -- Sharon F MS-MVP ~ Windows XP Shell/User |
#8
|
|||
|
|||
FIXMBR redux
Sharon F wrote:
On Tue, 01 Jun 2004 06:50:13 -0400, William B. Lurie wrote: I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie Something about your saga keeps nagging at the back of my mind but I can't put my finger on it. When you create an exact image to second drive, the target purpose is to be able to yank a non-functioning drive and drop the imaged drive into place. (A restorable image is something different. It's usually compressed and can be restored to any drive that is large enough to hold the uncompressed image.) Have you tried booting with only the imaged drive placed as master on the main controller? At this point, those recovery console fix it thingies should be able to help with rebuilding the bootconfig and boot record. Or, if PM will restore it, give that a try. Or are you trying to maintain two bootable drives and trying to switch between two separate XP installations? If this is what you're doing and XP's boot manager is failing to handle this, you might want to try a third party boot manager. I no longer use Drive Image, stopped with Drive Image 6. The newer version may offer alternatives that I'm not aware of - meaning that the above may not apply. For a drive to boot, there are some requirements. There has to be an active partition, for one. On that partition the boot records and files have to be available to get past the initial boot strap and let it move on to the actual loading of the operating system. I don't know the answer to your problem, William. Just typing some thoughts "out loud" that may or may not help. It sounds like you're so close to getting this to work but a step is missing. Just can't put my finger on which step and since I don't use Drive Image can't give specific advice. Thank you, Sharon. You speak the truth, of course, and I'll simplify your thinking by making it clear that when I've spoken about what I do with the 'cloned' hard drive, I mean that I physically shut the system down, and pull out the Master, and insert the Clone exactly in its place, electrically and physically. There should be no conflict there. BTW, D-I 7 is, I believe, the only version for XP. The D-I 2002/6 version is expressly not for XP. Yes, the drive onto which I Recover the Image is Active and Primary. It is brand new and not even partitioned. As an aside, and not pertinent here, I have another completely separate drive with WIN ME on it, and I am able, through a simple manipulation of the BIOS, to boot to HDD-0 (these XP alternates) or to HDD-1 (the ME), should I care to go that route. I think the next step will be for you, or Michael, to instruct me how to deactivate the RC altogether, after which I will first test my Master Drive (and pray that it will still work), and then repeat the D-I Image creation followed by trying to create the clone from it. W B L -- William B. Lurie |
#9
|
|||
|
|||
FIXMBR redux
I need to understand what you've stated as I have Drive Image 2002 as well.
If Drive Image 2002 doesn't include the contents of the MBR, would that not make image restoration useless as it would not produce a bootable drive? Since I've used Drive Image 2002 through several betas wherein I deleted my system partition and restored the image created with Drive Image and had a bootable system upon completion of the restore process, I'd like to know how that is possible. In fact, as a part of the DI 2002 restore routine, you must first delete the partition. -- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "*Vanguard*" wrote in message ... Although PartitionMagic is great at managing partitions, it doesn't let you save the contents of the MBR. Neither does DriveImage since it creates image filesets for the partition and doesn't include the MBR. You mentioned a "keep the MBR" option. Is this something new in their latest version 7? I have DriveImage 2002 (and prior versions) and that was not an option. If PartitionMagic or DriveImage really don't include the MBR in whatever version you have, and if you were looking to copy the MBR from the source drive to the cloned drive, use mbrutil from Powerquest. Go to: ftp://ftp.symantec.com/public/englis.../pq/utilities/ and download head.zip. You can also use tools like MBRtool (http://www.diydatarecovery.nl/~tkuurstra/mbrtool.htm). If you know the bootstrap program is larger than 460 bytes and usurps the unused portion of track 0 then be sure to save the entire track 0 rather than just the MBR section (sector 0). Some multiboot managers will use the rest of track 0 for their code or for an extended partition table (if they support more than 4 partitions). You could save the MBR or track 0 onto a floppy and then use the mbrutil or MBRtool to restore it onto the cloned drive. With the message regarding hal.dll missing, did you perchance change the power saving settings in the BIOS from ACPI to APM or visa versa? Have you tried running the Repair function from the install CD? You can configure the timeout for the boot menu. System applet in Control Panel, Advanced, Startup and Recovery button, -- __________________________________________________ __________ *** Post replies to newsgroup. Share with others. *** Email domain = ".com" *AND* append "=NEWS=" to Subject. __________________________________________________ __________ |
#10
|
|||
|
|||
FIXMBR redux
So just reinstall the recovery console. I have had to do that because =
after restoring an image (TrueImage7 www.acronis.com) the RC was not = accessible. As far as the MBR is concerned, I did a fresh install of XP, ran RC from = the CD, and fix MBR found that the MBR was corrupted or not standard, I = left it alone this time and it is working fine. --=20 Just my 2=A2 worth Jeff __________in response to__________ "William B. Lurie" wrote in message = ... | I think this leads back to my discussions with, and | advice from, Michael Solomon a while back....... |=20 | Since 'solving' the problems of creating a drive image | of my master hard drive with Drive Image 7, and creating | a clone of that drive with its PowerQuest Recovery | Environment software, I've been living is a fool's | paradise. I discovered this when I went to create the | monthly Drive Image yesterday, and create the clone on | a newly purchased hard drive. |=20 | I've been living with my Master drive booting to a | choice between normal start-up and Recovery Console, | a minor annoyance because after a ten-second countdown | it goes to normal boot, automatically. No problem there. |=20 | I believe that the main part of the problem is now that | the new exact clone does not have Master Boot Record | correct, because the 'Normal Boot' path leads to the | choices of Safe Mode or Normal etcetera, and no choice | gets to anything other than a repeat of that set of | choices. If I select Recovery Console, I get a short | DOS-type message saying that file 'xxxxx.dll' is missing, | and to reload it somehow from somewhere. I suspect that | more than one '.dll' file will be in the list of what it | needs. I tried selecting Recovery Console, hoping that I | could somehow do a FIXMBR there, but I can't get to RC. |=20 | Incidentally, in running Drive Image, I've repeated the | whole image-and-recreate process, with and without the | 'keep the MBR' option, with no apparent difference in | results. I've tried to solve the problem without going to | you experts, but what I've considered all logical paths | haven't solved it. |=20 | William B. Lurie | |
#11
|
|||
|
|||
FIXMBR redux
First, I'm assuming you did, in fact, install the Recovery Console to your
hard drive. Were both hard drives connected to the system when you created the image of the first drive? -- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "William B. Lurie" wrote in message ... Michael, it is my suspicion that the "restore MBR" feature of PowerQuest's Drive Image 7 is not compatible with the bootup procedure which I have, namely, on *every* bootup it gives the choice of going to XP in normal manner, or going to Recovery Console. I don't think I have any alternative to de-energizing the RC option on boot-up. Of course I'd like to do that on the clone without disturbing the Master Drive, but I wouldn't know how to get there. If you agree, and can tell me, I'd like to do that first, namely, get back to a pure system. Failing that, I'd say, tell me how to disable RC altogether on my Master Drive, figuring we can put it back again if and when we need it. William B. Lurie wrote: I think this leads back to my discussions with, and advice from, Michael Solomon a while back....... Since 'solving' the problems of creating a drive image of my master hard drive with Drive Image 7, and creating a clone of that drive with its PowerQuest Recovery Environment software, I've been living is a fool's paradise. I discovered this when I went to create the monthly Drive Image yesterday, and create the clone on a newly purchased hard drive. I've been living with my Master drive booting to a choice between normal start-up and Recovery Console, a minor annoyance because after a ten-second countdown it goes to normal boot, automatically. No problem there. I believe that the main part of the problem is now that the new exact clone does not have Master Boot Record correct, because the 'Normal Boot' path leads to the choices of Safe Mode or Normal etcetera, and no choice gets to anything other than a repeat of that set of choices. If I select Recovery Console, I get a short DOS-type message saying that file 'xxxxx.dll' is missing, and to reload it somehow from somewhere. I suspect that more than one '.dll' file will be in the list of what it needs. I tried selecting Recovery Console, hoping that I could somehow do a FIXMBR there, but I can't get to RC. Incidentally, in running Drive Image, I've repeated the whole image-and-recreate process, with and without the 'keep the MBR' option, with no apparent difference in results. I've tried to solve the problem without going to you experts, but what I've considered all logical paths haven't solved it. William B. Lurie -- William B. Lurie |
#12
|
|||
|
|||
FIXMBR redux
On Tue, 01 Jun 2004 17:31:52 -0400, William B. Lurie wrote:
Yes, the drive onto which I Recover the Image is Active and Primary. It is brand new and not even partitioned. The above statement cannot be true if there are no existing partitions. Suggestion: Partition and format the drive. Then clone your image to it. I think the next step will be for you, or Michael, to instruct me how to deactivate the RC altogether, after which I will first test my Master Drive (and pray that it will still work), and then repeat the D-I Image creation followed by trying to create the clone from it. To make it less troublesome to boot, you could reduce the timeout to 3 seconds. To remove the recovery console, delete the cmdcons folder off of C: and edit the boot.ini file to remove the reference to it. -- Sharon F MS-MVP ~ Windows XP Shell/User |
#13
|
|||
|
|||
FIXMBR redux
Michael Solomon (MS-MVP Windows Shell/User) wrote:
First, I'm assuming you did, in fact, install the Recovery Console to your hard drive. Michael, several months ago you helped me install RC to my Master hard drive. Were both hard drives connected to the system when you created the image of the first drive? I thought I stated that D-I 7 is on my Master Drive, and I use it to create a Drive Image on a sepate, Slave Drive. Then I take out and off the Master Drive, put there instead a newly formatted drive, with only one 'partition' if you call it that, the full drive. Then I use PowerQuest's PQRE (Power Quest Recovery Environment) to (supposedly) create, on the new blank master drive, a clone of the drive that was there. Specifically, Drive Image 7 is what PowerQuest supplies for XP. It is not for 98 or ME or Windows 2000. The furnish Drive Image 6 for earlier systems. Don't you think that RC has outlived its usefulness on my system, and may actually be standing in the way of Drive Image's Restore software from exactly recreating my drive? If so, I'd appreciate specific instructions on how to get it out of the way during boot-up. -- William B. Lurie |
#14
|
|||
|
|||
FIXMBR redux
William, I did not ask the question I meant to ask. I meant to ask, were
both drives connected to the system when you first installed XP on the primary drive. If not, then XP setup, never saw the second drive. If you added the drive after you installed XP and then imaged the first drive to the second drive, that might account for the HAL error as it sees the new drive, though an image of the first drive as though it were a separate computer. -- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "William B. Lurie" wrote in message ... Michael Solomon (MS-MVP Windows Shell/User) wrote: First, I'm assuming you did, in fact, install the Recovery Console to your hard drive. Michael, several months ago you helped me install RC to my Master hard drive. Were both hard drives connected to the system when you created the image of the first drive? I thought I stated that D-I 7 is on my Master Drive, and I use it to create a Drive Image on a sepate, Slave Drive. Then I take out and off the Master Drive, put there instead a newly formatted drive, with only one 'partition' if you call it that, the full drive. Then I use PowerQuest's PQRE (Power Quest Recovery Environment) to (supposedly) create, on the new blank master drive, a clone of the drive that was there. Specifically, Drive Image 7 is what PowerQuest supplies for XP. It is not for 98 or ME or Windows 2000. The furnish Drive Image 6 for earlier systems. Don't you think that RC has outlived its usefulness on my system, and may actually be standing in the way of Drive Image's Restore software from exactly recreating my drive? If so, I'd appreciate specific instructions on how to get it out of the way during boot-up. -- William B. Lurie |
#15
|
|||
|
|||
FIXMBR redux
Michael Solomon (MS-MVP Windows Shell/User) wrote:
William, I did not ask the question I meant to ask. I meant to ask, were both drives connected to the system when you first installed XP on the primary drive. I am sure that, way back when I installed XP on the primary drive, I had no slave drive. However, I don't understand the significance. When both drives are online, I only 'run' the master. The slave doesn't even have an OS on it. If not, then XP setup, never saw the second drive. If you added the drive after you installed XP and then imaged the first drive to the second drive, that might account for the HAL error as it sees the new drive, though an image of the first drive as though it were a separate computer. I must clarify quickly an error in what version of D-I is for what. I quote their Installation Instructions: "Drive Image for Windows 2000, Windows XP. Drive Image 7.0 does not run under Windows 9x, Windows ME, or Windows NT 4.0 Workstation. If you have one of these operating systems, use the Drive Image CD that is marked for your operating system". I really think I should de-activate RC frommy Master drive, and make sure it is bootable (suicide would be an alternative), and then make a fresh Drive Image of it, on my Slave Drive, and then try to Recover a clone from that fresh drive image. But I need specific instructions on how to do so, if you agree. William B. Lurie |
Thread Tools | |
Display Modes | |
|
|