Paragon Drive Backup, Windows 7 and P2P adjust.

I have converted to Windows 7 from XP and already know I will miss the
"repair/install" or "in place upgrade"
feature of Windows XP. Under XP I could replace my motherboard/Processor and
run the "repair install" from the XP
CD and have the new mother board boot and run XP with no problem. All the
installed programs, such as Office and
Firefox were still there and functional. Under Win 7 they do not get carried
over to the new MB computer according
to post here and elsewhere and will have to be reinstalled. Under XP, I did
have to reactivate with a 'phone call
to MS but that was no big deal. Apparently

As I understand it, Paragon's Drive Backup Professional 10's P2P Adjust
feature will allow me install a new MB or
other major hardware and restore EVERYTHING from a Paragon backup to the
modified computer without having to
reinstall my programs.

Yes. I know Win 7 has a repair install feature that will make an unbootable
Win 7 run on a 'repaired' machine. But
from what I read here and in the Windows 7 forums, if I use it, it
apparently will not incorporate my Office 2003,
Firefox and other such things into the 'repaired' system as XP did. I will
have to reinstall them.

Am I wrong? I hope so.

Has anyone used Win 7's repair/install to rejuvenate Win 7 and user programs
after replacing an MG in the way XP did?

Thanks

"Jack Gillis" <> wrote in message
news:...
>
> I have converted to Windows 7 from XP and already know I will miss the
> "repair/install" or "in place upgrade"
> feature of Windows XP. Under XP I could replace my motherboard/Processor
> and run the "repair install" from the XP
> CD and have the new mother board boot and run XP with no problem. All the
> installed programs, such as Office and
> Firefox were still there and functional. Under Win 7 they do not get
> carried over to the new MB computer according
> to post here and elsewhere and will have to be reinstalled. Under XP, I
> did have to reactivate with a 'phone call
> to MS but that was no big deal. Apparently
>
> As I understand it, Paragon's Drive Backup Professional 10's P2P Adjust
> feature will allow me install a new MB or
> other major hardware and restore EVERYTHING from a Paragon backup to the
> modified computer without having to
> reinstall my programs.
>
> Yes. I know Win 7 has a repair install feature that will make an
> unbootable Win 7 run on a 'repaired' machine. But
> from what I read here and in the Windows 7 forums, if I use it, it
> apparently will not incorporate my Office 2003,
> Firefox and other such things into the 'repaired' system as XP did. I will
> have to reinstall them.
>
> Am I wrong? I hope so.
>
> Has anyone used Win 7's repair/install to rejuvenate Win 7 and user
> programs after replacing an MG in the way XP did?


Just like XP, Win7 (and Vista) have the ability to be prepared for new
hardware. The MS supplied SYSPREP utility sets the installation to a
hardware neutral state. Shutdown, replace motherboard and when you startup
again the OS does hardware scan just like it did during initial
installation.

This is the same methods large companies use to have a single image work on
all the hardware they own with all the common software already installed.

"Seth" <> wrote in message
news:hngnmp$7nu$...
> "Jack Gillis" <> wrote in message
> news:...
>>
>> I have converted to Windows 7 from XP and already know I will miss the
>> "repair/install" or "in place upgrade"
>> feature of Windows XP. Under XP I could replace my motherboard/Processor
>> and run the "repair install" from the XP
>> CD and have the new mother board boot and run XP with no problem. All the
>> installed programs, such as Office and
>> Firefox were still there and functional. Under Win 7 they do not get
>> carried over to the new MB computer according
>> to post here and elsewhere and will have to be reinstalled. Under XP, I
>> did have to reactivate with a 'phone call
>> to MS but that was no big deal. Apparently
>>
>> As I understand it, Paragon's Drive Backup Professional 10's P2P Adjust
>> feature will allow me install a new MB or
>> other major hardware and restore EVERYTHING from a Paragon backup to the
>> modified computer without having to
>> reinstall my programs.
>>
>> Yes. I know Win 7 has a repair install feature that will make an
>> unbootable Win 7 run on a 'repaired' machine. But
>> from what I read here and in the Windows 7 forums, if I use it, it
>> apparently will not incorporate my Office 2003,
>> Firefox and other such things into the 'repaired' system as XP did. I
>> will have to reinstall them.
>>
>> Am I wrong? I hope so.
>>
>> Has anyone used Win 7's repair/install to rejuvenate Win 7 and user
>> programs after replacing an MG in the way XP did?
>
>
> Just like XP, Win7 (and Vista) have the ability to be prepared for new
> hardware. The MS supplied SYSPREP utility sets the installation to a
> hardware neutral state. Shutdown, replace motherboard and when you
> startup again the OS does hardware scan just like it did during initial
> installation.
>
> This is the same methods large companies use to have a single image work
> on all the hardware they own with all the common software already
> installed.
>

