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 |
#31
|
|||
|
|||
FIXMBR redux
Sharon F wrote:
On Wed, 02 Jun 2004 07:40:05 -0400, William B. Lurie wrote: For one thing, I'd like to take Recovery Console out of the picture, and not by reducing its delay time to zero, but just remove that option. If any of the MVPs told me how to do that, I missed it. It was at the end of my other post to you: "To remove the recovery console, delete the cmdcons folder from the root (usually C and edit the boot.ini file to remove the reference to it." You can also delete the cmldr file that is added by the recovery console installation - also in the root folder. William, the term image is used interchangeably for a cloned hard drive and for an image set that is restored using the imaging software. Usually which type of image is being discussed is noted very early in a discussion so that both parties are on the same page. This is why I made the effort to define the distinction at the beginning of my previous message. Vanguard picked up on what I was trying to say and did a great job expanding on the two different meanings. Thanks, Vanguard! Oh, you are at least 105% correct, Sharon. On all counts. And I did see your note and saved the message but didn't follow up right away (or yet) because I wasn't sure I could find all the items. I'm in a ticklish position: I willingly perform any operations on the clones while keeping the Master off the system, out of harm's way, but I'm reluctant to do anything to the Master which might cause me to have *no* working system. My question, obviously, is, if I do what you show in quotes above, am I taking any chance at all that I'm endangering my Master system? Bill Lurie |
Ads |
#32
|
|||
|
|||
FIXMBR redux
On Wed, 02 Jun 2004 09:54:57 -0400, William B. Lurie wrote:
Oh, you are at least 105% correct, Sharon. On all counts. And I did see your note and saved the message but didn't follow up right away (or yet) because I wasn't sure I could find all the items. I'm in a ticklish position: I willingly perform any operations on the clones while keeping the Master off the system, out of harm's way, but I'm reluctant to do anything to the Master which might cause me to have *no* working system. My question, obviously, is, if I do what you show in quotes above, am I taking any chance at all that I'm endangering my Master system? No chances that I know of. I had the Recovery Console installed too with a 3 second time out. Eventually I removed it too. Those were the steps I used (including the deletion of the cmldr file) and my setup didn't keel over. The same directions can be found in this document: http://support.microsoft.com/default.aspx?scid=307654 -- Sharon F MS-MVP ~ Windows XP Shell/User |
#33
|
|||
|
|||
FIXMBR redux
Sharon F wrote:
On Wed, 02 Jun 2004 07:40:05 -0400, William B. Lurie wrote: For one thing, I'd like to take Recovery Console out of the picture, and not by reducing its delay time to zero, but just remove that option. If any of the MVPs told me how to do that, I missed it. It was at the end of my other post to you: "To remove the recovery console, delete the cmdcons folder from the root (usually C and edit the boot.ini file to remove the reference to it." You can also delete the cmldr file that is added by the recovery console installation - also in the root folder. William, the term image is used interchangeably for a cloned hard drive and for an image set that is restored using the imaging software. Usually which type of image is being discussed is noted very early in a discussion so that both parties are on the same page. This is why I made the effort to define the distinction at the beginning of my previous message. Vanguard picked up on what I was trying to say and did a great job expanding on the two different meanings. Thanks, Vanguard! Sharon, it's indeed unfortunate that the software designer, in PQ, chose to leave the words 'copy' and 'image' mixed up. What they call a "drive image" is indeed a bunch of code which their own recovery program is supposed to convert to a clone or exact copy or duplicate of the original. Neither they nore anybody else has made it clear to tired, muddled old me, why that two-step capability is necessary or even desirable. So I went back to where I was a month ago, when I tried making what PowerQuest describes as a "copy". I installed my Slave drive as Master and formatted it anew, as Active and Primary, and empty. I then jumpered it as Slave, put it in Slave position, put my Master on as Master, and used Drive Image 7.0 to "Copy One Drive to Another This copes the contents of your Drive directly to another drive". Actually, I copied only the first (Master) partition of my Master Drive to the Slave. I used Partition Magic to verify that the Slave Drive contained very close to the same number of bytes as the Master OS. I then shut down, jumpered the Slave Drive as a Single Drive, put it in Master position on the cable, no other drive present, and booted up. It got to where I was when I did this same thing a month ago, so at least it's reproducible. It booted through BIOS, to the place where I could select XP Pro or Recovery Console, I picked XP, and got the black Windows logo screen, and then after the usual wait, the light blue Windows logo screen, which should say "loading your personal settings"........and there it hangs. So Windows copied nicely, and all my data and files and programs and applications copied nicely, but it doesn't get to the "Loading your personal settings" place. Those words are missing from the light blue screen, and that's where I was when one of the MVPs (who shall remain nameless) convinced me that I should not use the "Drive Copy" path, that I really wanted the Image. Well, he couldn't get me past that road block, in the XP boot-up procedure, Sharon, maybe you can? Or maybe I need the other piece of software that somebody just suggested here. By the way, I searched for cmdcons folder on C:\ and can't find it. Yes, I told it to seek hidden files. I did find it in boot.ini, however. -- William B. Lurie |
#34
|
|||
|
|||
FIXMBR redux
Sharon F wrote:
On Wed, 02 Jun 2004 09:54:57 -0400, William B. Lurie wrote: Oh, you are at least 105% correct, Sharon. On all counts. And I did see your note and saved the message but didn't follow up right away (or yet) because I wasn't sure I could find all the items. I'm in a ticklish position: I willingly perform any operations on the clones while keeping the Master off the system, out of harm's way, but I'm reluctant to do anything to the Master which might cause me to have *no* working system. My question, obviously, is, if I do what you show in quotes above, am I taking any chance at all that I'm endangering my Master system? No chances that I know of. I had the Recovery Console installed too with a 3 second time out. Eventually I removed it too. Those were the steps I used (including the deletion of the cmldr file) and my setup didn't keel over. The same directions can be found in this document: http://support.microsoft.com/default.aspx?scid=307654 Okay, I put the clone back in Slave spot so that I could search and make the deletions you recommended. I found boot.ini and removed the line referring to CMDCONS. That's the first good news. The first bad news is that Search couldn't find CMDCONS itself, nor could it find CMLDR. The second good news is that I ran that drive again in Master or Single position (alone, as Master) and this time it (of course) didn't do the RC choice,ecause it is gone from boot.ini .... But the second bad news is that it proceeds then to the black Windows XP logo screen, and then to the light blue screen where it should load my personal settings......and still hangs there. So I'll hope you can tell me how to get past that road block. Bill Lurie |
#35
|
|||
|
|||
FIXMBR redux
"C:\cmdcons" is where mine is found. Just open Explorer.
--=20 Just my 2=A2 worth Jeff __________in response to__________ "William B. Lurie" wrote in message = ... =BB snip =AB|=20 | By the way, I searched for cmdcons folder on C:\ and can't find | it. Yes, I told it to seek hidden files. I did find it in boot.ini, | however. |=20 | --=20 | William B. Lurie |
#36
|
|||
|
|||
FIXMBR redux
» mrtee « wrote:
"C:\cmdcons" is where mine is found. Just open Explorer. Thanks, Jeff. I looked for cmdcons and \cmdcons all over c: ..... several ways. Windows Explorer; Search; and even went to run 'cmd' and went to c:\ root directory and I couldn't find it. And of course, I did all the *show hidden files and folders* and cleared the Hide Protected operating system files. Of course, if I can't find those files and folders, then I don't have to delete them. -- William B. Lurie |
#37
|
|||
|
|||
FIXMBR redux
Well, I'm not sure, should I be insulted?
William, I did the best I could for you under the circumstances and I did initially try to direct you to the hardware forum where I thought there might be users who had done what you were trying to do. Second, when pressed, I tried to help but cautioned I had not done precisely what you were attempting. Third, my understanding of a "drive copy" versus an "image" is exactly the opposite of what has been presented in that the copy is simply a copy of what is on the drive while an image is an exact sector by sector duplicate. You've now had problems attempting to do what you are trying to do with either method, using the same product. Perhaps you are using the wrong product, (That's rhetorical, I don't want to be accused of encouraging you to use a different product only to have it fail as well and get blamed for that tooG) perhaps it's the nature of your setup or perhaps it's the manner in which you are using the product; I don't know. I've had some pretty vile things said to me and about me on these boards, usually from people that I wasn't even trying to help and often from people who contributed nothing else to a particular thread. That was easy to ignore. But, when I've gone out of my way to help someone who from the very outset I specifically told I had not done this procedure in the manner it was being done yet gave whatever benefit of my experience I could when pressed by that someone and he has the temerity seemingly to offer up an implied dig in my direction, I can't help but find that a bit insulting. I wasn't arguing with you last night with regard to my interpretation of the issue. I cannot be sure XP's anti-piracy scheme is the source of the problem but I said and reiterate the error message is consistent with that being the issue. Kirk to Spock, "Nonsense, no ship that size could generate energy enough to hold a ship the size of the Enterprise." Spock to Kirk, "We are being held, Captain," and all the logic in the world and pronouncements about imaging software doesn't change the fact, you did indeed receive such a message and it is consistent with that type of issue and I had this concern and expressed it from the very beginning. I don't expect to be complimented, especially when I haven't resolved the issue but I don't appreciate left handed comments when I've gone out of my way to help someone and have spent as much time on the issue as I have with you. Symantec has a bulletin board on USENET, it's simply listed as symantec.support. If you can't find it in your newsreader on a USENET server to which you might have access, you might find at Google under groups. Perhaps, you will be able to find someone there who has tried precisely what you are attempting and will know what is wrong. The issue I sited, may only be a symptom, perhaps someone who is doing this can diagnose the cause and give you the help you need. -- 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 ... Sharon F wrote: On Wed, 02 Jun 2004 07:40:05 -0400, William B. Lurie wrote: For one thing, I'd like to take Recovery Console out of the picture, and not by reducing its delay time to zero, but just remove that option. If any of the MVPs told me how to do that, I missed it. It was at the end of my other post to you: "To remove the recovery console, delete the cmdcons folder from the root (usually C and edit the boot.ini file to remove the reference to it." You can also delete the cmldr file that is added by the recovery console installation - also in the root folder. William, the term image is used interchangeably for a cloned hard drive and for an image set that is restored using the imaging software. Usually which type of image is being discussed is noted very early in a discussion so that both parties are on the same page. This is why I made the effort to define the distinction at the beginning of my previous message. Vanguard picked up on what I was trying to say and did a great job expanding on the two different meanings. Thanks, Vanguard! Sharon, it's indeed unfortunate that the software designer, in PQ, chose to leave the words 'copy' and 'image' mixed up. What they call a "drive image" is indeed a bunch of code which their own recovery program is supposed to convert to a clone or exact copy or duplicate of the original. Neither they nore anybody else has made it clear to tired, muddled old me, why that two-step capability is necessary or even desirable. So I went back to where I was a month ago, when I tried making what PowerQuest describes as a "copy". I installed my Slave drive as Master and formatted it anew, as Active and Primary, and empty. I then jumpered it as Slave, put it in Slave position, put my Master on as Master, and used Drive Image 7.0 to "Copy One Drive to Another This copes the contents of your Drive directly to another drive". Actually, I copied only the first (Master) partition of my Master Drive to the Slave. I used Partition Magic to verify that the Slave Drive contained very close to the same number of bytes as the Master OS. I then shut down, jumpered the Slave Drive as a Single Drive, put it in Master position on the cable, no other drive present, and booted up. It got to where I was when I did this same thing a month ago, so at least it's reproducible. It booted through BIOS, to the place where I could select XP Pro or Recovery Console, I picked XP, and got the black Windows logo screen, and then after the usual wait, the light blue Windows logo screen, which should say "loading your personal settings"........and there it hangs. So Windows copied nicely, and all my data and files and programs and applications copied nicely, but it doesn't get to the "Loading your personal settings" place. Those words are missing from the light blue screen, and that's where I was when one of the MVPs (who shall remain nameless) convinced me that I should not use the "Drive Copy" path, that I really wanted the Image. Well, he couldn't get me past that road block, in the XP boot-up procedure, Sharon, maybe you can? Or maybe I need the other piece of software that somebody just suggested here. By the way, I searched for cmdcons folder on C:\ and can't find it. Yes, I told it to seek hidden files. I did find it in boot.ini, however. -- William B. Lurie |
#38
|
|||
|
|||
FIXMBR redux
Michael, please take no umbrage. Realize that it is frustrating,
and the whole system of narrow-band Q & A and waiting only adds to the frustration. You may be right, and "they" may be right, but your definitions of "image" and "copy" are the reverse of what some other knowledgeable people prefer. As you say, I've tried both and they lead me ultimately to the same place, which is almost a dead end. Even the Microsoft Article 307654 doesn't accurately lead me to folders and files that should be there. Maybe if they were there, my system would work the way it should. I acknowledge with appreciation that you spent considerable time and effort trying to educate me, and to work through to a solution to the problem. That you didn't succeed doesn't mean that you failed....the problem may not be solvable. It may be an after-effect or interactive effect, caused by Microsoft's passion or obsession with security. Note, however, that others have succeeded, maybe by starting with a cleaner system. As for Norton, their practice is to give you a document which includes links to five other documents, each of which has links to five other documents, and you have to print them all out because you can't possibly remember what steps to take or what registry items to find and delete, and the end result is even more unsatisfying than what we've been going through. Even more so than 307654 to which I was recently directed. Again, please don't misinterpret my frustration and impatience as dissatisfaction with your spirit of cooperation, only with the end result. Michael Solomon (MS-MVP Windows Shell/User) wrote: Well, I'm not sure, should I be insulted? William, I did the best I could for you under the circumstances and I did initially try to direct you to the hardware forum where I thought there might be users who had done what you were trying to do. Second, when pressed, I tried to help but cautioned I had not done precisely what you were attempting. Third, my understanding of a "drive copy" versus an "image" is exactly the opposite of what has been presented in that the copy is simply a copy of what is on the drive while an image is an exact sector by sector duplicate. You've now had problems attempting to do what you are trying to do with either method, using the same product. Perhaps you are using the wrong product, (That's rhetorical, I don't want to be accused of encouraging you to use a different product only to have it fail as well and get blamed for that tooG) perhaps it's the nature of your setup or perhaps it's the manner in which you are using the product; I don't know. I've had some pretty vile things said to me and about me on these boards, usually from people that I wasn't even trying to help and often from people who contributed nothing else to a particular thread. That was easy to ignore. But, when I've gone out of my way to help someone who from the very outset I specifically told I had not done this procedure in the manner it was being done yet gave whatever benefit of my experience I could when pressed by that someone and he has the temerity seemingly to offer up an implied dig in my direction, I can't help but find that a bit insulting. I wasn't arguing with you last night with regard to my interpretation of the issue. I cannot be sure XP's anti-piracy scheme is the source of the problem but I said and reiterate the error message is consistent with that being the issue. Kirk to Spock, "Nonsense, no ship that size could generate energy enough to hold a ship the size of the Enterprise." Spock to Kirk, "We are being held, Captain," and all the logic in the world and pronouncements about imaging software doesn't change the fact, you did indeed receive such a message and it is consistent with that type of issue and I had this concern and expressed it from the very beginning. I don't expect to be complimented, especially when I haven't resolved the issue but I don't appreciate left handed comments when I've gone out of my way to help someone and have spent as much time on the issue as I have with you. Symantec has a bulletin board on USENET, it's simply listed as symantec.support. If you can't find it in your newsreader on a USENET server to which you might have access, you might find at Google under groups. Perhaps, you will be able to find someone there who has tried precisely what you are attempting and will know what is wrong. The issue I sited, may only be a symptom, perhaps someone who is doing this can diagnose the cause and give you the help you need. -- William B. Lurie |
#39
|
|||
|
|||
FIXMBR redux
Sharon, thank you for the link to the Micro site on RC.
That told a lot, maybe more than we realize. Maybe my system doesn't act right because some files that ought to be there, aren't. Like, I can't remove what isn't there, but who knows what else ought to be there, that could be halting my XP initializing and loading all the way? But I scanned the Master, which does boot okay, and I can't find cmdcons folder or cmldr file. I suppose they're all on the Installation CD, but I wouldn't know what to look for, or how to get it repaired via Repair Install. I'm enjoying the process of getting educated, even though it's obvious that my frustration can be misinterpreted. -- William B. Lurie |
#40
|
|||
|
|||
FIXMBR redux
Okay, William, I apologize for my stridency, your post just seemed to touch
a raw nerve with me. I understand your frustration and don't blame you for being annoyed, you are justifiably so. The Symantec newsgroup to which I pointed you is a user to user, peer support group much the same as this group. They may point you toward Norton Ghost, a very good product that I have used as well. As such, you might be able to explain to the users what you are trying to do, what errors you've received and they may be able to tell you why you've been having trouble (Which may require an in-depth description of the procedure you followed) or if what you are trying to do can be done. You should be able to get more their than what you get from the Symantec website or their e-mail tech support. -- 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, please take no umbrage. Realize that it is frustrating, and the whole system of narrow-band Q & A and waiting only adds to the frustration. You may be right, and "they" may be right, but your definitions of "image" and "copy" are the reverse of what some other knowledgeable people prefer. As you say, I've tried both and they lead me ultimately to the same place, which is almost a dead end. Even the Microsoft Article 307654 doesn't accurately lead me to folders and files that should be there. Maybe if they were there, my system would work the way it should. I acknowledge with appreciation that you spent considerable time and effort trying to educate me, and to work through to a solution to the problem. That you didn't succeed doesn't mean that you failed....the problem may not be solvable. It may be an after-effect or interactive effect, caused by Microsoft's passion or obsession with security. Note, however, that others have succeeded, maybe by starting with a cleaner system. As for Norton, their practice is to give you a document which includes links to five other documents, each of which has links to five other documents, and you have to print them all out because you can't possibly remember what steps to take or what registry items to find and delete, and the end result is even more unsatisfying than what we've been going through. Even more so than 307654 to which I was recently directed. Again, please don't misinterpret my frustration and impatience as dissatisfaction with your spirit of cooperation, only with the end result. Michael Solomon (MS-MVP Windows Shell/User) wrote: Well, I'm not sure, should I be insulted? William, I did the best I could for you under the circumstances and I did initially try to direct you to the hardware forum where I thought there might be users who had done what you were trying to do. Second, when pressed, I tried to help but cautioned I had not done precisely what you were attempting. Third, my understanding of a "drive copy" versus an "image" is exactly the opposite of what has been presented in that the copy is simply a copy of what is on the drive while an image is an exact sector by sector duplicate. You've now had problems attempting to do what you are trying to do with either method, using the same product. Perhaps you are using the wrong product, (That's rhetorical, I don't want to be accused of encouraging you to use a different product only to have it fail as well and get blamed for that tooG) perhaps it's the nature of your setup or perhaps it's the manner in which you are using the product; I don't know. I've had some pretty vile things said to me and about me on these boards, usually from people that I wasn't even trying to help and often from people who contributed nothing else to a particular thread. That was easy to ignore. But, when I've gone out of my way to help someone who from the very outset I specifically told I had not done this procedure in the manner it was being done yet gave whatever benefit of my experience I could when pressed by that someone and he has the temerity seemingly to offer up an implied dig in my direction, I can't help but find that a bit insulting. I wasn't arguing with you last night with regard to my interpretation of the issue. I cannot be sure XP's anti-piracy scheme is the source of the problem but I said and reiterate the error message is consistent with that being the issue. Kirk to Spock, "Nonsense, no ship that size could generate energy enough to hold a ship the size of the Enterprise." Spock to Kirk, "We are being held, Captain," and all the logic in the world and pronouncements about imaging software doesn't change the fact, you did indeed receive such a message and it is consistent with that type of issue and I had this concern and expressed it from the very beginning. I don't expect to be complimented, especially when I haven't resolved the issue but I don't appreciate left handed comments when I've gone out of my way to help someone and have spent as much time on the issue as I have with you. Symantec has a bulletin board on USENET, it's simply listed as symantec.support. If you can't find it in your newsreader on a USENET server to which you might have access, you might find at Google under groups. Perhaps, you will be able to find someone there who has tried precisely what you are attempting and will know what is wrong. The issue I sited, may only be a symptom, perhaps someone who is doing this can diagnose the cause and give you the help you need. -- William B. Lurie |
#41
|
|||
|
|||
FIXMBR redux
Sharon, between Michael's help and yours, I've made
a bit of progress. On my 'cloned' OS, removing the call from boot.ini let it boot past the choice between XP and RC....to the black with WIN XP Logo screen.... past there to the light blue WIN XP Logo screen (that's good)....but the bad part is that what also belongs on that screen is "Loading your personal settings" (but isn't there), and that it doesn't load my personal settings and proceed on. Also bad is that the file and folder mentioned in the Delete RC document, I never found, but then again maybe that isn't all bad, since I was supposed to delete them anyway. So that takes me to a specific place in the start-up, where perhaps you can diagnose why it hangs at that particular spot. I hope you can see why I don't try this on my working Master system; if I tgo there and delete the last line in boot.ini, I'd very likely have a Master system, now working, that would no longer boot all the way, and then I'd have two non- working systems. Right now I only have one, and we have to fix that one, not the Master. -- William B. Lurie |
#42
|
|||
|
|||
FIXMBR redux
Here's a thought, though I'm not sure it would work because it will place a
file on your unbootable drive but you might use the option to log the boot on the bootable drive (You find this option, I've forgotten the name for the moment) on the same menu as Safe Mode; boot the system, start tapping F8, select the appropriate option which will be obvious by the name and check that log. Then do the same thing on the unbootable drive, it too, should create a bootlog. If you can access it, you might be able to compare the two and see on what exactly the boot is choking. -- 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 ... Sharon, between Michael's help and yours, I've made a bit of progress. On my 'cloned' OS, removing the call from boot.ini let it boot past the choice between XP and RC....to the black with WIN XP Logo screen.... past there to the light blue WIN XP Logo screen (that's good)....but the bad part is that what also belongs on that screen is "Loading your personal settings" (but isn't there), and that it doesn't load my personal settings and proceed on. Also bad is that the file and folder mentioned in the Delete RC document, I never found, but then again maybe that isn't all bad, since I was supposed to delete them anyway. So that takes me to a specific place in the start-up, where perhaps you can diagnose why it hangs at that particular spot. I hope you can see why I don't try this on my working Master system; if I tgo there and delete the last line in boot.ini, I'd very likely have a Master system, now working, that would no longer boot all the way, and then I'd have two non- working systems. Right now I only have one, and we have to fix that one, not the Master. -- William B. Lurie |
#43
|
|||
|
|||
FIXMBR redux
On Wed, 2 Jun 2004 12:08:23 -0700, Michael Solomon (MS-MVP Windows
Shell/User) wrote: Okay, William, I apologize for my stridency, your post just seemed to touch a raw nerve with me. I understand your frustration and don't blame you for being annoyed, you are justifiably so. The Symantec newsgroup to which I pointed you is a user to user, peer support group much the same as this group. They may point you toward Norton Ghost, a very good product that I have used as well. As such, you might be able to explain to the users what you are trying to do, what errors you've received and they may be able to tell you why you've been having trouble (Which may require an in-depth description of the procedure you followed) or if what you are trying to do can be done. You should be able to get more their than what you get from the Symantec website or their e-mail tech support. Michael, I hope I didn't put an extra twist in this. I have great respect for your knowledge and abilities. Apologies to you if anything I said made you uncomfortable as that was not my intention. Your help in William's experiments has been amazing and a learning experience for me. Personally, I've used Drive Image and Image for Windows to create compressed images of a drive. Have also restored those images successfully. However, I've never created a cloned drive/copied drive/imaged drive that can be dropped into place to run the operating system. -- Sharon F MS-MVP ~ Windows XP Shell/User |
#44
|
|||
|
|||
FIXMBR redux
On Wed, 02 Jun 2004 14:48:45 -0400, William B. Lurie wrote:
Sharon, thank you for the link to the Micro site on RC. That told a lot, maybe more than we realize. Maybe my system doesn't act right because some files that ought to be there, aren't. Like, I can't remove what isn't there, but who knows what else ought to be there, that could be halting my XP initializing and loading all the way? But I scanned the Master, which does boot okay, and I can't find cmdcons folder or cmldr file. I suppose they're all on the Installation CD, but I wouldn't know what to look for, or how to get it repaired via Repair Install. I'm enjoying the process of getting educated, even though it's obvious that my frustration can be misinterpreted. If you don't have the file and folder, you don't have them. There's nothing to delete and the boot path in boot.ini has been removed. Makes one wonder where you would have ended up if you had elected to boot with the Recovery Console though. I think that all you've accomplished so far is to eliminate the presence of a second boot option as the cause for the boot failure. You'll need to look elsewhere for it. I see Michael has made some good suggestions for you about trying a logged boot. Sounds like a worthwhile plan. -- Sharon F MS-MVP ~ Windows XP Shell/User |
#45
|
|||
|
|||
FIXMBR redux
Thank you, Sharon.
Nothing you did or said was an issue for me. -- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "Sharon F" wrote in message ... On Wed, 2 Jun 2004 12:08:23 -0700, Michael Solomon (MS-MVP Windows Shell/User) wrote: Okay, William, I apologize for my stridency, your post just seemed to touch a raw nerve with me. I understand your frustration and don't blame you for being annoyed, you are justifiably so. The Symantec newsgroup to which I pointed you is a user to user, peer support group much the same as this group. They may point you toward Norton Ghost, a very good product that I have used as well. As such, you might be able to explain to the users what you are trying to do, what errors you've received and they may be able to tell you why you've been having trouble (Which may require an in-depth description of the procedure you followed) or if what you are trying to do can be done. You should be able to get more their than what you get from the Symantec website or their e-mail tech support. Michael, I hope I didn't put an extra twist in this. I have great respect for your knowledge and abilities. Apologies to you if anything I said made you uncomfortable as that was not my intention. Your help in William's experiments has been amazing and a learning experience for me. Personally, I've used Drive Image and Image for Windows to create compressed images of a drive. Have also restored those images successfully. However, I've never created a cloned drive/copied drive/imaged drive that can be dropped into place to run the operating system. -- Sharon F MS-MVP ~ Windows XP Shell/User |
Thread Tools | |
Display Modes | |
|
|