Solved Win7 Sysprep program to migrate a disk continues to reboot

[loninappleton]

I have seen the thread on the Windows 7 Sysprep program that Sevenforums provided for use to
migrate an HD to a new motherboard-- older one in this case.

After doing the instructions at the Out of Box screen, system shuts down after doing it's prep routine.
I then attached the new (old Biostar K8M800) motherboard. POST went ok and the message about DMI pool check came on and said finished or whatever. Then system reboots and shows the oldest Biostar splash screen there is (my guess) in full screen and then shuts down.

Start in safe mode also failed to load the OS to be able to get to the drivers disk.
I'll see if I can boot from the cdrom drive after POST.

What is missing? I can run Biostar drivers disk perhaps but will that initialize
with all these shutdowns?

I'm going to reconnect the cleaned disk to the original setup and see if my files are ok.

 

[loninappleton]

A bit of progress this time through. It appeares that the BIOS was cleaned and going to the setup screen showed that Floppy was the first boot device. I changed that to cdrom first and hdd second and third in the

There was an attempt to start and the Win7 throbber started up but a very brief BSOD and another shut down followed. That BSOD from my experience means the disk is rejected.

I recall from doing other operations in XP that simply deleting the generic HD driver as Administrator
works that OS. What happens is 'discovery of hardware' is involked and the OS just reinstalls that.

Here in Win7 more problems than that with using Sysprep.

Next stop is trying to run the Biostar motherboard drivers disk.

 

[loninappleton]

This time on Start Up, Safe mode was available which ran up til HD was sought. Followed by blue screen.
It flashed fast. I made out something about error 100.

Here I want to ask if System File Checker (SFC) could be invoked from CMD in Safe Mode
to reinstall the needed Win HD driver.

I thought Sysprep was supposed to correct all of this.

 

[johnhoh]

Not sure if that board supports AHCI. In bios settings, try booting from both IDE and RAID and see if either one works for you. If your first board was addressing the hard drive using AHCI mode you may be out of luck.

K8M800 Micro AM2 :: Motherboard :: BIOSTAR

 

[loninappleton]

No AHCI here on any of my builds.
I think what I'm going to do is make a fresh backup-- the old drives are for these experiments--
and try the old XP method. I'll report back.

I got hosed using Sysprep.

 

[loninappleton]

I'm reluctantly returning to another attempt at Sysprep.

Can I ask it this way: have other users here successfully used it?

Perhaps then I could copy the steps. One error I had was not saying my HD is a SATA.

I've prepared a new test disk to start over.

 

[torchwood]

Hi Ion,
just for arguements sake, why sysprep??

use the clean install option, as long as the motherboard supports W7, use the iso and away you go.
(if its that old use the 32bit OS)

Roy

 

[loninappleton]

hello Torchwood,

It was my understanding that Sysprepo would simply delete then engage the search for an HD that was fully loaded with programs and running on a newer motherboard. These happen to be Biostars.

Since I'm retro fitting an old one with a newer processor recommended as compatible by CPU World
I'm wondering if, as you hint at, the old K800 board will not recognize the Win7 64 OS.

It's something I just don't know. But a scratch install from the System disk also failed to engage.
Frankly there might be other problems with weak SATA ports. But I looked at the board bottom and don't see anything broken or cracked. I'm trying to assemble this just as a backup.

We have the board number as K8M800 Micro AM2 with the AMD ADHI640IAA4DP

bought used to replace a Sempron with a bent pin.

Thanks for answering.

 

[torchwood]

Hi Ion,
had a quick shuftee at the MB specs.
Its not that great,
suggest you run W7 Home premium 32bit, its only got 2GB ram max not good!!
and read this tutorial
Install Windows 7 on Computer with Less than 512MB RAM
your phones/ipad etc probably got more grunt
(starter would be better but its very limited)
you should also run this W7 checker tool
http://www.microsoft.com/en-gb/download/details.aspx?id=20

Roy

 

[loninappleton]

Today I got sysprep to complete properly after getting through an error it was giving.
It did the routine, shut down the way it's supposed to. I put the disk on the
Biostar old board. It's like it _wants_ to do it but stops and reboots.

Could it be that that it's looking for something besides a SATA HD and can't find it?

I know earlier someone mentioned something about AHCI but can the
HD itself be a problem in this routine? It's hard to imagine. But the routine
begins to start the Win7 Throbber and then reboots.

As an observation, it's not running that setup black and white screen as
the Sysprep is supposed to do.


Before doing anything more with this particular scratch disk I'll await any replies.

The point is I think it's ready to go but has some peculiar stop point.

