VoodooShield/Cyberlock

Maybe jmongeShield would be fine?

 

Not bad .

 

This product already has a good reputation under original name.

 

The icon problem has reoccurred, and also I am seeing an excess CPU usage.

 

It's been a while since I was online. The technician from my ISP (TDS) never did show up. My internet has been out for the most part of two weeks now. I made an appointment for them to come two weeks ago. They was suppose to come on Monday, but never showed. Each day since they have informed me they would come each day, but never showed. I had an extra modem router combo we used that only worked for a short time before it would not work anymore. TDS gave us that one as well. I plugged it in, and now the internet is working. I tested the Linksys router, and the modem we was using. The router works fine. The modem seems to be fine, but it appears the ISP is blocking it. I can't wait to move away from this area! TDS has to be one of the worst ISP's in the country! I know this combo box i'm using will not work long so if you guys do not hear from me again for a while then you will know my internet is out again.

Well I have a lot of catching up to do with the thread. Hows coding coming along with running VS as a service?

 

No not at all since this ~ an it's gone now.

TH

 

Is that with Vipre running? How long was VS running fine before Vipre was installed? I signed up for an account with premiumbeta.com to see if I could download the Virpre beta, so I am waiting to hear back from them.

On the CPU utilization, what are the CPU values for VoodooShield.exe and startvs.exe in the task manager?

 

It could be all the other things as I just use WSA & VS.

TH



And Task Manager it shows even lower.

 

Tarnak, looks like you have run into some of the same exact problems I had the last time I used VS right before my internet went out. I hope VS running as a service will resolve these problems. The last time I ran VS it started blocking several vital services. I even tried disabling backing up of the whitelist to the cloud. That made things worse VS was completely shutting down my Laptop.

Dan, sorry I did not get back with you about your PM. I think you understand though since i have not had any internet access since receiving it. I'm not using Viper, but i'm pretty sure I have discovered a major bug with NOD 32 in which my computer will not boot when using NOD 32. I always have to do a hard shut down. After uninstalling NOD 32 I have not had anymore boot failures, or problems with Windows hanging as soon as the desktop loaded. I was having this problem a lot, and I tried uninstalling everything I though could cause it, and it continued to occur until I uninstalled NOD 32. The only thing i'm using presently is Appguard so i'm not visiting anything except security, and tech forums right now. I'm going to have to get some support from Eset to see if they can guide me through forcing a BSOD by using the hot keys so I can generate a full memory dump to send them. I have been unsuccessful so far. I have tried several different hot keys combinations that I have found listed online, but none of them have worked. I know sometimes forcing a BSOD with the hot keys can not be done if the system hangs at a low level.

 

I know what you mean about bad ISP's... the only good one in Kansas City is Google Fiber, but they are not quite in my area yet.

Well, I am trying to decide exactly what to do, because the service is going to do 3 main things.

1. It will have a more reliable method for getting the paths of the processes
2. It will use the new kill method
3. It should be unkillable as well

So there is a lot involved, and I need to make sure that VS 1.xx is stable in the mean time. I think for the most part it is extremely stable, but it seems to possibly have some conflicts with other security software. I hope to be finished with VS 2.0 in a month or two, it just kind of depends on a lot of things.

 

Me too. I run VS on 3 systems... Windows XP, 7 and 8, and I have not seen any errors at all for 1.27. I am going to try some of the other security software that other people have been using and try to get to the bottom of the issues they are having.

 

No offense Dan, but only 26 people has voted, and by that you say you will most likely keep it Just want to point out that I too think you should keep it as I am not a "strong" believer, I believe at same level as most people I guess whatever that is, almost neutral But with that said, I also think it is important to remember people like jmonge wich dislike it so much that he won't even use it, even if he likes the product. But if you don't mind losing some income due to the name then yes you should keep it.

I guess the best would have been to have thought about this before you named the product, gone through trademark process etc etc...since as you say that cost money. So starting all over now is perhaps a bit too late

 

