VoodooShield/Cyberlock

Speaking of videos, if VS had a video that describes all that has happened since I started four years ago, it would be this


https://www.youtube.com/watch?v=BT1ircqQklo

Canadians know how to rock, right TH?

I realized somewhat recently that a lot of users do not understand what we were trying to accomplish, unless they could experience VS working the way it should be working. So just because we had certain ideas in mind, that did not mean that every user would understand what we were trying to do. Basically, it was vital to get VS running really, really, really well.

I have also learned a little more about coding security software over the last four years, so that has helped as well. So the last couple of months I tried to create the best computer lock possible, and I think we are getting close. There are still a few minor bugs (mainly with XP), but they are easy to fix.

Sorry I have missed a lot of posts, but I will catch up very soon.

Thank you guys for all that you have done, I really appreciate it .

 

I did a fresh install of v2.72, after uninstalling v2.50...It seems OK, except for the high CPU usage on XP mentioned previously, that still occurs after initial bootup.

 

Tarnak, there is already VS 2.73.

 

I know, but Dan asked, if anyone running XP, to test and let him know....So, that's what I just did...I was slow to do that, and in the meantime v2.73 beta was released.

 

Ahhh.....mkay.

 

@VoodooShield have u any plans to make the option avaiable for free that we can disable the desktop symbol? Specialy when someone play games like me or show often movies online its abit annoying and while playing i have some frame laggs sometimes when its open.


nvm,just installed the latest beta to test it out didnt use it for some times and see with rightclick we can disable it,nice!

 

Hehehe, try VS now... I think you will like the Scan & Allow option .

 

VS auto detects whether something is an installer or not, then displays either the Allow button or the Install button, depending on if the blocked file is an install or not. That way, if someone is trying to install something, VS will turn OFF like it should... but it will ask the user if they want to turn VS back ON again if they return to a web app.

 

I know... I have been dealing with this for a long time now. Some versions of Chrome work ok, but some versions do not shutdown chrome.exe when the user exits Chrome. It has nothing to do with VS.

 

Cool, if you guys think of any others, please let me know. Maybe System Restore as well, huh?

 

Hehehe, I am not sure what I meant here, but yeah, appdata and programdata are 2 of the top hangouts for malware. Either way, it is fixed in the latest version.

 

There is a new feature that asks the user if they want to relock their computer when they return to a web app... assuming that the user turned VS OFF. I think this is what you mean, if not, please let me know.

 

Yeah, everything should be working by now .

 

Hehehe, if anyone on Wilders ever needs a license, just let me know!

 

Not in this case... If the user MANUALLY disables VS, they will be prompted when returning to a web app either way. Let me think about this... we might want to make this part of that option.

 

Yeah, it is fixed in the latest version. If it is not working the way you want it to, please let me know!

 

Cool, thank you. Please try 2.73 .

 

Cool, yeah, that is a good command line.

 

Hey Pete. Cool, thank you... please try 2.73 and let me know what you think .

 

From what I remember, I think I added this option a long time ago because a lot of times an installer will launch a web app towards the end of installation, then run some command lines and finish up the install. So basically, VS was reactivating because the installer launched a web app during installation, but I thought it might be a good idea to check with the user first. We can refine this a little... it will be easy. But I agree, VS should automatically turn ON whenever a web app is running in Smart Mode... unless an installation is running.

 

Hmmm, that is odd, but it should be working great now, if not, please let me know!

 

Yeah, that is all fixed in 2.73, but if you find any issues, please let me know!

 

Great to hear, thank you. Please try 2.73 .

 

Cool, thank you TH .

 

Yeah, it is fixed now... as we have discussed many, many times on here, it is critical to block new processes in the appdata and programdata folders. So if for some reason 2.73 is not working right, please let me know, thank you!