Registry Defragmentation 9.1< のgiveaway は 2009年8月25日
Registry Defragmentation はWindowsのレジストリーを管理してパフォーマンスを向上。新しいアプリケーションを頻繁にインストールする方に最適なプログラム。
Windows 95/98/ME/NT/2000/XP/2003 and Vista
Registry Defragmentation はレジストリーを整理して正確なライン構造に並び替え。ソフトウエアを頻繁に入れ替えする方に最適。
Premium Booster はPC を簡単にパワーアップ。
コメント Registry Defragmentation 9.1
Please add a comment explaining the reason behind your vote.
* Easy to use.
* Works quickly.
* Can backup and restore registry.
* In-house ability to create and use System Restore points.
* Has a scheduler to allow you to automate tasks.
* Did not mess up my computer after a defrag.
* No "analysis" report prior to actual defragmentation.
* Does not warn you to close all programs before you defrag.
* Scheduler is set to run automatically at boot by default.
* Registry backup files are not self-executing (you must have a program that supports the backup format to restore your registry).
* Opens a website in your browser advertising another product during installation.
* Mentions it is for "95-XP" some places and "XP-Vista" other places.
TuneUp Utilities 2008 ("TuneUp Registry Defrag" module)
For final verdict, recommdendations, and full review please click here.
Save | Cancel
Since the website says next to nothing, I read Ashraf's review. I'm giving the same advice I give for most tools which mess with the registry--stay far away from them.
The registry is a specialized database which Windows uses, primarily for Windows and program settings, but applications have been known to put all kinds of stuff in the registry which they aren't supposed to. It's the absolute worst idea which Microsoft ever came up with, apart from Windows itself. The idiots at Microsoft claim that the common database was supposed to provide for ownership and access control, but it fails miserably at both of those. Don't believe me? If there's access control, why are applications allowed to screw up critical registry entries for Windows and other applications? If there's ownership, why does uninstalling programs leave tons of their crap behind in the registry? The whole thing's a fiasco. The issue of ease of application portability (or lack thereof) is actually a very minor issue compared to the rest.
Based on what Registry Defragmentation 9.1 says it does and what Ashraf's review says it does, its documentation is extremely misleading. The registry consists of files, the physical fragmentation of those files is one thing. The registry is a database, the internal structure and fragmentation of the database entries within the physical files is another matter. It's primarily the second issue which Registry Defragmentation addresses, although it implies the first.
I don't care that some people will claim that they've "been using registry tools since they were knee-high and never had a problem". It's an extremely simple matter to determine that the registry is constantly in-use. While there are tools which will track all registry access, both reads and writes, what's relevant are actual changes over time. There are a number of registry snapshot tools, I use a licensed copy of Blue Project SysTracer Pro, an earlier version of which was a previous giveaway. If you take two snapshots over a couple of minutes and compare them, you'll see that all sorts of stuff has changed. Trying to terminate running applications is insufficient. Any utility which modifies the registry as a whole while Windows is running is going to mess stuff up, whether you notice it or not. Such utilities, if used, must be run prior to Windows boot, which Registry Defragmentation 9.1 doesn't do.
There are the issues about whether internal or external registry defragmentation should be done at all. The big-name disk defragmenters (Raxco PerfectDisk, Diskeeper, O&O Defrag, etc.) are all capable of handling the physical defragmentation of the registry and other system files safely. I doubt that they do the internal defragmentation of the database structure, but it's unnecessary, as Windows (at least XP and higher) will handle that automatically as-needed. Unlike Registry Defragmentation 9.1, there are other utilities which will do the internal database defragmentation prior to Windows boot.
Some people are big fans of registry backups. I'm definitely not a fan of all-or-nothing registry restoration, it's guaranteed to screw things up whether you notice or not (again, do traces on a running system and see how much changes, and how rapidly, and don't forget files and the registry have to be kept synchronized). Moderately safe things to do include System Restore (XP and higher), and when desperate, Use Last Known Good Configuration. I do occasional "backups" via SysTracer snapshots. Those let me examine what's changed and specifically select the individual items which I want to restore.
Save | Cancel
- "Registry Defragmentation is a small utility that does gigantic improvements in computer performance"
Yah, just run it 10 times and presto - your computer is 10 times faster. What a load of rubbish!
The facts are : Most registry optimization programs give very minor (if any) performance improvement. Registry operations, after all, are not the most frequent operation. The registry is a database used to store static date that may fragment over time. Most programs when starting-up do look up some values in the registry, and may also store some values when exiting.
The registry may acquire "holes" when deletes are done, as when one uninstalls a program. But it would require a hell of a lot of such operations to unbalance it so that the difference becomes noticeable. Shrinking the size of the registry by x percent doesn't mean at all that performance is improved by x percent, far from it. The improvement from defragmentation is usually measured in nanoseconds and is really unnoticeable and not worth the risk of rendering the computer unbootable. And no reason to do this more than about once a year.
I really dislike companies trying to profit from the non computer savvy and using scarecrow claims that have no validity at all.
Save | Cancel
What I don't like is no Analyse option to report the current state of fragmentation of the registry hives to determine if a full "defragmentation" is even warrented. One has to choose Defragmentation or nothing. I am concerned over the term "also removes unused entries" A defragmenter should not touch the format of any entries in the registry, it should just defragment it and remove the fragmented space left by previously deleted or shortened entries and that is all. The description implies it is also a registry cleaner too and I certainly don't want to trust a programatic registry cleaner when most will change settings that are there for a good reason as well as stuff left behind by lazey developers.
Save | Cancel
More everyday free alternatives that never time out:
* Free Registry Defrag (can analyze first):
* NTREGOPT (get ERUNT with it to make a backup first):
Save | Cancel