Swap File Size

That's pretty much my take on it, too. Reg cleaners definitely have
their place in this world of ours these days. I particularly liked your
fist paragraphG.

Cheers,

Twayne`



"db" wrote in message

I agree.

you see, some people are simply hyprocrites or ignorant
at best.

they do not understand what database's are.

they do not understand that the operating system is a highly
complex database and when people add programs to it, they
are updating the database.

so if they clean and defrag a database like the operating system,

then they should also clean and defrag the registry hive because
it is also database - a database of keys and settings.

the registry keys in a database are not unlike a handful of ol'
computer punch cards.

bad cards or erroneously punched cards had to be removed or
replaced before processing them as a batch or the end results
would be erroneous.

a faulty registry will not only decrease system performance and
has to propencity to prevent the system from booting.

I did an analysis on a couple of registry cleaners utilizng simply
database methodologies.

the microsoft one care reg cleaner and the eusing cleaner were
proven as beneficial in keeping the reg cleaned of unneeded keys.

removing unneeded keys keeps the hive lean and mean and less
fragmented.

people don't realize that if one fragments out of dozens belonging
to a file becomes corrupted, then that entire file becomes corrupted
as well.

also, if one fragment of a file system becomes corrupted, then there
is a possibility that the file system is becoming corrupted as well.

reducing the registry fragmentation has also been addressed by
mark russinovich.

so it is highly important for people to use the reg cleaners I
mentioned above.

or will be seeing them in the future posting an issue about the
failure of their system to boot up due to missing or corrupted system
32 files.

~~~~~~~~~~~~~~~



"Twayne" wrote in message
...
"Gerry" wrote in message

Twayne

So you would agree, on the basis of what you now say, that the
"crap" you have written about Registry Cleaners is a lot of
nonsense. You being, one of a small minority, who regularly
advocate their use.

Nope, not at all. You try to insult me, but I don't worry about the
small stuff like you. I've written all factual and correct
informatoin about registry cleaners. The only ones I disagree with
are those who say they are "snakeoil", "never any good", "cannot do
anything useful", "will damage your computer" and similar statements
made by some egotistic narcissists around here. Because I say a
registry cleaner CAN be useful does not mean one should run it every
day, and I've never said any such thing, but you could run one every
day, and other than wasting your time, you would never see any
downsides to it as long as it was a reputable, reliable and properly
sourced program. Anyone that says to NEVER use a registry cleaner
because it WILL damage your system, for the stupid reasons they
give, without a drop of backup, is a fool, and I could make a long
sentence out of this, but I won't. I have often used registry
cleaners for various taks: Most of the
time they accomplish nothing noticeable, the other times they
accomplish a good fix for a problem, and if nothing else, when the
TSing leads you to the registry, they're good for the process of
elimination. Of the hundreds of machines and the many hundreds of
times I've used a good registry cleaner, I have never encountered so
much as one event of damage or detriment to an operating system. And
if that did happen, I'd be able to put the "fix" back and
correct the erroneous "fix" that way. But like I said, it's never
happened to me or anyone I respect or have seen occur. IME good
registry cleaners are more robust than most programs, better tested
and have not, for instance, done any of the damage that Microsoft
itself has done to their own operating system over the years. Partly
because of the robustness of the XP registry heirarchy, and
partly because I know how to choose a useful product, as most any
thinking person can do. Unless and until someone provides
verifiable, repeatable evidence
otherwise, I will continue to believe that those who say to never
use such a thing and how much damage it will cause are simpletons of
yesterday who can/will not open their eyes to see what's right in
front of them. lol, sorry! I've done a lot of work with registry
cleaners and their
breathern, and have considerable positive experience with them. The
ones I use mostly (three of them) are excellent programs and no more
likely to cause any damage to a system than any other program on a
computer. Stuff DOES happen, and eventually I'm sure a negative
outcome WILL result from a registry cleaner, but when it does
happen, it will be no surprise since at ANY time windows can do
silly things, "stuff" happens, and it's silly to say always or never
in any continuous, without exception way because there is no such
solidarity in the universe. THAT is my objection to the
misinformationists. If I say never or always I attach a timeframe
to it for occurring in the past experiences, I don't encompass all
time in the universe for every living person on the earth as the
misinfomationists are wont to do. And if tomorrow the opposite
happens to me, it would interest me, but it would not cause such
fear in me as it seems to do in these few MVP misinformationists and
their sock puppets they've been weaning. What is entertaining about
them is the seriousness of which they've trapped themselves into
believing their own tripe and it's even entertaining to watch them
wiggle when someone has the audacity to actually say their
information isn't correct. g Cheers,

Twayne`





