VoodooShield/Cyberlock

I just collected all the data you may need for debugging. I will upload it to my dropbox account tomorrow when the internet is working, and send you the link. I have less than 56k down, and my upload does not even register. I can't even get speedtest.net to load right now. I'm going to roll my Laptop back now incase anything became corrupted.

 

Hmmm, it looks like AG and VS are not playing well together for some reason. I would try a couple of things...

1. After restoring your laptop to the factory image, try VS 1.27 without AG and see how it does.

2. You can try the old VS 1.26 with AG http://voodooshield.com/Download/versions/Install VoodooShield.1.26.exe

But I really do not think there were any changes from 1.26 to 1.27 that would create these issues.

I just installed VS on 5 computers at a client's place today, and 1.27 worked great on all of them. It was pretty cool because he had everything from an old XP machine to a brand new machine, so basically every OS, and 5 different hardware profiles.

Is this the same machine that has been experiencing a BSOD? If so, I would bet that there is some kind of bad hardware, maybe a bad motherboard, bad stick of RAM, or bad HDD.

The logs are stored here: C:\Users\User Name\AppData\Roaming\VoodooShield\VoodooShield\0.94.0.0\log

Ultimately there was only one version of 1.27. There were a few small tweaks that I tried, but nothing that would cause the problems you are experiencing.

Please let me know what you find out! Thank you.

 

A request please Dan

Could you adopt the system setting for the date in the logs. It gets confusing reading them.

 

Sure, which logs are you talking about?

 

All, but User log in particular. The UK format is DD/MM/YY and it gets confusing reading them.

 

Oh, I see what you mean now. So you want the ability to change the format of the date? Sure, I can do that at some point.

 

I think djg is suggesting that VS should auto adjust its date format in logs to the system date format (DD/MM/YY in this case or any other).

 

Thanks Siketa - yes VS should look at the regional settings and apply them to the program

 

I see, thank you for clarifying siketa. Sure, I should be able to include that in the next update. At some point we would like to offer VS in many different languages as well.

 

Wish I could buy you a reliable desktop workstation for all testing purposes, but (sorry) I'm not a millionaire. Throwing just about anything I can get hold of at my all-around modest Windows 7 Pro, vintage 6-core AMD, is my idea of life. I haven't had one problem with VoodooShield (from version 1.23) in combination with 11-or-so layers of security (kicking-in variably, depending on what I want to do with my PC).

On the other hand... thank you very much, Dan. I've fancied this kind of anti-malware implementation (anti-exe) concept from many years back. Only, I'm no developer, at least from the days of BASIC (ca 1983, Asia) and later the Y2K hullabaloo (1998, NJ/NY)

 

Thank you, I am happy to hear that you like what we are doing! Hopefully Cutting_Edgetech will figure it out soon, I really think it is a hardware issue.

Yeah, my first computer was a commodore vic 20, those were the days, huh? The first software I ever wrote was a card game known as In Between. Basically, the dealer would deal 2 cards, and you had to guess if the next card was in between the 2 cards he had dealt you. It was a card game that I played with my uncle at the lake when I was 10 or so. Anyway, it was an all text game, but it was actually fun!!! Here is the source code

10 Print "In Between"
20 A=int(rnd(1)*52)
30 B=int(rnd(1)*52)
40 C=int(rnd(1)*52)
50 Input "Is the next card going to be In Between " A$ " and " B$ "?"
60 If C$ <>...

Ok, I forgot the rest .

 

I thought this was the VS code.....

 

It is . See, VS really is simple .

 

BTW, I found one small bug. When you click "Yes" to the final prompt when you are trying to run something, it changes the "Protect User Space" Option to unchecked. It is a super easy fix, and I will update it tomorrow.

 

Confirmed Bug.

Daniel

 

You crack me up TH! . I am going to look at the date format in the log, and see how hard that is to change, then add the one line to fix this issue. The only thing is, most of the non-wilders VoodooShield users would rather me not push out too many updates, so I might wait a week or so to see if any other bugs appear.

Also, I noticed something very interesting the other day. I was removing viruses from a computer that did not have VS. This computer was just absolutely riddled with viruses. Anyway, I removed about 95% of the viruses and decided to install VS, and I was going to reset the whitelist after it was completely clean. Well, after installing VS, I noticed that VS was blocking 2 different viruses in the AppData folder, which from my experience, is typically where the viruses are (or programdata folder). Anyway, it was blocking the viruses because of VS's option to not whitelist items in the AppData directory. So it made it a lot easier to remove the 2 viruses because VS would not let them run.

Anyway, I was thinking that VS could have a Baseline Whitelist Mode, where after VS is installed, it takes a baseline snapshot and stores it separately from the normal whitelist snapshot. Then if for some reason a virus did get through, the user could just put VS in this mode, and it would kill everything that was not on the initial snapshot after installation.

So it was just a thought, what do you guys think?

 

genious

 

Dan - Like that idea. Would you be able to rollback to that initial snapshot.

 

Thank you guys! Yeah, it would just load the baseline snapshot instead of the normal snapshot. We could also create a standard snapshot for XP, Vista, 7 and 8, and use those, but it might just be better to use the initial snapshot that is taken on first run of VS after installation. It is something to think about.

 

Wow you guys have the extremely fast support, keep up the awesome job...

 

Thank you, we appreciate that!

 

Dan, that is a great idea!

 

I am not sure what is going on here, but I am beta testing another software, i.e. Vipre AV, which seems to have affected VS icon.

 

Also, looking at the log for VS, shows a lot of entries suddenly happening since yesterday. Seems odd.

 

Ok, thank you for letting me know. I noticed that you are running XP, and I made some changes for VS's desktop shield gadget in 1.27 so that there would no longer be a black boarder around the shield.

So I am thinking that it is either that change, or it might be a conflict with Vipre. Is there a chance that you can run 1.26 for a couple of hours to see if you still have that issue?

Here is the link to 1.26 in case you are interested in trying it. http://voodooshield.com/Download/versions/Install VoodooShield.1.26.exe