Macrium Reflect Free offline installer

On 03/12/2018 10:31 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
[]
That's odd Paul, I am running Macrium reflect Version 7.1.2917 sitting
open on the desktop at Idle and it is using 0% on all 3 items in task
manager. The only thing using CPU cycles is Task manager, Less than 1%.

Rene


Presumably if it's listed at all in task manager (let alone three
times!), it must be using _some_ cycles, even if negligible.

Listed in processes

Macrium Reflect Disk Imaging and Backup 0%
Macrium Reflect UI Watcher 0%
Macrium Reflect Utility Service 0%

With Macrium running on the desktop idling.

Rene

In message , Rene Lamontagne
writes:
On 03/12/2018 10:31 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
[]
That's odd Paul, I am running Macrium reflect Version 7.1.2917
sitting open on the desktop at Idle and it is using 0% on all 3
items in task manager. The only thing using CPU cycles is Task
manager, Less than 1%.

Rene


Presumably if it's listed at all in task manager (let alone three
times!), it must be using _some_ cycles, even if negligible.

Listed in processes

Macrium Reflect Disk Imaging and Backup 0%
Macrium Reflect UI Watcher 0%
Macrium Reflect Utility Service 0%

With Macrium running on the desktop idling.

Rene

I saw the 0% the first time you said it! But, presumably, for them to
appear in Task Manager _at all_, they (all three of them) must be using
_some_ cycles - even if it's one a fortnight. Or some memory. If they
weren't, they wouldn't be listed. (Task Manager rounds to nearest %, and
I think K, so will show 0.)

Whether that actually _matters_, is another matter (-:
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

As individuals, politicians are usually quite charming, so it is quite hard to
dislike them, but in most cases, it is worth making the effort.
- Mark Williams (UMRA), 2013-4-26

On Mon, 12 Mar 2018 14:47:10 +0100, FredW wrote:

On Mon, 12 Mar 2018 08:26:37 +0000, PeterC
wrote:
On Sun, 11 Mar 2018 23:03:46 -0400, Paul wrote:

When I tested version 7, I was seeing too much CPU usage
from the Macrium service that is running. It uses CPU, even if
you weren't doing backups at the time.

Is there any disadvantage to setting the service to Manual or Disabled?
I use MR just for clones, so a monitoring service is of no use to me.

I have set the service to Manual.
No problems when I start making an image.

Also, does v7 have any benefits over v6?

New in Version 7
https://knowledgebase.macrium.com/di...w+in+Version+7

Release notes V7:
http://updates.macrium.com/reflect/v...ls7.1.2917.htm

At the bottom (Initial Release) you can see the improvements

Ah, thanks for the links.

As I am on Windows 7 and version 6 did all I wanted , I decided to stay
with Version 6 (proven in practice).

Yes, the better can be the enemy of the good.
Or, if it ain't broke...
More importantly, if you can't fix it, don't break it.
--
Peter.
The gods will stay away
whilst religions hold sway

On Mon, 12 Mar 2018 06:15:53 -0400, Paul wrote:

PeterC wrote:
On Sun, 11 Mar 2018 23:03:46 -0400, Paul wrote:

When I tested version 7, I was seeing too much CPU usage
from the Macrium service that is running. It uses CPU, even if
you weren't doing backups at the time.

Is there any disadvantage to setting the service to Manual or Disabled?
I use MR just for clones, so a monitoring service is of no use to me.

Also, does v7 have any benefits over v6?

Well, I'm funny that way. If you write software
that ****es me off, I uninstall it in the blink
of an eye. And that's what happened with V7.
I took one look at Task Manager, and didn't even
have a chance to look for "Features".

A certain printer driver and a webcam driver, got
the same kind of express service here. Burn up my
CPU for nothing, out the door you go :-)

As it is, I occasionally have to switch off Windows Defender
in Windows 10, because it'll cut the performance of
some application in half. If I want to run hashdeep
on a partition, I turn off WD (realtime) first.

Paul

Same here - I've been trying 'portable' s/w, it wants to do something like
chane the Reg. and it's out.
--
Peter.
The gods will stay away
whilst religions hold sway

On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 10:31 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
[]
That's odd Paul, I am running Macrium reflect Version 7.1.2917
sittingÂ* open on the desktop at Idle and it is using 0% on all 3
items in taskÂ* manager. The only thing using CPU cycles is Task
manager, Less than 1%.

Rene


Presumably if it's listed at all in task manager (let alone three
times!), it must be using _some_ cycles, even if negligible.