Twayne wrote:
"Gerry" wrote in message

John

Most people SHOULD want to know why! A lot of "crap" is posted. A
test of the value of the advice is being able to understand why
and what is being recommended.

Actually, the more important thing is to verify and clarify an
answer that seems plausible from other sources if it has any
importance to the querant. That needs to be done for anyone
getting information from anywhere on the 'net, period. I often
don't ask why unless it's important to me, since when I go
elsewhere to verify it, I'll find out why anyway.
OTOH it's nice if a poster does say why something is so, if he
actually knows it for a current fact.

HTH,

Twayne`




John John - MVP wrote:
Bennett Marco wrote:
John John - MVP wrote:

John John - MVP wrote:
Just D. wrote:

Btw, I'd wish to know how could I move the hiberfil.sys to
another location than the C:\.
It can't be done, the file *must* reside in the root of the
system partition alongside the ntldr, NTDETECT.COM and
boot.ini file. This is due to file system driver limitations
during the early stages of the boot process, at this early
stage the system relies on the ntldr mini file system driver
and the file can only be loaded if it is in the root folder
of the system partition.
PS: The hyberfil.sys will be on the same volume as the
/Windows folder (the boot volume), that is where the operating
system will create the large memory image file. But, the file
hyberfil.sys *must* also be in the root of the System
partition alongside ntldr, that is the only place where ntldr
will look for it. The hyberfil.sys file on the system
partition will either contain the actual memory image, (when
the boot and system partitions are one and the same) or it
will contains the ARC path to the boot partition of the last
operating system that entered hibernation (when the boot
volume is on a different partition than the System partition).
John

Woulda been simpler to have just stopped after "It can't be
done".

Some people want to know "why". If you already know, or if you
don't want to know, you can just move on, others will do as they
please. John

Yes they have their place------in the nearest trash can.
"Twayne" wrote in message
...
That's pretty much my take on it, too. Reg cleaners definitely have their
place in this world of ours these days. I particularly liked your fist
paragraphG.

Cheers,

Twayne`



"db" wrote in message

I agree.

you see, some people are simply hyprocrites or ignorant
at best.

they do not understand what database's are.

they do not understand that the operating system is a highly
complex database and when people add programs to it, they
are updating the database.

so if they clean and defrag a database like the operating system,

then they should also clean and defrag the registry hive because
it is also database - a database of keys and settings.

the registry keys in a database are not unlike a handful of ol'
computer punch cards.

bad cards or erroneously punched cards had to be removed or
replaced before processing them as a batch or the end results
would be erroneous.

a faulty registry will not only decrease system performance and
has to propencity to prevent the system from booting.

I did an analysis on a couple of registry cleaners utilizng simply
database methodologies.

the microsoft one care reg cleaner and the eusing cleaner were
proven as beneficial in keeping the reg cleaned of unneeded keys.

removing unneeded keys keeps the hive lean and mean and less
fragmented.

people don't realize that if one fragments out of dozens belonging
to a file becomes corrupted, then that entire file becomes corrupted
as well.

also, if one fragment of a file system becomes corrupted, then there
is a possibility that the file system is becoming corrupted as well.

reducing the registry fragmentation has also been addressed by
mark russinovich.

so it is highly important for people to use the reg cleaners I
mentioned above.

or will be seeing them in the future posting an issue about the
failure of their system to boot up due to missing or corrupted system
32 files.

~~~~~~~~~~~~~~~



"Twayne" wrote in message
...
"Gerry" wrote in message

Twayne

So you would agree, on the basis of what you now say, that the
"crap" you have written about Registry Cleaners is a lot of
nonsense. You being, one of a small minority, who regularly
advocate their use.