I wonder if you and Tarnak are running the same software with VS when there are issues? Is there a chance that you and Tarnak can list the other software you guys were using when VS was having issues? Also, I wanted to make sure that UAC is not enabled on your machines when running VS. VS 2.0 should work fine with UAC, but the current version does not work that well with it enabled.

 

Yeah, I totally understand what you are saying. When we first started the project close to 2.5 years ago, the initial name was VS. We almost did not use that name because of a trademark issue with HP, but it turned out they they were abandoning the Voodoo trademark. Remember, for awhile HP had a line of computers known as VoodooPC. And we even realized at the time that they were probably abandoning the name because of marketing problems.

So we spent 4 months or so trying to come up with a different name. We even hired a marketing company to help us, but they ultimately liked the name better than anything that they came up with. We then talked to another big time marketing genius, and he absolutely loved the name VS. I was quite surprised, I thought he would truly dislike the name.

We still can change the name if someone comes up with something better. For me, the name really doesn't matter. I just know that some people have an issue with it, and I would like to find a better name if possible.

 

I agree we are not looking at chicken bones or Dolls of people to stick needles in to give pain to me it's just a name. http://en.wikipedia.org/wiki/Voodoo and there's Voodoo in computing. http://en.wikipedia.org/wiki/VoodooPC from Calgary, Alberta.

TH

 

I had UAC turned off. I have been using NOD 32, Appguard, and Shadow Defender with VS. VS even started blocking Appguard. Shortly after VS began to block spmservice, isbmgr, exporer.exe, and igfxpers. I had all the exceptions defined for AG to allow VS full access to everything. I have been using them together for well over a year now, and this was the first time anything like this happened. I had also trained VS for over 12 hours in training mode while working offline. I did discover some services that came installed with this Sony Laptop was causing some errors so I uninstalled the software. Viao care that came with this Laptop was attempting to read the memory of every single application I used. Appguard was blocking Viao care from doing this because this is usually an unsafe action. I'm building my next Laptop so I will have a dependable machine!

 

Well if not you guys, or even the "experts" at the companies you worked with could come up with something better then maybe you should keep it, as in "it's meant to be" (says the man who is not a believer ).

Regarding the poll, first it's too few people voting, and second, if you're really looking for a new name(no looking back), then VoodooShield should not be included in the poll since everyone that likes it would vote for it, and the new names would not get a fair chance, and you'll end up keeping it

 

Is there any chance that you could try VS 1.26 to see if you still have these issues? From what I remember, I think 1.26 ran great on your computer, and that would be a HUGE help if you could try it. If so, you can download it here:

http://voodooshield.com/Download/versions/Install VoodooShield.1.26.exe

 

Rather than answer everyone, this is my current software, which also shows the load order...I have to go out, so won't be available to answer any questions.

Currently, VS has no CPU issue.

 

Yeah, that is true, 26 votes is simply not enough to be able to tell for sure. Maybe we should have left out VS, but then again, it is kind of helpful to have it included as well.

 

That is a secure system!!! It is hard to say which security software is conflicting with VS, but I am going to try Vipre beta since that was your first inclination.

Were you running VS 1.26 for awhile without any issues? And then VS 1.27 for a day or two without issues, until you installed the Virpe beta?

 

I fail to see how it is helpful if the goal is a new name, if you're seriously looking for a new name then there should be new product names only, nothing old.

As I said, even meme would vote for VoodooShield, but I can't do that if it's not included. And that's the point, I would be forced to chose one of the new product names. And the result would be that Voodooshield would be rebirth with a new name yay! And jmonge will be happy as a child yay again

 

Yeah, there were also the line of Voodoo video cards from 3dfx, remember those? I think the name Voodoo is quite common in the pc world.

 

Haha, the HP voodoo site has been offline for quite some time now apparently...I get an 404

 

Yeah, I see what you are saying, but being that the poll what set up to accept multiple votes, it is kind of helpful to see how VS compares to the other names.

We could do another poll and leave out VS, but we would probably only get 26 people voting on it again. And in that case, most likely SmartShield would win, although I liked pretty much all of them on the list, I really liked SmartShield. Hey, how about IntelliShield? Na, it is too hard to say. IntelliGuard? SafeGuard? I give up!!!! .