Blue screens that have popped up during this practice show a stop at 'drivers'
and hangs when looking at safe mode. But this Sysprep does not get far enough to run Safe.

 

[loninappleton]

This one will hang as unsolved. With the HD that successfully ran Sysprep to it's conclusion at a
machine shut down, I moved it to my other fully working system-- not the old one
I was trying to rejuvenate for a backup. That Sysprepped HD would not run the Setup
with the Installer disk in the DVD drive.

I'd ask again if anyone has actually seen this work and _if_ the motherboards have to
be similar as some Sysprep text has said? For me it was a no go.

 

[loninappleton]

Giving sysprep another whirl I had one question:

I have a successful sysprep shut down for the move to an MSI (newer) motherboard
this time to avoid any old board problems I might have missed previously.

The question is: Since Setup runs, does the System Setup disk need to be in the
dvd drive? It has to look for it's install items yes?

The MSI motherboard suite of drivers disk would then be run if I understand it correctly.

 

[loninappleton]

solved with this info

I will mark this solved when I reconnect and reboot to test.

What got past the errors was the helpful guide at this site:

Windows Clients - Its all about Microsoft Windows Client, Servers and much more

Follow the steps shown before running sysprep.

You will have to make your network connections and do some screen setup. Inspect your program
files and data files since you will have made a new user to initiate the procedure.
Sharma says you can revert to the original user afterward. That is another thing for me to test.

 

[loninappleton]

errors found at reboot

I had detached and replugged the sysprepped disk to test.
Bootmgr was the first error I saw--

MSI motherboard boot manager not found.

It requested a system image backup which I did not have. Starting over might cure this but
I'm not much aware of how the system image is made-- something else to do.

Then another restart attempt gave an error screen called:


Windows Boot Manager saying

File \Boot\BCD

I have not done a wider search on this error message yet. But I'm here to ask
Sevenforums: Can this error be fixed by running the Repair disk in cmd mode for the
"Fix boot" routines?

I don't know if I can get to the MSI motherboard disk yet. That would normally run
after the Win7 is installed. Using it within Win7 did not load any of that at all.\\



An error occurred while attempting to read the boot configuration data file

 

[loninappleton]

Hi Ion,
just for arguements sake, why sysprep??

use the clean install option, as long as the motherboard supports W7, use the iso and away you go.
(if its that old use the 32bit OS)

Roy

I'm re-reading this thread. The answer is that from my experience anything you do to install takes all your data: XP had a repair routine that worked if you were careful. I had used that
many times. With the clean install you suggest I don't know that the famous 'all data will lost'\warning shows up.

Does anyone know if subsequent versions of Windows has actually made a usable repairr tool similar to XP ( not Win7)?

Just now I am gathering info from Microsoft and Sevenforums to correct the bootmgr
not found and assciated errors.

 

[loninappleton]

Boot manager not found is an error that I'm getting _the second_ time I attached the
sysprepped drive to that same MSI motherboard. What would cause this failure after the OS
had successfully booted (though at a different base resolution)?

If I had thought to run MSI system disk on the first bootup it might have fixed something.

Now I am going to Microsoft to find the hard to understand routines to find where BCD is.
The HD is minimally and siply configured. I don't know if a new thread is needed but I'll
continue here for anyone interested. If I can get through it, it will be a lesson well-kept\for the
future.

Still don't know why this is needed and not encountered and solved earlier.

 

[loninappleton]

I took the solved mark off of this.

Very confused. After all went well at first boot up to the new motherboard I removed it
to storage as a test HD. Today I intended to run the MSI motherboard system disk to update the drivers.

The sysprepped disk completely failed to load: a black screen, not even a blue one: dead.

I'm running the Partition Wizard cd to learn of any MBR problems. It's a big disappointment and I don't know a cure for it.

But I'm glad there's an 'unsolved' button on here so people aren't caught in a bind without the new info.

 

[loninappleton]

I'm back.
I retraced my steps and realized I had made some small changes in the MSI BIOS.
I went to BIOS and asked for FailSafe Default settings.

That got this sysprepped disk going as I has seen before.

Will leave this unsolved yet for any other shake-ups.

 

[loninappleton]

Continuing,

I ran the MSI motherboard setup disk yesterday. Next will try a cold boot again.

 

[loninappleton]

My last note on this. On that test disk I tried the routine for MBR refresh using Partition magic as described in a tutorial. I repeated some small changes in BIOS.

Leaving the BIOS at Fail Safe Default setting was necessary to get a good boot again.

That should satisfy any remaining questions.