Listed in processes

Macrium Reflect Disk Imaging and BackupÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 0%
Macrium Reflect UI WatcherÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 0%
Macrium Reflect Utility ServiceÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â* 0%

With Macrium running on the desktop idling.

Rene

I saw the 0% the first time you said it! But, presumably, for them to
appear in Task Manager _at all_, they (all three of them) must be using
_some_ cycles - even if it's one a fortnight. Or some memory. If they
weren't, they wouldn't be listed. (Task Manager rounds to nearest %, and
I think K, so will show 0.)

Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

Rene Lamontagne wrote:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 10:31 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
[]
That's odd Paul, I am running Macrium reflect Version 7.1.2917
sitting open on the desktop at Idle and it is using 0% on all 3
items in task manager. The only thing using CPU cycles is Task
manager, Less than 1%.

Rene


Presumably if it's listed at all in task manager (let alone three
times!), it must be using _some_ cycles, even if negligible.

Listed in processes

Macrium Reflect Disk Imaging and Backup 0%
Macrium Reflect UI Watcher 0%
Macrium Reflect Utility Service 0%

With Macrium running on the desktop idling.

Rene

I saw the 0% the first time you said it! But, presumably, for them to
appear in Task Manager _at all_, they (all three of them) must be
using _some_ cycles - even if it's one a fortnight. Or some memory. If
they weren't, they wouldn't be listed. (Task Manager rounds to nearest
%, and I think K, so will show 0.)

Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

Nothing stops them from fixing it.

But you see, this is how the QA game works.
"You only get one chance to get it right."

Say you go to a restaurant and are served a
bad meal. How many times will you go back and
repeat the experience ?

Paul

On Mon, 12 Mar 2018 06:15:53 -0400, Paul
wrote:

PeterC wrote:
On Sun, 11 Mar 2018 23:03:46 -0400, Paul wrote:

When I tested version 7, I was seeing too much CPU usage
from the Macrium service that is running. It uses CPU, even if
you weren't doing backups at the time.

Is there any disadvantage to setting the service to Manual or Disabled?
I use MR just for clones, so a monitoring service is of no use to me.

Also, does v7 have any benefits over v6?

Well, I'm funny that way. If you write software
that ****es me off, I uninstall it in the blink
of an eye. And that's what happened with V7.
I took one look at Task Manager, and didn't even
have a chance to look for "Features".

There was a problem with Macrium Reflect v7 when running on Windows 10
version 1607.
Windows 10 version 1607 introduced a new registry entry to block
legacy drivers - IoBlockLegacyFsFilters, and this registry entry had
to be explicitly set to exclude legacy drivers from loading. However,
the default value for this new registry entry has been changed from
'0' (Not blocked) to '1' (blocked) in the Insider Preview 17063 build
of Windows 10. This means that that no 'Legacy' kernel drivers,
except for Microsoft's own legacy drivers, are loaded at boot time.

Macrium averted this "problem" in v7.1.2917.

"J. P. Gilliver (John)" wrote:
In message , FredW
writes:
[]
Also, does v7 have any benefits over v6?

New in Version 7
Thanks for these.
https://knowledgebase.macrium.com/di...w+in+Version+7

Seems to be mainly 3 things:
1. Improvement that makes differential/incremental images faster (not
available for XP). No benefit if you don't make differential/incremental
images.
2. (I think) ability to run a certain kind of virtual machine directly
from a Macrium image.
3. Improvement (and bugfix for W10Ann users) to the task scheduler.

Release notes V7:
http://updates.macrium.com/reflect/v...ls7.1.2917.htm

At the bottom (Initial Release) you can see the improvements
Same three, I think.

As I am on Windows 7 and version 6 did all I wanted , I decided to stay
with Version 6 (proven in practice).

Ditto (I don't do scheduled or incremental/differential backups). (I'll
probably stay with 5!)

Same here, but I never got v5 so I have v6.
--
Quote of the Week: "Ants never sleep." --Ralph Waldo Emerson, poet
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org
/ /\ /\ \ Please nuke ANT if replying by e-mail privately. If credit-
| |o o| | ing, then please kindly use Ant nickname and URL/link.
\ _ /
( )

On 03/12/2018 2:18 PM, Paul wrote:
Rene Lamontagne wrote:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 10:31 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
[]
That's odd Paul, I am running Macrium reflect Version 7.1.2917
sittingÂ* open on the desktop at Idle and it is using 0% on all 3
items in taskÂ* manager. The only thing using CPU cycles is Task
manager, Less than 1%.

