1. The Product Name
Unfortunately, the domains magiczip and zipmagic were both taken. So was rarmagic, but magicrar was available
. Since the product's shell namespace integration is unique, there was no clearer way to communicate this than to append or prepend the phrase "magic" to one of the most commonly recognized archive formats. There are countless utilities with the name ZIP, and by your reasoning you should go and flame them as well for cashing in on the "ZIP brand".2. Allegations of Marketing Hyperbole
If you actually bother to leave your openly admitted and apparently intense paranoia aside for a moment, and actually install the product
, you will find that each claim is based on fact and is entirely accurate. Heavens forbid, you may even like the product!
Moreover, the extensive benefits described on the product page are mostly unique (with perhaps just one or two exceptions). Are you able to counter this claim based on fact and not your own paranoid FUD hyperbole? It is astounding that you are engaged in the exact same thing you are accusing MagicRAR of doing.3. "Windows doesn't select every file and folder by default"False
. There is simply no mechanism in the Windows shell to force Windows to compress all files that are actually safe to compress, even if you have actually selected everything
. Period. You can keep trying and you will see that Drive Press will always compress better - gigabytes better - when you reprocess the drive with Drive Press.4. "Simply calling the built-in NTFS compression routines from multiple threads"False
. There are significant engineering challenges in building safely multi-threaded software that are also load-balanced. You could manually try to compress folders and files using more than one instance of the Windows shell, but it will be simply impossible for you to do load balancing
, such that each thread will end up at the approximate same time. This means you will sit around waiting - and apparently whining - when Drive Press would have already done the job for you.5. "The default Windows compression is date based"False
. The "Default Windows Compression" you are referring to is in the Disk Cleanup utility
, which actually archives files that are rarely used. The compression Drive Press actually does is full disk, transparent, on-the-fly NTFS (de)compression
. What you are talking about has absolutely nothing to do with NTFS compression.6. "The software probably does nothing else than force the compression flag on all files, even on those, where it would make no sense"False
. If you indiscriminately compress all files on your computer, you will actually end up with an unbootable system
. Drive Press is completely safe to use and will not compress files that will jeopardize your operating system's integrity or ability to boot.7. "From their marketing fluff, I'd conclude that the developers aren't too skilled"
Thank you for sharing your marketing insights. Does it occur to you that no archive utility at all features shell namespace extension technology
? Is that because their developers are so much more highly skilled than ours, to the extent that they cannot be bothered to come out of their coder's nirvana, trying to achieve a completely undocumented, extremely difficult level of integration with the Windows shell?8. "because some SSD controllers do their own compression"False
. The SandForce compression you are referring to is not at the file system level
. Meaning, it will not actually give you any additional space on disk. With Drive Press, you actually get additional space on disk. I agree that this may stress SandForce based SSDs when they are unable to re-compress the raw data they receive from the OS...but that is something you will need to take up with the drive manufacturers. If a SandForce drive crashes when it has too much compressed data, do you blame the compression software - that runs fine on every other drive - or SandForce for making a loose assumption which you have just violated? In fact, I would strongly recommend all SSD users to avoid SandForce drives because they are extremely brittle under atypical, non-consumer loads. What this means for YOU, the consumer, is that your drive may randomly fail after years of apparently "successful" operation - at the worst possible time of course. That's a real concern you *should* be getting paranoid about.9. "Somehow I'm reminded of this"
MagicRAR has nothing to do
with that company, period.10. Conclusion
You are free to drink the kool-aid of the competition and attack MagicRAR with FUD. The fact remains that none of you have even bothered to try the software, in addition to the many factual inaccuracies in your posts above which I have ripped apart to shreds above. We all at MagicRAR have worked very hard to bring you genuine innovation - but apparently you are so brainwashed by the existing brands which have been selling you essentially the same tools for over a decade, that you cannot possibly conceive of actually having something better
- save recognize when it is actually delivered.
for discussion on Tom's Hardware of using MagicRar to improve SSD performance.