VoodooShield/Cyberlock

Yes, I was planning for that to be the final release for 1.25, so I included the updater when I compiled it. I really thought I had everything just right in that version, but for me it is not working too well, it is very buggy. Is that what everyone else is experiencing as well?

So if you do update, it will install a previous version... which the way 1.25 is running, may actually be a good idea .

It really is hard to get VS to do exactly what we want it to do, but we are very, very close. And once we are finished, it will be well worth it.

It is like this... OK VoodooShield, a browser is open so turn ON... Hey VS, the user clicked on you, so turn OFF, but do not forget to reactivate if that is enabled in settings... Nevermind, someone just inserted a USB drive, turn ON... OK, you blocked something and someone clicked on your balloon, so turn OFF.

Poor little guy, I think we are bossing him around too much .

 

Cool, thank you for helping me out with this. What version of windows are you running? Has there ever been a version of VS that worked really well for you? If so, which one was it?

 

Cool, thank you for letting me know. Is there any chance that you are running AVG? Here is a thread that has a lot of good ideas to try. Please let me know what you find!

http://forums.anandtech.com/archive/index.php/t-220057.html

 

Hehehe, I saw that too!!!!!!!!! I was sooo frustrated when I saw that. I will get it right very soon. Everything was fine until we added the Protect User Space and USB Drive support. The more options we add, the hard it is to tell VS whether it should be ON or OFF.

I switched back to the 1.24 current release until I get all of the timings just right. I worked on it a lot last night and got pretty far... it will be just right soon! Thank you for letting me know... I was starting to think that I was just seeing things .

 

are you planing to change the name?it will be nice to get a nice name

 

I just did a short time ago...



P.S. I have manged to get .NET v3.0 installed, but getting v3.5 installed is proving to be a hurdle.

 

There's no sense until you finish the last fixes as every new version will be unknown again, in the end I can submit them and only these 2 processes are unknown. If they were detected as bad it would say

c:\program files\voodooshield\voodooshield.exe [MD5: 8080831D5159BB7C99A8BCE5D32DA3B6] [Flags: 10081001.9385]
c:\program files\voodooshield\vsup.exe [MD5: 569F597AF273982C132A74183D80B664] [Flags: 00081001.9384]

c:\users\daniel\downloads\install voodooshield.1.25.exe [MD5: B21C370ED1B3C34E137D819FA23BFE87] [Flags: 00081001.9383]
d:\security programs folder\voodooshield folder\install voodooshield.1.24.exe [MD5: 93170C07AD4E9C0D94747CBA793A58FE] [Flags: 00081001.9358]
d:\security programs folder\voodooshield folder\install voodooshield.1.23.exe [MD5: D1541BD779404AB120772EFA37DF20FB] [Flags: 00081001.9321

HTH,

Daniel

 

My bad Dan Cool, I didn't know you already had a company name.

 

I rolled my Laptop image back so I will be upgrading from Version 1.09 to 1.25 in a bit. I will let you know how that goes.

 

The upgrade from 1.09 to 1.25 went ok. I will test some of the features a little later to see what I find.

 

Sure, if we can figure out a really cool name that describes VS well. There have been a lot of suggestions and we are going to do a poll to see what people like the most.

 

Thank you for that!

You should not have to install the .net frameworks one by one... VS should do it all for you if you just install VS without .net 3.5!!!!

 

Oh, I see. That does make sense now that you mention it. Thank you!

 

I am having serious issues with 1.25. I mean it works but it is very quirky.

It will be running exactly right very soon!

 

thank you dan

 

TerminatorShield, maybe TMShield (TM=Short for Terminator).

OperShield, (Oper=Short for operating, from operating system).

AtomShield, StopShield...

 

bombguard lol or even explotionshield
what about lol we have to find a good name

 

Do you really want those added to the list?

 

Just the mention of the word 'bomb' these days in the wrong place can land you in trouble.

 

i was just kidding
we have to find a better name for it

 

Definitely since 911 here in the United States. I think Bomb anything would cause some people not to use a product unless it really has something to do with a bomb.

 

I was hoping so lol Thanks for the clarification though.

 

i just wonder if VS and AppGuard are good solid protection

 

Appguard, and VoodooShield combined definitely offer superb protection. I would just recommend adding a good traditional antivirus. You never know if something you are installing or allow to run has malicious code in it. Also, Appguard, and VoodooShield do not provide phishing protection. There are other reasons to use a traditional AV as well, but the two I named are the first that comes to mind for me.

 

All VS files are now Good in WSA for 1.25 it took support 7 minutes to reply.

[-] = UNKNOWN NONEXE
[G] = Good


Some legitimate files are not included in this log
[G] c:\program files\voodooshield\unins000.exe [MD5: 68A5B1324BEF34E90CED35B33026F04F] [Flags: 40000000.61]
[G] c:\program files\voodooshield\voodooshield.exe [MD5: 8080831D5159BB7C99A8BCE5D32DA3B6] [Flags: 10081001.9385]
[G] c:\program files\voodooshield\vsup.exe [MD5: 569F597AF273982C132A74183D80B664] [Flags: 00081001.9384]
[G] c:\program files\voodooshield\startvs.exe [MD5: 524E232B55BDD1F7AEE3E4F36CEC0FE0] [Flags: 00111000.9175]
[G] c:\program files\voodooshield\virustotalupload2.exe [MD5: EAC393C39AC69CA813ACB017CB4AB05F] [Flags: 00000000.7103]
[-] c:\program files\voodooshield\eula.rtf [MD5: 5B5A21E7C954480BC6ACD1D46A1AAA25] [Flags: 00000000.0]
[-] c:\program files\voodooshield\unins000.dat [MD5: F0A4C2D5BD74EB1668F7F0A783B0E293] [Flags: 00000000.0]
[-] c:\program files\voodooshield\voodooshield.exe.config [MD5: 321CA199EABBB02E867C5BD04711F000] [Flags: 00000000.0]
[-] c:\program files\voodooshield\voodooshield.xml [MD5: 0795443FDAB6D27E7E86279B7B45394E] [Flags: 00000000.0]
[-] c:\program files\voodooshield\vsicon.ico [MD5: 62949A761431A94FB784EF1D9F066758] [Flags: 00000000.0]

Cheers,

Daniel