Nope, not at all. You try to insult me, but I don't worry about the
small stuff like you. I've written all factual and correct
informatoin about registry cleaners. The only ones I disagree with
are those who say they are "snakeoil", "never any good", "cannot do
anything useful", "will damage your computer" and similar statements
made by some egotistic narcissists around here. Because I say a
registry cleaner CAN be useful does not mean one should run it every
day, and I've never said any such thing, but you could run one every
day, and other than wasting your time, you would never see any
downsides to it as long as it was a reputable, reliable and properly
sourced program. Anyone that says to NEVER use a registry cleaner
because it WILL damage your system, for the stupid reasons they
give, without a drop of backup, is a fool, and I could make a long
sentence out of this, but I won't. I have often used registry cleaners
for various taks: Most of the
time they accomplish nothing noticeable, the other times they
accomplish a good fix for a problem, and if nothing else, when the
TSing leads you to the registry, they're good for the process of
elimination. Of the hundreds of machines and the many hundreds of
times I've used a good registry cleaner, I have never encountered so
much as one event of damage or detriment to an operating system. And if
that did happen, I'd be able to put the "fix" back and
correct the erroneous "fix" that way. But like I said, it's never
happened to me or anyone I respect or have seen occur. IME good
registry cleaners are more robust than most programs, better tested
and have not, for instance, done any of the damage that Microsoft
itself has done to their own operating system over the years. Partly
because of the robustness of the XP registry heirarchy, and
partly because I know how to choose a useful product, as most any
thinking person can do. Unless and until someone provides verifiable,
repeatable evidence
otherwise, I will continue to believe that those who say to never
use such a thing and how much damage it will cause are simpletons of
yesterday who can/will not open their eyes to see what's right in
front of them. lol, sorry! I've done a lot of work with registry
cleaners and their
breathern, and have considerable positive experience with them. The
ones I use mostly (three of them) are excellent programs and no more
likely to cause any damage to a system than any other program on a
computer. Stuff DOES happen, and eventually I'm sure a negative
outcome WILL result from a registry cleaner, but when it does
happen, it will be no surprise since at ANY time windows can do
silly things, "stuff" happens, and it's silly to say always or never
in any continuous, without exception way because there is no such
solidarity in the universe. THAT is my objection to the
misinformationists. If I say never or always I attach a timeframe
to it for occurring in the past experiences, I don't encompass all
time in the universe for every living person on the earth as the
misinfomationists are wont to do. And if tomorrow the opposite
happens to me, it would interest me, but it would not cause such
fear in me as it seems to do in these few MVP misinformationists and
their sock puppets they've been weaning. What is entertaining about
them is the seriousness of which they've trapped themselves into
believing their own tripe and it's even entertaining to watch them
wiggle when someone has the audacity to actually say their
information isn't correct. g Cheers,

Twayne`





Twayne wrote:
"Gerry" wrote in message

John

Most people SHOULD want to know why! A lot of "crap" is posted. A
test of the value of the advice is being able to understand why
and what is being recommended.

Actually, the more important thing is to verify and clarify an
answer that seems plausible from other sources if it has any
importance to the querant. That needs to be done for anyone
getting information from anywhere on the 'net, period. I often
don't ask why unless it's important to me, since when I go
elsewhere to verify it, I'll find out why anyway.
OTOH it's nice if a poster does say why something is so, if he
actually knows it for a current fact.

HTH,

Twayne`




John John - MVP wrote:
Bennett Marco wrote:
John John - MVP wrote:

John John - MVP wrote:
Just D. wrote:

Btw, I'd wish to know how could I move the hiberfil.sys to
another location than the C:\.
It can't be done, the file *must* reside in the root of the
system partition alongside the ntldr, NTDETECT.COM and
boot.ini file. This is due to file system driver limitations
during the early stages of the boot process, at this early
stage the system relies on the ntldr mini file system driver
and the file can only be loaded if it is in the root folder
of the system partition.
PS: The hyberfil.sys will be on the same volume as the
/Windows folder (the boot volume), that is where the operating
system will create the large memory image file. But, the file
hyberfil.sys *must* also be in the root of the System
partition alongside ntldr, that is the only place where ntldr
will look for it. The hyberfil.sys file on the system
partition will either contain the actual memory image, (when
the boot and system partitions are one and the same) or it
will contains the ARC path to the boot partition of the last
operating system that entered hibernation (when the boot
volume is on a different partition than the System partition).
John

Woulda been simpler to have just stopped after "It can't be
done".

Some people want to know "why". If you already know, or if you
don't want to know, you can just move on, others will do as they
please. John