Rene


Presumably if it's listed at all in task manager (let alone three
times!), it must be using _some_ cycles, even if negligible.

Listed in processes

Macrium Reflect Disk Imaging and BackupÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 0%
Macrium Reflect UI WatcherÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 0%
Macrium Reflect Utility ServiceÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â* 0%

With Macrium running on the desktop idling.

Rene

I saw the 0% the first time you said it! But, presumably, for them to
appear in Task Manager _at all_, they (all three of them) must be
using _some_ cycles - even if it's one a fortnight. Or some memory.
If they weren't, they wouldn't be listed. (Task Manager rounds to
nearest %, and I think K, so will show 0.)

Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

Nothing stops them from fixing it.

But you see, this is how the QA game works.
"You only get one chance to get it right."

Say you go to a restaurant and are served a
bad meal. How many times will you go back and
repeat the experience ?

Â*Â* Paul

I agree with that, I have tossed many pieces of software because they
were poorly tested and put on the market.
But in this case 7.1 is working fine on my system and so was 6.3, so I
continue with it unless it proves unsatisfactory.

Rene

In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
I saw the 0% the first time you said it! But, presumably, for them
to appear in Task Manager _at all_, they (all three of them) must be
using _some_ cycles - even if it's one a fortnight. Or some memory.
If they weren't, they wouldn't be listed. (Task Manager rounds to
nearest %, and I think K, so will show 0.)
Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

_____
___ |[]|_n_n_I_c
|___||__|###|____)
O-O--O-O+++--O-O

On 03/13/2018 1:16 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
Â*I saw the 0% the first time you said it! But, presumably, for them
toÂ* appear in Task Manager _at all_, they (all three of them) must be
usingÂ* _some_ cycles - even if it's one a fortnight. Or some memory.
If theyÂ* weren't, they wouldn't be listed. (Task Manager rounds to
nearest %, andÂ* I think K, so will show 0.)
Â*Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)

Don't Know, Someone with more knowledge of task manager might know.

Rene

Rene Lamontagne wrote:
On 03/13/2018 1:16 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
I saw the 0% the first time you said it! But, presumably, for them
to appear in Task Manager _at all_, they (all three of them) must
be using _some_ cycles - even if it's one a fortnight. Or some
memory. If they weren't, they wouldn't be listed. (Task Manager
rounds to nearest %, and I think K, so will show 0.)
Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not* using
cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)

Don't Know, Someone with more knowledge of task manager might know.

Rene


When something is railed in Task Manager, you have the
option of studying it in Process Explorer (sysinternals.com).

https://s14.postimg.org/6ba7eypc1/Rpc_Ss_busy_loop.gif

A "svchost" is, as the name implies, a "host for services".
A service "takes requests" and "delivers results". Multiple
services can live inside one SVCHOST.

In older Windows OSes, like WinXP, one of the SVCHOSTs had
15 services in it, and they were all "network oriented".
On Windows 10, by comparison, for reasons unknown, Microsoft
has implemented a "one service one SVCHOST" policy, but, it
didn't do it for everything. The result is, the Task Manager
list in Windows 10 is *huge*, but it's huge for two reasons.
There are more services. The services have been given their
own SVCHOST to hide it.

A well-written service, doesn't use any cycles unless you
"talk to it". Services should not be like proper "processes"
and should be lighter in weight, and also lighter in
intent. They're not like a copy of Excel or Word, and don't
use up nearly the same amount of resources. They don't
put a window on the screen AFAIK.

Think for a moment, of a hypothetical "spooler service".
The user wants to print. The printer isn't ready. What
better way to handle it, then have a queue where the
print can be saved, and dribbled out as the printer
is ready for it. I "call" the spooler service with my
print file, and between the spooler service and some printer
service, they dribble out stuff until it is done. As a program,
I can disconnect from the spooler service, while the spooler
service handles the whole print job for me. It means my program
doesn't "jam" until the entire document is printed. The
program doing the printing, is responsive almost immediately
after the print operation happens. And it's all because a
spooler service could be designed to offload individual
programs, and prevent them from "jamming up".

In the picture above, RpcSs service appears to be
doing garbage collection (recovery of unused RAM) for
the desktop display process (the entire desktop is
some kind of program). It had something to do with
the thing that MSEdge was doing, and MSEdge needed a lot
of RAM to do it, then later, MSEdge gave the RAM back.
That RpcSs service for some reason, seemed to be making
RAM freeing calls for about 20 seconds continuously. Which
smacks of bad design. It's like your mom has left for
a three week vacation, and you decide to do 50 loads of
wash an hour before she arrives back from vacation. And
it's too little too late. That garbage collection should
have been done in much smaller time segments. Not left
until the last minute.

