Wuzzup from BugBopper: What do you think of it?

Some text problem in 1.1.0.8131, cannot figure out what they are.

Anyway, I have updated sucessfully as the first option is likely "Accept" & second is "Do not accept"

 

i updated both my machines windows 7 64 bit and windows xp 32 bit and the text on both of mine was just fine. while i was writing this i just notice bugbopper has a new version 1.1.0.8151 and when updating to that version its difference now you read it and put a dot for your answer much better of a change

 

Thanks for the reply.

No luck for me, the text is still unreadable in the new version 1.1.0.8151.

I am running Windows 7 32-bit.

 

See, you should have stayed with Windows 95.

But seriously -- Bughumper updated just fine for me (WinXP) with no text problems.

 

Same text problem in my case too...

 

Jim figured out the problem, and is now at work on a solution.

The problem: It's the skins. FWIW, here's the workaround:

1. When you see the ugly dialog, just click OK, which will cancel the update
2. On the main Launch tab, set the Skin Selector to [Windows] and close the program
3. Start again, do the update with nice radiobutton labels
4. When the update is complete, select your preferred skin again

I'll report back here soon with news on a real fix.

 

smith2006 i guess thats why my computers were ok i have the default skin selection
mrgigabyte

 

See David's reply, it is not because of Windows 7.

 

Hello David,

Thanks for the update.

 

You are right, I am not using the default skin.

Personally I think it look nicer in "smokey (internal)".

 

i have to try it

thanks mrgigabyte

 

Same here...

 

In that case you should have stayed with WinXP. (I read somewhere that Win7 is a virus.)
~~~~~~~~~~~~~~~~~~~~~~~~~~

But seriously -- I use smokey & I still didn't have any text problems. Sheesh, no problems. I feel left out.

Never mind all of that -- HEY DAVE, when are you gonna get right click scans?

 

I like this product .

Some thoughts:

• Please consider adding a detailed explanation of exactly what features are lost when unregistered.
• On the Scan Progress tab, there is always a Cancel All button. This may give some the impression that operations are ongoing when there are no operations ongoing. Please consider removing that button and the progress circle when operations are not ongoing. Additionally, before the first file upload (if there is one) takes places, please display a message such as "Uploading files...", and a message such as "Uploads complete" when done uploading. If there are no files to upload, then display a message such as "No files to upload."
• On Scan Progress tab, consider changing text 'Suspects Uploaded' to 'Files Uploaded' - no need to unnecessarily alarm users.
• Feature request: show number of unknown files on the Scan Progress tab.
• Feature request: show names of unknown files in Scan Log tab.
• Feature request: show names of files uploaded in Scan Log tab.
• For clarity, consider changing term "unknown" to "unclassified" in all places it appears in the user interface. The concept of a file that's never been encountered before by Wuzzup/BugBopper is different from the concept of a file that may have been encountered before by Wuzzup/BugBopper but hasn't been classified as good or bad yet.
• Consider consolidating Wuzzup and BugBopper into one product. BugBopper is the better brand name, IMHO. The consolidated BugBopper would feature free scanning for life, eliminating the need for Wuzzup.

 

Bug: a file that's changed since a prior Wuzzup/BugBopper scan isn't uploaded for analysis.

 

Fabulous suggestions. I'll be back here in a bit to provide a detailed response.

 

It is possible that Wuzzup or BugBopper sent the changed file, got the analysis results, and was able to pronounce it OK all within the same scanning session. Sometimes our analysis backlog is less than a minute. Can you tell me if this seems possible (how long did the scan take? was the file encountered near the start of the scan?)

Can you send this file for analysis? You could zip it and email it to me at Support@BugBopper.com

 

I don't think that's what happened. Steps to reproduce:
1. Run Wuzzup/BugBopper and let it scan all executables on disk. Wait until Wuzzup/BugBopper has completed operations.
2. Use a hex editor to edit one of the existing executables so that it's very likely unique in the world.
3. Run Wuzzup/BugBopper again. No 'suspects' are uploaded this time.

I've done this a few times with different files, and always got the same behavior - no changed file uploaded, at least according to the 'suspects' metric. Please let me know if you cannot reproduce this behavior, or if my interpretation is wrong.

 

Thank you .

Another thought: if you wish to keep two separate programs, perhaps Wuzzup could be renamed BugBopper Lite, while BugBopper is renamed BugBopper Pro. By doing so, it should be immediately clear to a person browsing your website that BugBopper Lite and BugBopper Pro are related .

 

Consider consolidating Wuzzup and BugBopper into one product. BugBopper is the better brand name, IMHO. The consolidated BugBopper would feature free scanning for life, eliminating the need for Wuzzup.

I rather like this idea.

 

WHY buy a cow when milk is being given away for free?

For a product to survive over the long term, I think that there needs to be a stream of revenue. If I understand this suggestion correctly, it sounds to me like this idea would very shortly lead to the demise of Bugbopper altogether.

IMO, as it now stands, Bugbopper is not all that much better than Wuzzup. IMO, when there is a free version of a non-free product, the NON-free version must offer MUCH greater features & capabilities than are present in the free version.

But perhaps I have read MrBrian's suggestion incorrectly.

 

Removal would not be free. Or maybe removal would be free for the first 30 days from the first removal. See Hitman Pro as a reference.

So, one can see the cow's milk but one can't drink it unless one pays first.

 

Hi, Brian,

I think you've simulated an overwriting virus. Historically, these were very easy to write, but never found in the wild because they'd damage their host files and be caught. A scan of the WildList doesn't list any virus, much less an overwriting virus. Your hex editor made a change in a file, but did not generate malware. I believe our users are quite safe with this aspect of our approach.

 

Just to add the way I took the suggestion was it would be one product still but removal would like always only be in the PRO version. As an example you do not see two different products for Hitman PRO (Free Scan Only) and Hitman PRO (Paid Removal).