A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Macrium Reflect Question



 
 
Thread Tools Rate Thread Display Modes
  #31  
Old January 7th 19, 02:09 AM posted to alt.windows7.general
Bill in Co[_3_]
external usenet poster
 
Posts: 266
Default Macrium Reflect Question

Char Jackson wrote:
On Sun, 6 Jan 2019 17:12:56 -0500, Zaidy036 wrote:

As I understand you have one HDD with partitions C and D and are
therefor making an image back onto the HDD you are imaging.

That has to be confusing for any imaging program and is probably why you
are having the C/D problem on restore.


If he's imaging C: and storing it on D:, it doesn't matter in the
slightest that C: and D: are two partitions on the same physical disk.
No imaging program is going to have a problem with that.

--

Char Jackson


Right. The problem, as noted by Paul, is that the ramdisk boots up as C: ,
effectively "stealing" that drive letter away from me for a flawless restore
operation to my C: (it thinks my system drive is now D: during the restore
operation, and that E has the backup image, (instead of D. But it worked,
however, but with some minor issues, which I can't recall now.

I rarely use that Windows 7 laptop at this point, so it hasn't been a big
issue for me. I'm using the Windows XP desktop computer almost all the
time, including right here.


Ads
  #32  
Old January 7th 19, 06:56 AM posted to alt.windows7.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,531
Default Macrium Reflect Question

In message , Paul
writes:
J. P. Gilliver (John) wrote:
In message , Paul
writes:
[]
Whereas Macrium dispensed with their build-in Linux ISO
around Version 4 or 5 or so, and only uses WinPE style for the
later ones.

Paul

FWIW: When I was making my Macrium 5 CDs, I'm pretty sure I had a
choice between a WinPE and something Linuxy, so the _choice_ was
still there up to at least 5. I think the guidance rather implied
that the Linuxy one was somewhat more spartan, but would still have
done the job - it was certainly smaller; I chose the Windowsy one
because I'm more familiar with it, and it would still fit on a CD
(even, as I found out, a mini-one).


I thought at the time, that when the Linux Rescue.iso was removed,
there was a big saving. But between 7149x64 and 909x64 it's only
9,000,000 or so. Linux is gone in Macrium6, by searching inside
with 7ZIP for the ISO. Macrium 7 seemed to put on a fair bit
of weight.

v5.3.7149_reflect_setup_free_x64.exe\ISOFiles.cab \ download=51,693,008
bytes \
Rescue.iso 20,375,552 \
/
v6.1.909_reflect_setup_free_x64.exe download=42,288,592 bytes /
v6.1.1225_reflect_setup_free_x64.exe download=42,833,920 bytes
v6.3.1849_reflect_setup_free_x64.exe download=46,645,904 bytes
v7.1.2963_reflect_setup_free_x64.exe download=65,792,600 bytes
v7.1.3317_reflect_setup_free_x64.exe download=65,875,720 bytes

Paul


Interesting. From your statements above, I infer that the single
download file includes the .iso required to make the CD (or even two
such ISOs in the case of v5). Presumably compressed, as my v5 CD IIRR
occupies most of the space on my mini-CD, i. e. about 200M.

Yes, I remember the process of making the CD as relatively painless, as
would indeed be the case if what you had downloaded included all you
needed. I've been slightly puzzled since by discussions about you having
to choose - and by implication download extra - which versions of WinPE
(PE4, PE5, PE10?) are needed to make a CD.

For interest, here (courtesy of Everything with "reflect_" as the search
string) are the 32-bit ones I have stored (I must have had at some point
a 64-bit v5 as well, sine I have two CDs [though I'm unaware of any
noticeable advantage to the 64- one, but presumably there must be
something!]):
on my D:
downloaded 2014-9-28:
v5.3.7170_reflect_setup_free_x86.eze 49,926,608 bytes
downloaded 2018-3-11 (I think well after it was issued):
v6.3.1852_reflect_setup_free_x86.exe 44,303,520 bytes
I also find that I have, in my C:\Windows\Installer:
reflect_setupv5.3.7170-x86-00.msi 48,521,216 bytes dated
2018-12-7, which is interesting: I don't think I've ever installed any
Macrium on this machine, and would certainly never have put anything
there (I didn't know of the _existence_ of C:\Windows\Installer until
now; I rarely manually write to C: at all). I did however make (onto
eternal drive) an image of C: and the hidden partition in early
December, using one of the CDs (the 64-bit one) I had made on my XP
machine, so that's presumably when the .msi file appeared.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf

There's too much attention paid to how TV can be bad for you, but I think it's
good for us more often than it's bad - Professor Barrie Gunter of Sheffield
University (quoted in RT, 15-21 March 2003).
  #33  
Old January 7th 19, 02:18 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 8,733
Default Macrium Reflect Question

J. P. Gilliver (John) wrote:
In message , Paul
writes:
J. P. Gilliver (John) wrote:
In message , Paul
writes:
[]
Whereas Macrium dispensed with their build-in Linux ISO
around Version 4 or 5 or so, and only uses WinPE style for the
later ones.

Paul
FWIW: When I was making my Macrium 5 CDs, I'm pretty sure I had a
choice between a WinPE and something Linuxy, so the _choice_ was
still there up to at least 5. I think the guidance rather implied
that the Linuxy one was somewhat more spartan, but would still have
done the job - it was certainly smaller; I chose the Windowsy one
because I'm more familiar with it, and it would still fit on a CD
(even, as I found out, a mini-one).


I thought at the time, that when the Linux Rescue.iso was removed,
there was a big saving. But between 7149x64 and 909x64 it's only
9,000,000 or so. Linux is gone in Macrium6, by searching inside
with 7ZIP for the ISO. Macrium 7 seemed to put on a fair bit
of weight.

v5.3.7149_reflect_setup_free_x64.exe\ISOFiles.cab\ download=51,693,008
bytes \
Rescue.iso 20,375,552 \
/
v6.1.909_reflect_setup_free_x64.exe download=42,288,592 bytes /
v6.1.1225_reflect_setup_free_x64.exe download=42,833,920 bytes
v6.3.1849_reflect_setup_free_x64.exe download=46,645,904 bytes
v7.1.2963_reflect_setup_free_x64.exe download=65,792,600 bytes
v7.1.3317_reflect_setup_free_x64.exe download=65,875,720 bytes

Paul


Interesting. From your statements above, I infer that the single
download file includes the .iso required to make the CD (or even two
such ISOs in the case of v5). Presumably compressed, as my v5 CD IIRR
occupies most of the space on my mini-CD, i. e. about 200M.

Yes, I remember the process of making the CD as relatively painless, as
would indeed be the case if what you had downloaded included all you
needed. I've been slightly puzzled since by discussions about you having
to choose - and by implication download extra - which versions of WinPE
(PE4, PE5, PE10?) are needed to make a CD.

For interest, here (courtesy of Everything with "reflect_" as the search
string) are the 32-bit ones I have stored (I must have had at some point
a 64-bit v5 as well, sine I have two CDs [though I'm unaware of any
noticeable advantage to the 64- one, but presumably there must be
something!]):
on my D:
downloaded 2014-9-28:
v5.3.7170_reflect_setup_free_x86.eze 49,926,608 bytes
downloaded 2018-3-11 (I think well after it was issued):
v6.3.1852_reflect_setup_free_x86.exe 44,303,520 bytes
I also find that I have, in my C:\Windows\Installer:
reflect_setupv5.3.7170-x86-00.msi 48,521,216 bytes dated
2018-12-7, which is interesting: I don't think I've ever installed any
Macrium on this machine, and would certainly never have put anything
there (I didn't know of the _existence_ of C:\Windows\Installer until
now; I rarely manually write to C: at all). I did however make (onto
eternal drive) an image of C: and the hidden partition in early
December, using one of the CDs (the 64-bit one) I had made on my XP
machine, so that's presumably when the .msi file appeared.


When software installs, the MSI can be cached.

If you go to Add/Remove (WinXP) or Programs and features (Win7),
you may be offered a Repair option, and the cached MSI comes
in handy for that.

The Linux ISO (rescue.iso) is part of the 40-50MB main download
for Reflect.

The WinPE ISO requires downloading additional materials, part
of the WAIK or WADK kit.

https://en.wikipedia.org/wiki/Window...Deployment_Kit

On first installation, the Reflect Stub installer can download
two apparent files. The main installer is 40MB. The WADK is actually
downloaded as a dozen files or so. First a manifest is fetched
from the Macrium site, then a dozen files are downloaded from MS. These
are compressed into a ZIP file for a rainy day. The ZIP can
be uncompressed, when it is desired to make a 300MB WinPE
rescue CD.

Macrium supports as many as four different WinPE versions,
and will download the materials needed on demand. However,
not all WAIK/WADK kits work on all OSes. There is a table
of what works somewhere.

The Linux ISO is initrd based and the image is a lot smaller.
Only 20MB of surface need be burnt on your CD.

Both cases can be analyzed with the services of 7ZIP.

The Macrium rescue disc procedures resist meddling,
so it's not really possible to have a positive influence
by trying to repair what it's doing by hand. I learned
some of that, trying to get WinPE4 working in WinXP recently.
It appears Microsoft has removed the components for download,
to make one of those. So the Macrium manifest file now
doesn't point to the stuff it should point to. You can try
making a later version of WinPE materials, using a Win7 or
Win10 PC, then testing whether the rescue disc works
on your WinXP machine. A newer release of Macrium should
be able to restore .mrimg files made with an older
version.

At some point, the entire universe will be 64 bit, and
there won't be sufficient materials to make 32-bit
machines happy any more. 32-bit-only machines today
are circling the gurgler.

Paul
  #34  
Old January 7th 19, 02:21 PM posted to alt.windows7.general
David B.[_10_]
external usenet poster
 
Posts: 286
Default Macrium Reflect Question

On 07/01/2019 01:09, Bill in Co wrote:
I rarely use that Windows 7 laptop at this point, so it hasn't been a big
issue for me. I'm using the Windows XP desktop computer almost all the
time, including right here.


FYI

Updates are cumulative(and have been for some time) for Windows 7, thus
January's update(and each month thereafter) will include December's(and
subsequent month) patches.

While one can hide updates on Win7, the more prevalent issue is Win7 has
about 1 yr of entire life support left. Anyone running Win7 should have
a plan to replace the device. Also of note, application software from
other companies will also cease support for Windows 7, some even prior
to MSFT Win7 end-of-life/support.

Plan ahead, MSFT is already on record that consumer's will not see an
extension of Win7 support after Jan 20, 2020.
- i.e. they won't make the same mistake they did by extending support
for XP.

--
....w¡ñ§±¤ñ
  #35  
Old January 7th 19, 03:38 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 8,733
Default Macrium Reflect Question

David B. wrote:

Anyone running Win7 should have a plan to replace the device.


An abacus perhaps ?

Paul
  #36  
Old January 7th 19, 04:04 PM posted to alt.windows7.general
Ken Blake[_5_]
external usenet poster
 
Posts: 2,122
Default Macrium Reflect Question

On Sun, 06 Jan 2019 18:06:48 -0600, Char Jackson
wrote:

On Sun, 6 Jan 2019 17:12:56 -0500, Zaidy036 wrote:

As I understand you have one HDD with partitions C and D and are
therefor making an image back onto the HDD you are imaging.

That has to be confusing for any imaging program and is probably why you
are having the C/D problem on restore.


If he's imaging C: and storing it on D:, it doesn't matter in the
slightest that C: and D: are two partitions on the same physical disk.
No imaging program is going to have a problem with that.




Right. Hardly any program, imaging or not, would even know they are
two partitions on the same physical disk.


 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 01:23 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Copyright 2004-2019 PCbanter.
The comments are property of their posters.