Macrium from running OS ...

Just after posting saying I'd not make an image of a running OS, I am
trying. (I've misplaced my 32-bit Macrium mini-CD, and this old computer
isn't seeing my 64-bit one as a bootable CD.)

So I selected the little recovery partition and drive C, and set it
going. It's been at "Analyzing file system on volume C:" for over 26
minutes now, with no progress being shown.

I'm a _little_ disappointed: assuming it can't image a running OS, I'd
have thought it would have said so, rather than just sitting there for
ever. I've just hit Cancel, said Yes I do want to ... and the window's
not gone away (just Cancel and Pause are now greyed).
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Of course, this show - like every other cop show on earth - massively
overstates the prevalence of violent crime: last year, in the whole of the UK,
police fired their weapons just three times. And there were precisely zero
fatalities. - Vincent Graff in RT, 2014/11/8-14

J. P. Gilliver (John) wrote:
Just after posting saying I'd not make an image of a running OS, I am
trying. (I've misplaced my 32-bit Macrium mini-CD, and this old computer
isn't seeing my 64-bit one as a bootable CD.)

So I selected the little recovery partition and drive C, and set it
going. It's been at "Analyzing file system on volume C:" for over 26
minutes now, with no progress being shown.

I'm a _little_ disappointed: assuming it can't image a running OS, I'd
have thought it would have said so, rather than just sitting there for
ever. I've just hit Cancel, said Yes I do want to ... and the window's
not gone away (just Cancel and Pause are now greyed).

Is the drive physically fit ? Any "bad spots" ?
That'll increase the analysis time.

Also, have a look at the status of your AV.
Did you disable "real time scanning" ?
With the AV disabled, the scan speed could
double.

Third thing is Windows Search Indexer. Check in
Task Manager, and see if it has gone nuts. I have
one OS here, where the damn thing stays railed on
one core, and the file count in the dialog never
increases. And yes, I've reset the build operation
to make it start over again, and when it gets to the
end, it rails again. You have to change the service
policy on the Indexer, while mercilessly hitting the
"Stop" button, to eventually get it to stop it.

Paul

Paul wrote:
J. P. Gilliver (John) wrote:
Just after posting saying I'd not make an image of a running OS, I am
trying. (I've misplaced my 32-bit Macrium mini-CD, and this old
computer isn't seeing my 64-bit one as a bootable CD.)

So I selected the little recovery partition and drive C, and set it
going. It's been at "Analyzing file system on volume C:" for over 26
minutes now, with no progress being shown.

I'm a _little_ disappointed: assuming it can't image a running OS, I'd
have thought it would have said so, rather than just sitting there for
ever. I've just hit Cancel, said Yes I do want to ... and the window's
not gone away (just Cancel and Pause are now greyed).

Is the drive physically fit ? Any "bad spots" ?
That'll increase the analysis time.

Also, have a look at the status of your AV.
Did you disable "real time scanning" ?
With the AV disabled, the scan speed could
double.

Third thing is Windows Search Indexer. Check in
Task Manager, and see if it has gone nuts. I have
one OS here, where the damn thing stays railed on
one core, and the file count in the dialog never
increases. And yes, I've reset the build operation
to make it start over again, and when it gets to the
end, it rails again. You have to change the service
policy on the Indexer, while mercilessly hitting the
"Stop" button, to eventually get it to stop it.

Paul

There's a thread here, where it is mentioned that
if you're doing Incremental backup, and the user
area includes a HomeGroup, Windows messes with
file metadata behind the scenes. Which triggers
extra processing time before a tiny Incremental
is spit out. But other than that, it's supposed
to be using info from the $MFT. Now, I know that
characterization is a little simplistic, as there
is "seeking" going on during the analysis phase
on the disk drive, implying it does actually visit
the folders themselves for some reason. If the
method used just the $MFT, it would be as fast
as Everything.exe (2 seconds to index C: ). And it's
slower than that, by a fair amount.

http://www.wilderssecurity.com/threa...o-slow.339884/

Paul

In message , Paul
writes:
J. P. Gilliver (John) wrote:
Just after posting saying I'd not make an image of a running OS, I am
trying. (I've misplaced my 32-bit Macrium mini-CD, and this old
computer isn't seeing my 64-bit one as a bootable CD.)
So I selected the little recovery partition and drive C, and set it
going. It's been at "Analyzing file system on volume C:" for over 26
minutes now, with no progress being shown.
I'm a _little_ disappointed: assuming it can't image a running OS,
I'd have thought it would have said so, rather than just sitting
there for ever. I've just hit Cancel, said Yes I do want to ... and
the window's not gone away (just Cancel and Pause are now greyed).

Is the drive physically fit ? Any "bad spots" ?
That'll increase the analysis time.

I believe so; it's only a couple of years old, and has always SMARTed
happily.

Also, have a look at the status of your AV.
Did you disable "real time scanning" ?
With the AV disabled, the scan speed could
double.

Ah, no, I didn't. Although double zero speed would still be zero (-:

Third thing is Windows Search Indexer. Check in
Task Manager, and see if it has gone nuts. I have
one OS here, where the damn thing stays railed on
one core, and the file count in the dialog never
increases. And yes, I've reset the build operation
to make it start over again, and when it gets to the
end, it rails again. You have to change the service
policy on the Indexer, while mercilessly hitting the
"Stop" button, to eventually get it to stop it.

Well, this machine only _has_ one core (it's a VIA nano - same vintage
as the Intel Atom, i. e. it's a netbook [though I think machines are
still appearing with something _called_ Intel Atom in]). I did fire up
task manager, and I don't _think_ anything was railing - certainly the
PC seemed as responsive as usual - but I can't be sure.

Paul

I think I'll just burn another copy of the 32-bit Macrium CD (-:
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

A sleekzorp without a tornpee is like a quop without a fertsneet (sort of).