Solved Image your system with free Macrium

[Dick Jagger]

Without the 100MB active system partition, it will not boot. Check first on the system from where the image came whether that 100MB partition exists. Then make 2 seperat images of that and of C: (you can use the one you have).

On the new system you will first have to define those 2 partitions before you can rstore them. The 100MB partition is the active partition.

But that is not the end of your troubles. The whole project will probably die in the drivers and the Win7 product activation. What I suggest is to install Windows 8 Consumer Preview on the old XP system. Then you have a clean slate.

Thanks - on my current win7 system, there is a 100mb system partition set as active and two primary drives, of about 250gb each.

so first, I need to make an image of the system partition, then restore that to the old xp box? How or where to restore it to?

 

[whs]

To get it on the XP system is no big deal. To make it work, is another matter. Do you in fact have an extra Win7 product key to make it work on another system?? If not, I would stop right here.

 

[Dick Jagger]

I ended up just doing a new install and now trying to copy files and replicate settings. Thanks for the help.

 

[TanyaC]

Macrium Free: Create custom WinPE with added drivers

Hi,

I recently imaged my system with Macrium, and I got the missing drivers errors. I had my mobo cd handy and could load the drivers. Surprisingly, Macrium was missing the RTL8111 LAN driver.

Anyway, I integrated the drivers from my mobo into the .wim file per the knowledgebase article, but silly me, I didn't create a new rescue disk. So when I went to use the disk, it of course complained of missing drivers.

So I went to create a new WinPE, but I'm not sure how to proceed when I'm asked for the .wim file. The default one that is checked is the one dated 2009 (winPE.wim). The one I integrated my drivers into is called boot.wim, and is 14mb larger (for 2 drivers??)

Anyway, I note that Macrium do not allow users of the free version access to any support whatsoever, nor do they allow access to the forums (The latter is quite disappointing). So I'm hoping that some expertise exists here...

Can anyone clarify if I should use the boot.wim, or do I have to stick with the WinPE.wim installed with the software?

thanks
Tanya

ooops.. I meant to post this as a new thread. My mistake, sorry.

 

[mjf]

You can integrate your driver using the DISM command to the base winpe.wim then use the "custom" winpe.wim option in Macrium (free). If you have selected the option to always include new drivers manually after boot then that would work also.

 

[jimbo45]

Hi there
I know this is W7 but some of you are probably trying out the new W8 consumer preview.
Hope I'll save you some time here ==:

This doesn't work on it !!! (yet).

IMO if you want a FREEBIE that is reliable -- takes a bit of a learning curve but works in W7 and W8

1: get the imageex.exe from the WAIK (same program from W7 WAIK can be used on W8 too).

2: Create an install.WIM file of your running system system

3: Image it.

4: extract it when you want to restore your image.

Commands are a bit fiddly but works every time. Google a bit as the explanation is a bit complex for this type of thread.


For Windows 8 there is a built in utility for restoring an image called recimg.

http://www.eightforums.com/installa...ng-your-own-data-etc-no-need-acronis-etc.html

For W7 the utility doesn't exist but you can still restore a .WIM file

read through this link -- should help to further searches for you.

http://systemmanagement.ro/blog/2009/12/21/how-to-create-a-windows-image-wim-file/

On W7 I have acronis -- which also works on W8 --but if you have a few machines paying 45 USD per machine gets expensive so on W8 I'm using the "Freebie".

Cheers
jimbo

 

[kado897]

I can confirm that it doesn't work on win 8. See this thread. Macrium Reflect Free BSODS - Windows 8 Forums

 

[essenbe]

You can also use Hiren's Boot SD, download the ISO file and burn it to CD/USB drive boot into mini XP. One of the many programs on there is the linux version pf Macrium rescue.

 

[kado897]

You can also use Hiren's Boot SD, download the ISO file and burn it to CD/USB drive boot into mini XP. One of the many programs on there is the linux version pf Macrium rescue.

It is actually an old PE version(4.2 I think) but it still works even with images created by v5.

 

[SIW2]

@Jimbo - have you only just realised this?

Wim imaging has been around for a few years. It is not intended as a backup mechanism - it is possible to use it that way - but it is not practical.

Yes , In am aware of recimg on win8 ( it is not for a complete restore btw - your data is not included ). It is nowhere near as good as a 3rd party app.

Free ( or paid ) 3rd party apps. specially made for the job are much better.




@ Kado - can you elaborate on macrium bsod on win8 ?

How and when did that happen?

 

[lehnerus2000]

Another reason to avoid W8

I can confirm that it doesn't work on win 8. See this thread. Macrium Reflect Free BSODS - Windows 8 Forums