In the old days with Unix, you had daemons. The "inetd"
process was a daemon for dispatching things. One of the
things reporting to it was "telnetd", a telnet support
daemon. If the user telnetted remotely to the
computer with an 80x24 terminal, inetd would see the
activity on some control port, and would wake telnetd up
to respond to the login attempt and session. The concept
of services has existed with other names for it, for
some time.

For me, the worst part of the Windows scheme, is it's
so hard to use debugging tools to compare "inside" and
"outside" activities. Some of the tools I use would tell
me "svchost 1156 is doing something", but then I couldn't
peer inside to see any details. And that sucks. I like it
when each service has a unique name (i.e. viewable at the
Task Manager level), and just the name alone hints at what
job it's doing, and why it might be railed.

Paul

On 03/13/2018 10:20 AM, Paul wrote:
Rene Lamontagne wrote:
On 03/13/2018 1:16 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
Â*I saw the 0% the first time you said it! But, presumably, for them
toÂ* appear in Task Manager _at all_, they (all three of them) must
be usingÂ* _some_ cycles - even if it's one a fortnight. Or some
memory. If theyÂ* weren't, they wouldn't be listed. (Task Manager
rounds to nearest %, andÂ* I think K, so will show 0.)
Â*Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not*
using cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)

Don't Know, Someone with more knowledge of task manager might know.

Rene


When something is railed in Task Manager, you have the
option of studying it in Process Explorer (sysinternals.com).

https://s14.postimg.org/6ba7eypc1/Rpc_Ss_busy_loop.gif

A "svchost" is, as the name implies, a "host for services".
A service "takes requests" and "delivers results". Multiple
services can live inside one SVCHOST.

In older Windows OSes, like WinXP, one of the SVCHOSTs had
15 services in it, and they were all "network oriented".
On Windows 10, by comparison, for reasons unknown, Microsoft
has implemented a "one service one SVCHOST" policy, but, it
didn't do it for everything. The result is, the Task Manager
list in Windows 10 is *huge*, but it's huge for two reasons.
There are more services. The services have been given their
own SVCHOST to hide it.

A well-written service, doesn't use any cycles unless you
"talk to it". Services should not be like proper "processes"
and should be lighter in weight, and also lighter in
intent. They're not like a copy of Excel or Word, and don't
use up nearly the same amount of resources. They don't
put a window on the screen AFAIK.

Think for a moment, of a hypothetical "spooler service".
The user wants to print. The printer isn't ready. What
better way to handle it, then have a queue where the
print can be saved, and dribbled out as the printer
is ready for it. I "call" the spooler service with my
print file, and between the spooler service and some printer
service, they dribble out stuff until it is done. As a program,
I can disconnect from the spooler service, while the spooler
service handles the whole print job for me. It means my program
doesn't "jam" until the entire document is printed. The
program doing the printing, is responsive almost immediately
after the print operation happens. And it's all because a
spooler service could be designed to offload individual
programs, and prevent them from "jamming up".

In the picture above, RpcSs service appears to be
doing garbage collection (recovery of unused RAM) for
the desktop display process (the entire desktop is
some kind of program). It had something to do with
the thing that MSEdge was doing, and MSEdge needed a lot
of RAM to do it, then later, MSEdge gave the RAM back.
That RpcSs service for some reason, seemed to be making
RAM freeing calls for about 20 seconds continuously. Which
smacks of bad design. It's like your mom has left for
a three week vacation, and you decide to do 50 loads of
wash an hour before she arrives back from vacation. And
it's too little too late. That garbage collection should
have been done in much smaller time segments. Not left
until the last minute.

In the old days with Unix, you had daemons. The "inetd"
process was a daemon for dispatching things. One of the
things reporting to it was "telnetd", a telnet support
daemon. If the user telnetted remotely to the
computer with an 80x24 terminal, inetd would see the
activity on some control port, and would wake telnetd up
to respond to the login attempt and session. The concept
of services has existed with other names for it, for
some time.

For me, the worst part of the Windows scheme, is it's
so hard to use debugging tools to compare "inside" and
"outside" activities. Some of the tools I use would tell
me "svchost 1156 is doing something", but then I couldn't
peer inside to see any details. And that sucks. I like it
when each service has a unique name (i.e. viewable at the
Task Manager level), and just the name alone hints at what
job it's doing, and why it might be railed.

