New
#1511
In my view that is an exceptionally dangerous assumption.
A 32 bit application can run on a 64 bit Windows 7 system.
A 32 bit WinPE can be loaded into 64 bit wide RAM and restore an image read from a USB serial external drive to restore through a SATA or IDE interface to your internal drive.
A 64 bit application uses 64 bit wide RAM and uses 64 bit wide instruction codes to can reach beyond the addressing limits of a 32 bit system.
64 bit WinPE needs only a few hundred MB of RAM to execute,
but has the capability of addressing more than 4 GB of RAM.
It is more than probable that when Macrium runs on a full blown live 64 bit Windows system it will use 64 bit wide instruction codes,
and when Macrium creates WinPE it is unlikely to restrict itself to 32 bit wide instruction codes,
and your 64 bit WinPE CD will be unable to load 64 bit instructions into a 32 bit wide RAM.
What is safe to assume is that a 32 bit WinPE will successfully restore an image to a 64 bit system.
I have actually used an old WinPE created under 32 bit XP to restore 64 bit Windows 7 images.
Last edited by alan10; 05 Feb 2014 at 06:21.
Actually there is no single hash checksum - there are thousands of them.
I think the checksums are computed and embedded in the file every ? MBYte
(Macrium have published the interval but I cannot remember).
It is VERY WISE when restoring to select the image file and NOT restore until you verify.
Your image file might be corrupted and it would be sad to have the restore operation first erase C:\ and then restore the first half of your Windows and then abort, leaving you with an UN-bootable system.
N.B.
If a backup is corrupted and you really want to restore regardless of corruption,
there is a simple registry fix to disregard errors,
and perhaps you could create a WinPE CD that would restore a corrupted image.
I truly hope to never be in that position.
Regards
Alan
Thank you for all the comments, it seems I'm doing things right. :)
There's a thing though - since I used Reflect I have WmiPrvSE.exe running in the background all the time. I never had that before. I googled it and it says it's a process that's used in the enterprise environment - but I am a home user. What's that about? Can I disable it?
Right click on it and see whether the path is C:\Windows\System32\wbem - if yes, then it is OK and legit.
The path is right and the file is legit, I tested it at VirusTotal. The thing is it wasn't running before I used Macrium. So do I have to have this process running all the time to use Macrium once a month?
No idea - and it is not really 'running'. It is just sitting there doing no harm. Why would you want to muck around with it.
When you eliminate it, the best that can happen is that you save a few bytes in RAM - the worst that can happen is that you brick your system.
That is about in-line with the times I am seeing => 7.4 min for 38.4GB. But we have our systems on SSDs. That may make a difference.