Sounds like another reason to avoid W8.

 

[kado897]

@SIW2

If you look at the thread I posted it explains it. After the image I rebooted and got page fault in a non paged area. I thought originally it might have been due to using a VM but as you can see I am not the only one with this.

 

[alan10]

You can also use Hiren's Boot SD, download the ISO file and burn it to CD/USB drive boot into mini XP. One of the many programs on there is the linux version pf Macrium rescue.

It is actually an old PE version(4.2 I think) but it still works even with images created by v5.

I understood the Linux version does NOT include Win PE,
and is not amenable to incorporating requisite drivers,
you get what you get ready made for "standard" hardware.
If it fails to boot there is non work-around.

 

[kado897]

@SIW2

If you look at the thread I posted it explains it. After the image I rebooted and got page fault in a non paged area. I thought originally it might have been due to using a VM but as you can see I am not the only one with this.

Mmm! Interesting. I have just retried it in a clean install in VBox rather than my previous install in VMPlayer and it seems to have worked this time.

 

[whs]

If you have problems imaging Win8 with free Macrium, I suggest to use the Macrium WinPE CD/stick. In a double boot, you can also use Macrium from Win7 to image the Win8 partition(s).

 

[kado897]

Actually It is a later version of Macrium and 64bit in VBox as opposed to 32bit in VMPlayer so the comparison is not exact. Incidentally restoring an image works too now.

 

[bruce73]

Trouble creating image

I updated to the latest edition today (4694, dated June 12, 2012) and proceeded to make my regular image to an internal SATA drive (Seagate). At the 1 min/20 sec to go mark, the program stopped responding. When I moved the mouse my Win 7/64 system threw up a BSOD ("Kernal Data Inpage Error"). First time I had ever seen this one.

I rebooted into SafeMode and ran CHKDSK on all internal/external drives. Every one came up OK. I rebooted into Windows and tried again. At the *exact* same mark (1 min/20 sec to go), Macrium again became unresponsive. This time no BSOD, but I was unable to close the program. I tried forcing a close with Task Manager, but the screen went black (the mouse pointer was still visible and able to move). Again, I rebooted into SafeMode and ran CHKDSK. Everything OK.

I tried a third time, but chose as a destination drive a different SATA internal (Seagate). This time, the image completed without a problem.

Not sure what's going on. I googled "Kernal Data Inpage Error" and came up with possible RAM issues or a possible failing hard drive. Since the error occurred at the exact same time during the image creation on just that one drive, I'm wondering if it's, in fact, the latter. I ran the short test in SeaTools DOS and came up with nothing, but I'm not sure if that was adequate.

Any ideas?

 

[kado897]

Trouble creating image

I updated to the latest edition today (4694, dated June 12, 2012) and proceeded to make my regular image to an internal SATA drive (Seagate). At the 1 min/20 sec to go mark, the program stopped responding. When I moved the mouse my Win 7/64 system threw up a BSOD ("Kernal Data Inpage Error"). First time I had ever seen this one.

I rebooted into SafeMode and ran CHKDSK on all internal/external drives. Every one came up OK. I rebooted into Windows and tried again. At the *exact* same mark (1 min/20 sec to go), Macrium again became unresponsive. This time no BSOD, but I was unable to close the program. I tried forcing a close with Task Manager, but the screen went black (the mouse pointer was still visible and able to move). Again, I rebooted into SafeMode and ran CHKDSK. Everything OK.

I tried a third time, but chose as a destination drive a different SATA internal (Seagate). This time, the image completed without a problem.

Not sure what's going on. I googled "Kernal Data Inpage Error" and came up with possible RAM issues or a possible failing hard drive. Since the error occurred at the exact same time during the image creation on just that one drive, I'm wondering if it's, in fact, the latter. I ran the short test in SeaTools DOS and came up with nothing, but I'm not sure if that was adequate.

Any ideas?

Hi bruce73. I think you would be better off starting a new thread in the Crashes and Debugging section. One of our BSOD experts will pick it up there.

 

[bruce73]

Good idea, I'll do that. Although, to amend just a bit, I ended up restoring an image from a couple of weeks back as I was having others problems (unexplained 100% CPU usage). I also eliminated some files and defragged the problem disc and ran Macrium again (the previous version). This time it worked. Lots of variables here, I know, but the solid part is that it was the first restore I've done with Macrium and it performed perfectly.

 

[kado897]

That's good to know Bruce. I've never had a Macrium image fail but that doesn't mean that it won't in the future so make sure you have more than one. The problem you have with the BSOD post is that all evidence of it will have been removed by the restore. It may be better to wait until you have another so that you can follow the posting instructions to upload a crash report.