From: Carl on 29 Apr 2010 06:49 On Apr 28, 1:20 pm, "Twayne" <nob...(a)spamcop.net> wrote: > PS re the Subject line: You do not "clone" XP to a drive. A "clone" IS a > hard drive that contains the operating system. What you do is replace a bad > drive with a "cloned" drive, and in theory it will start right up. > Your problem could be in your understanding of what you're trying to > achieve. Whatever it is, it is not "cloning ... back to your HD". > > HTH, Thanks for weighing in, Twayne - You are right; I used the wrong terminology. One of the big surprises and disappointments of my introduction to Microsoft Windows was to learn that, after making a clone of your HD, if you have trouble, such as I am now having, that you could NOT copy back the clone of your HD to your internal HD. Macintosh allows this and instead of backing up each week, I use SuperDuper to clone my OS to an external HD. Haven't had to copy that clone back to my internal HD since Apple came out with OSX, but I did have to do so once or twice under OS 9 and its predecessors. Carl
From: John John - MVP on 29 Apr 2010 09:44 Carl wrote: > On Apr 28, 1:20 pm, "Twayne" <nob...(a)spamcop.net> wrote: >> PS re the Subject line: You do not "clone" XP to a drive. A "clone" IS a >> hard drive that contains the operating system. What you do is replace a bad >> drive with a "cloned" drive, and in theory it will start right up. >> Your problem could be in your understanding of what you're trying to >> achieve. Whatever it is, it is not "cloning ... back to your HD". >> >> HTH, > Thanks for weighing in, Twayne - > > You are right; I used the wrong terminology. > > One of the big surprises and disappointments of my introduction to > Microsoft Windows was to learn that, after making a clone of your HD, > if you have trouble, such as I am now having, that you could NOT copy > back the clone of your HD to your internal HD. > > Macintosh allows this and instead of backing up each week, I use > SuperDuper to clone my OS to an external HD. Haven't had to copy that > clone back to my internal HD since Apple came out with OSX, but I did > have to do so once or twice under OS 9 and its predecessors. What do you mean "you could NOT copy back the clone of your HD to your internal HD". We create clones and images all the time here and restore them back anytime without any problems. Of course, Windows PCs are much more varied than Macs, PCs come in a mutltitude of hardware configurations so moving clones or restoring images to different computers is not generally supported, whereas a Mac is a Mac is a Mac, so moving a clone or restoring an image to another Mac might not be a problem. John
From: Carl on 29 Apr 2010 14:06 On Apr 29, 9:44 am, John John - MVP <audetw...(a)nbnet.nb.ca> wrote: > Carl wrote: > > On Apr 28, 1:20 pm, "Twayne" <nob...(a)spamcop.net> wrote: > >> PS re the Subject line: You do not "clone" XP to a drive. A "clone" IS a > >> hard drive that contains the operating system. What you do is replace a bad > >> drive with a "cloned" drive, and in theory it will start right up. > >> Your problem could be in your understanding of what you're trying to > >> achieve. Whatever it is, it is not "cloning ... back to your HD". > > >> HTH, > > Thanks for weighing in, Twayne - > > > You are right; I used the wrong terminology. > > > One of the big surprises and disappointments of my introduction to > > Microsoft Windows was to learn that, after making a clone of your HD, > > if you have trouble, such as I am now having, that you could NOT copy > > back the clone of your HD to your internal HD. > > > Macintosh allows this and instead of backing up each week, I use > > SuperDuper to clone my OS to an external HD. Haven't had to copy that > > clone back to my internal HD since Apple came out with OSX, but I did > > have to do so once or twice under OS 9 and its predecessors. > > What do you mean "you could NOT copy back the clone of your HD to your > internal HD". We create clones and images all the time here and restore > them back anytime without any problems. Of course, Windows PCs are much > more varied than Macs, PCs come in a mutltitude of hardware > configurations so moving clones or restoring images to different > computers is not generally supported, whereas a Mac is a Mac is a Mac, > so moving a clone or restoring an image to another Mac might not be a > problem. > > John John - Lest my misuse of terminology confuses the situation, let me explain. What I should have said was I was told, that for licensing reasons, M/ S will not allow you to boot your machine from Windows on an external USB hard drive. I have a Seagate external HD. I used Seagate's free software to clone my Netbook's HD to an external USB HD. If I connect that USB HD, boot up, change the Boot Device Priority to list that USB HD first, then exit and save the configuration, I get nothing but a blinking white cursor on a black screen. The first time this happened, I asked on this forum, I believe, and was told that what I was doing was not possible because M/S did not allow you to boot from an external HD. I just tried it, and I am looking at the blinking cursor. Was I misinformed? Carl
From: John John - MVP on 29 Apr 2010 15:01 Carl wrote: > On Apr 29, 9:44 am, John John - MVP <audetw...(a)nbnet.nb.ca> wrote: >> Carl wrote: >>> On Apr 28, 1:20 pm, "Twayne" <nob...(a)spamcop.net> wrote: >>>> PS re the Subject line: You do not "clone" XP to a drive. A "clone" IS a >>>> hard drive that contains the operating system. What you do is replace a bad >>>> drive with a "cloned" drive, and in theory it will start right up. >>>> Your problem could be in your understanding of what you're trying to >>>> achieve. Whatever it is, it is not "cloning ... back to your HD". >>>> HTH, >>> Thanks for weighing in, Twayne - >>> You are right; I used the wrong terminology. >>> One of the big surprises and disappointments of my introduction to >>> Microsoft Windows was to learn that, after making a clone of your HD, >>> if you have trouble, such as I am now having, that you could NOT copy >>> back the clone of your HD to your internal HD. >>> Macintosh allows this and instead of backing up each week, I use >>> SuperDuper to clone my OS to an external HD. Haven't had to copy that >>> clone back to my internal HD since Apple came out with OSX, but I did >>> have to do so once or twice under OS 9 and its predecessors. >> What do you mean "you could NOT copy back the clone of your HD to your >> internal HD". We create clones and images all the time here and restore >> them back anytime without any problems. Of course, Windows PCs are much >> more varied than Macs, PCs come in a mutltitude of hardware >> configurations so moving clones or restoring images to different >> computers is not generally supported, whereas a Mac is a Mac is a Mac, >> so moving a clone or restoring an image to another Mac might not be a >> problem. >> >> John > > John - > > Lest my misuse of terminology confuses the situation, let me explain. > > What I should have said was I was told, that for licensing reasons, M/ > S will not allow you to boot your machine from Windows on an external > USB hard drive. > > I have a Seagate external HD. > > I used Seagate's free software to clone my Netbook's HD to an external > USB HD. > > If I connect that USB HD, boot up, change the Boot Device Priority to > list that USB HD first, then exit and save the configuration, I get > nothing but a blinking white cursor on a black screen. > > The first time this happened, I asked on this forum, I believe, and > was told that what I was doing was not possible because M/S did not > allow you to boot from an external HD. > > I just tried it, and I am looking at the blinking cursor. > > Was I misinformed? This has nothing to do with Microsoft's licensing, it' a technical limitation of the Windows operating system. What happens with Windows is that the USB stack is initialized well after the Windows session manager has started, so in essence Windows can't boot off a USB drive because Windows has to initialize the stack before it can use it, a catch 22 kind of situation. If you search the internet you will find information on how some have hacked the stack drivers to make them boot devices which in turn allows the ntldr boot manager to load the stack before the session manager is started. This is unsupported by Microsoft, they have never bothered rewriting the boot up routine to have ntldr load the stack so Windows can't boot off a USB drive. John
From: Carl on 29 Apr 2010 22:07 On Apr 29, 6:18 pm, "J. P. Gilliver (John)" <G6...(a)soft255.demon.co.uk> wrote: > In message > <5a264685-f302-4a10-92d5-8ad09b4da...(a)p17g2000vbe.googlegroups.com>,Carl <carlhamm...(a)gmail.com> writes: > > [] > > >> > You are right; I used the wrong terminology. > > >> > One of the big surprises and disappointments of my introduction to > >> > Microsoft Windows was to learn that, after making a clone of your HD, > >> > if you have trouble, such as I am now having, that you could NOT copy > >> > back the clone of your HD to your internal HD. > > Yes, you can. > [] > > >What I should have said was I was told, that for licensing reasons, M/ > >S will not allow you to boot your machine from Windows on an external > >USB hard drive. > > As another has said, it's technical rather than licencing reasons (and > there are people who've hacked it so that it can be done). > > > > >I have a Seagate external HD. > > >I used Seagate's free software to clone my Netbook's HD to an external > >USB HD. > > Very wise. (Not wise not to be sure how to restore it, though.) > > >If I connect that USB HD, boot up, change the Boot Device Priority to > >list that USB HD first, then exit and save the configuration, I get > >nothing but a blinking white cursor on a black screen. > > >The first time this happened, I asked on this forum, I believe, and > >was told that what I was doing was not possible because M/S did not > >allow you to boot from an external HD. > > >I just tried it, and I am looking at the blinking cursor. > > >Was I misinformed? > > [] > You can clone your HD (to all sorts of things - USB, DVD, external HD). > You can copy the clone back to your HD, for example after a corruption, > and it will restore a system that works as it did when you made the > clone. > > You cannot boot from whatever it is you cloned to - only the original > (or a replacement) HD after you've done the cloning-back. > > Whatever software you used to make the clone should have offered to make > some boot media that would be able to do the cloning-back. (I suppose it > is still valid to claim it's a cloning utility if it doesn't do this, > but it's not a lot of use without it.) > -- > J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar(a)T0H+Sh0!:`)DNAf > **http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htmfor ludicrously > outdated thoughts on PCs. ** > > A language is a dialect that has an army and a navy. -Max Weinreich, linguist > and author (1894-1969) Thanks for that explanation, J.P. This weekend, I will make another clone using the Seagate software and watch carefully to see if there is any offer to make some sort of boot media that will enable the clone to be copied back to the internal HD. Perhaps I missed it on my first clone; I am very new to Windows. Carl.
|
Next
|
Last
Pages: 1 2 3 Prev: PS Re: How to clone Windows XP back to your HD? Next: regarding bloking lan settings using GPO |