Â*Â* Paul

Thanks Paul, Task manager is so complicated that I cannot follow what
all it does.
It seems to work (most of the time) so I just let it do what it does.
I just did a backup using Macrium and this is some info I gathered.

The CPU speed varied between 2.6 GHz to 3.06 GHz.
CPU load ran from 11% to 16.5%.
6 cores seemed to be the most active, 2 cores were not used as much.
just as an aside I have 168 items listed under processes.

Rene

In message , Paul
writes:
Rene Lamontagne wrote:
On 03/13/2018 1:16 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
I saw the 0% the first time you said it! But, presumably, for
them to appear in Task Manager _at all_, they (all three of them)
must be using _some_ cycles - even if it's one a fortnight. Or
some memory. If they weren't, they wouldn't be listed. (Task
Manager rounds to nearest %, and I think K, so will show 0.)
Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not*
using cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)
Don't Know, Someone with more knowledge of task manager might know.
Rene


When something is railed in Task Manager, you have the
[]
Nothing is railed; on the contrary, Rene is saying that these three (!)
Macrium processes are using 0% (which I'm saying means they're using
less than 1%, probably less than half a percent, depending whether it
rounds or truncates). I was just saying that, if they appear in the list
at all, they must be using _some_ resources - though probably not a
significant amount.

(FWIW, I have 94 processes showing, _all_ but the System Idle Process
_showing_ as 0%. In fact the total usage figure at the bottom is
bouncing around between mostly 2 and 7% - and while I've been typing
this paragraph, I've even seen it show 1 and 0%, though also 9. [And
that's with both Firefox26 and Chrome open, each with lots of tabs!
_Memory_ is showing as 70%, which I expect _is_ those two mostly.])
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Veni Vidi Vacuum [I came, I saw, It sucked] - , 1998

J. P. Gilliver (John) wrote:
In message , Paul
writes:
Rene Lamontagne wrote:
On 03/13/2018 1:16 AM, J. P. Gilliver (John) wrote:
In message , Rene Lamontagne
writes:
On 03/12/2018 11:32 AM, J. P. Gilliver (John) wrote:
[]
I saw the 0% the first time you said it! But, presumably, for
them to appear in Task Manager _at all_, they (all three of
them) must be using _some_ cycles - even if it's one a
fortnight. Or some memory. If they weren't, they wouldn't be
listed. (Task Manager rounds to nearest %, and I think K, so
will show 0.)
Whether that actually _matters_, is another matter (-:

There are dozens of items listed in task manager that are *Not*
using cyles at all, so your presumptions would be incorrect.

Rene

{How did they get into}/{Why are they still in} the list of items in
Task Manager, then? (Not just the Macrium ones, but all the other
"dozens".)
Don't Know, Someone with more knowledge of task manager might know.
Rene


When something is railed in Task Manager, you have the
[]
Nothing is railed; on the contrary, Rene is saying that these three (!)
Macrium processes are using 0% (which I'm saying means they're using
less than 1%, probably less than half a percent, depending whether it
rounds or truncates). I was just saying that, if they appear in the list
at all, they must be using _some_ resources - though probably not a
significant amount.

(FWIW, I have 94 processes showing, _all_ but the System Idle Process
_showing_ as 0%. In fact the total usage figure at the bottom is
bouncing around between mostly 2 and 7% - and while I've been typing
this paragraph, I've even seen it show 1 and 0%, though also 9. [And
that's with both Firefox26 and Chrome open, each with lots of tabs!
_Memory_ is showing as 70%, which I expect _is_ those two mostly.])

The version of Macrium 7 I tested, there was a service that was
using cycles when Macrium wasn't running. That's verboten at
my house... It's like if some yutz decides to run a coin
miner on a web page - how long do you think I'm going to
stay on that web page ? About a microsecond :-)

I don't have a reason to keep testing Version 7, when I
have copies of 6.3 on the computers running just fine.

If this was a program for which I had no working copy,
I might put more effort into it. But as it is, there's
really no incentive for me personally, to be pursuing 7.

It's good that other people are still testing it
and have noted an improvement.

The Macrium staff seem to be pretty good at what they
do. They're better than Acronis. It isn't often that
you catch the Macrium people on an off-day.

Task Manager shows processes. Process Explorer can show
some information for Threads. A process can have hundreds
of threads inside. I don't know if Microsoft keeps a nice
web page with a taxonomy or not. It would be handy if
they did. I could use a refresher.

Paul