Thank you Seth.

I am familiar, but not experienced, with the Sysprep method you mentioned.
However it seems complex compared to what I had to do under XP. Under XP I
could simply reboot the machine using the XP CD after installing the new MB
and doing a Repair/Install (sometimes called an Upgrade Install.) The
process would make the necessary changes to XP and give me a running system
just like it was before the MB change out. I used that method at least 5
times on two different boxes over the years. It was almost too easy.
Apparently Win 7 doesn't offer that method, at least that is what I infer
from poking around the web.

Thanks again.

"Jack Gillis" <> wrote in message
news...
>
>
> "Seth" <> wrote in message
> news:hngnmp$7nu$...
>> "Jack Gillis" <> wrote in message
>> news:...
>>>
>>> I have converted to Windows 7 from XP and already know I will miss the
>>> "repair/install" or "in place upgrade"
>>> feature of Windows XP. Under XP I could replace my motherboard/Processor
>>> and run the "repair install" from the XP
>>> CD and have the new mother board boot and run XP with no problem. All
>>> the installed programs, such as Office and
>>> Firefox were still there and functional. Under Win 7 they do not get
>>> carried over to the new MB computer according
>>> to post here and elsewhere and will have to be reinstalled. Under XP, I
>>> did have to reactivate with a 'phone call
>>> to MS but that was no big deal. Apparently
>>>
>>> As I understand it, Paragon's Drive Backup Professional 10's P2P Adjust
>>> feature will allow me install a new MB or
>>> other major hardware and restore EVERYTHING from a Paragon backup to the
>>> modified computer without having to
>>> reinstall my programs.
>>>
>>> Yes. I know Win 7 has a repair install feature that will make an
>>> unbootable Win 7 run on a 'repaired' machine. But
>>> from what I read here and in the Windows 7 forums, if I use it, it
>>> apparently will not incorporate my Office 2003,
>>> Firefox and other such things into the 'repaired' system as XP did. I
>>> will have to reinstall them.
>>>
>>> Am I wrong? I hope so.
>>>
>>> Has anyone used Win 7's repair/install to rejuvenate Win 7 and user
>>> programs after replacing an MG in the way XP did?
>>
>>
>> Just like XP, Win7 (and Vista) have the ability to be prepared for new
>> hardware. The MS supplied SYSPREP utility sets the installation to a
>> hardware neutral state. Shutdown, replace motherboard and when you
>> startup again the OS does hardware scan just like it did during initial
>> installation.
>>
>> This is the same methods large companies use to have a single image work
>> on all the hardware they own with all the common software already
>> installed.
>>
>
> Thank you Seth.
>
> I am familiar, but not experienced, with the Sysprep method you mentioned.
> However it seems complex compared to what I had to do under XP. Under XP
> I could simply reboot the machine using the XP CD after installing the new
> MB and doing a Repair/Install (sometimes called an Upgrade Install.) The
> process would make the necessary changes to XP and give me a running
> system just like it was before the MB change out. I used that method at
> least 5 times on two different boxes over the years. It was almost too
> easy. Apparently Win 7 doesn't offer that method, at least that is what I
> infer from poking around the web.


Sysprep should be just as easy. Before swapping boards, SYSPREP machine and
shut down. Swap boards. Boot up and everything else is automatic.

You don't have to image the machine. Imaging is only required if you want
to capture the build with installed applications for mass distribution.

When I do image it (cause that's what I do. I'm the lead Windows desktop
engineer for 140,000 machines) I use ImageX. Also free from MS.

I moved XP installs between machines a number of times.
My technique was to go into Device Manager on the last occasion
it was used on that machine, & delete nearly everything there,
these removals don't take effect until the O/S is restarted.
Shut down.
Then when that install moves to the new machine it will Plug n Play
find & install all the various bits. Might have to restart it a number of
times to get XP to find all its bits.

Did this from an P4 Single Core with ATI AGP graphic card & IDE
Drives to a Core2Duo with NVidia PCI-E Graphics card & SATA Drives.
All was fine.
@@@@@@@@@@@

