At first, I posted a comment at: http://www.geekstogo.com/forum/ReImage-com-t223177.html. From there, I went to original link, and posted there: http://www.technibble.com/reimage/comment-page-1/#comment-5177, and at last, I started the topic here.
Since my comment was crtitical, someone Googled ReImage+Broni, and: http://www.google.com/search?hl=en&q=reimage+broni&btnG=Google+Search&aq=f&oq=
I guess...
My main thing here, is WHY DO you hunt people down like this?
Additionally, as EF points out about the blog post:
"CCleanup: Or CCmuckup?" on the reimage blog.
you guys state, that after running it:
1. Task manger still disabled.
if they were disabled before they will remain that way.
2. Multiple viruses still present (system doctor, virusseigyo, advanced registry optimizer, winspyware protect).
CCleaner is a disk cleanup utility. not a malware cleaner.
3. Can’t change wallpaper.
4. Control panel has missing functions.
5. New: Internet explorer won’t load now.
all three of these are directly related to the fact that the machine was infected when you tested it.
Actually, looking around, most of the entries seem to be discrediting their competition- both the good and the bad. You don't usually see direct attacks on competing programs like this from any reputable company. Sure, they provide <comparisons> but what you're doing there is simply saying what the competition can't do without any mention of wether or not reimage can do it, and since reimage isn't a malware scanner either (it's more for system problems) I hardly see any such comparison as fair.
1. Inventory description file ... SHELL32.DLL MD5 check to see if version is correct or modified by a virus.
MD5 has been useless to detect most virus modification for a while now. Several viruses released in the late 90's were able to infect files and change neither their MD5 sum nor their file size. These are rather rare, though. But what happens when MS releases a service pack? do you have to add every single new MD5 hash and filesize for that file into your database?
Of course such MD5 hashes are completely useless if the infection is in an Alternate Data Stream, which is becoming more common.
2. We have no images, we are not an online backup software.
Ahh, see I was under the impression that "re
image" had something to do with images. turns out your just a file copy service.
3. Spare parts, we have replacement files for your damaged files. if SHELL32.dll is damaged, we replace it with a clean copy.
something a quick sfc /scannow is more then capable of doing. And the advantage is it works on windows 2000! And they are NOT "spare parts" that is the worst possible name for them. Additionally, all the "spare parts" are probably the same as those you would be fixed by sfc /scannow.
Also, and the biggest issue- what about when a new version of a specific DLL is released? what happens if I, for example, copy calc.exe from a Windows 7 PC and install it on a Vista machine? What would reimage do then? will it replace it with the windows Vista version, recognize it as the windows 7 version, etc.
And of course the richedit and internet DLLs have far more versions and different Operating system releases that you cannot possibly keep track of them all. especially when some versions being present on the wrong OS are a mark of an infection.
Just set a networking sniffing tool, run windbg, dis-assemble the code and see what we do.
your site is now rated YELLOW by WOT, and I imagine a similar rating is given by mcaffee site advisor. not to mention the still prevalent red ratings of those download locations.
It's been an entire year, or more, since you were notified of these issues. Nicholas Black said he would look into it. and that it was obviously a result of using a software distribution company.
And yet the very same links are still there. Does it really take an entire year to do anything about it? any reputable company would be <all OVER> the issue.
Also, it was your Nicholas Black who stated this:
about 100,000 PCs already fixed and 10 million images in our repository
I'm sorry but we must be using a different definition of "image" here.
If image is not Disk image, then it must clearly mean executable/dll image, as stated before.
basically, all reimage does is the EXACT same thing that sfc /scannow does- at least, with regards to your "spare parts" collection.