I want to do that same VISTA move as the O/P. But I've moved the Drive with
the VISTA Install to the new machine before doing that routine as mentioned
above...
And of cause it won't fully start ...gets stuck about half way through &
repeatly
restarts . Tried all the Safe Mode & DVD Repair tactics.
Repair tries hard then announces "Can't Repair This One"

My question can that SYSPREP routine be run from 'outside' ..at start up ...
The Install ? or only from within the running O/S ?
I can look at the VISTA folders from either an XP or a Win 7 running
installs
on the same machine.
(\__/)
(='.'=)
(")_(") mouse (He Does Get In a Mess)

"Trimble Bracegirdle" <no-> wrote in message
news:hnhges$5ji$...
>I moved XP installs between machines a number of times.
> My technique was to go into Device Manager on the last occasion
> it was used on that machine, & delete nearly everything there,
> these removals don't take effect until the O/S is restarted.
> Shut down.
> Then when that install moves to the new machine it will Plug n Play
> find & install all the various bits. Might have to restart it a number of
> times to get XP to find all its bits.

Sysprep does all that, and then some.

> Did this from an P4 Single Core with ATI AGP graphic card & IDE
> Drives to a Core2Duo with NVidia PCI-E Graphics card & SATA Drives.
> All was fine.
> @@@@@@@@@@@
>
> I want to do that same VISTA move as the O/P. But I've moved the Drive
> with the VISTA Install to the new machine before doing that routine as
> mentioned above...
> And of cause it won't fully start ...gets stuck about half way through &
> repeatly
> restarts . Tried all the Safe Mode & DVD Repair tactics.
> Repair tries hard then announces "Can't Repair This One"

Before it auto-restarts, is it a BSOD? If so, is it a 0x0000007B? THat
happens when the hard drive host adapter changes and the system doesn't have
a driver for new host adapter.

> My question can that SYSPREP routine be run from 'outside' ..at start up
> ...
> The Install ? or only from within the running O/S ?
> I can look at the VISTA folders from either an XP or a Win 7 running
> installs
> on the same machine.

Sysprep must be run on the "old" hardware from within the OS.

There are other ways to possibly fix the issue you are encountering while
booted within a WinPE session and manually "service" the drive with
additional drivers and what-not but it's a fairly complicated process that I
don't think I could do in a Usenet posting fashion cause each step is
dependant upon findings from the previous.

"Seth" <> wrote in message
news:hnh3vm$pvc$...
> "Jack Gillis" <> wrote in message
> news...
>>
>>
>> "Seth" <> wrote in message
>> news:hngnmp$7nu$...
>>> "Jack Gillis" <> wrote in message
>>> news:...
>>>>

Much shipped.

>>
>> I am familiar, but not experienced, with the Sysprep method you
>> mentioned. However it seems complex compared to what I had to do under
>> XP. Under XP I could simply reboot the machine using the XP CD after
>> installing the new MB and doing a Repair/Install (sometimes called an
>> Upgrade Install.) The process would make the necessary changes to XP and
>> give me a running system just like it was before the MB change out. I
>> used that method at least 5 times on two different boxes over the years.
>> It was almost too easy. Apparently Win 7 doesn't offer that method, at
>> least that is what I infer from poking around the web.
>
>
> Sysprep should be just as easy. Before swapping boards, SYSPREP machine
> and shut down. Swap boards. Boot up and everything else is automatic.
>
> You don't have to image the machine. Imaging is only required if you want
> to capture the build with installed applications for mass distribution.
>
> When I do image it (cause that's what I do. I'm the lead Windows desktop
> engineer for 140,000 machines) I use ImageX. Also free from MS.
>

Thanks again, Seth.

That gives me the warm fuzzies about Sysprep.

Thanks for your interest Seth.
Looks like a VISTA reinstall for me.
(\__/)
(='.'=)
(")_(") mouse

Jack
Seth does have a point -- if you create an image using Sysprep you wil
be able to restore (still requires activation) to a new hardwar
configuration or new pc. Bear in mind that Sysprep is designed to assis
companies in deployment. To learn more about Sysprep, please see th
following link: 'How to Use Sysprep: An Introduction
(http://technet.microsoft.com/en-us/l.../bb457073.aspx
Jessic
Microsoft Windows Client Tea

--
JessicaD