VoodooShield/Cyberlock

Sounds good, thank you. I had to redo some of the code for the Settings since XP was having an issue. Hopefully this will fix this error for Win7 also.

 

Yeah, this is the CPN issue that we are working on, hopefully it will be fixed soon! Thank you!

 

Yeah, I am having a similar issue with Firefox, but only on 64 bit systems. Once we figure out the bug in the Create Process Notify 64 bit dll, I am hoping this will also fix this issue. Thank you!

 

Thank you for letting me know, I just tried to reproduce this error, but was unable to do so. Here is what I did:

I just "calc" into one of the 6 boxes, put VS in Smart Mode, then exited VS. Then I started the Windows Calculator, and then started VS. VS started in Smart Mode / ON. Do you have just the process name of your email client, without the extension, listed in the box? Does this only happen on startup? If so, I can tell calc to start on startup to see if that makes a difference. Thank you!

 

OK, I believe the CPN issues are completely fixed, along with the XP issues. I am going to do some more testing and release another version within a day or so. Hopefully everything is perfect this time .

 

Looking Good Dano!

Daniel

 

Thank you TH! I am assuming that you are running VS on a 32 bit system . It works great on 32 bit systems, and I think we finally figured out the bug in 64 bit systems. How was the MVP Open Day?

 

Hmmm, it turns out that 32bit dll's go in the C:\Windows\SysWOW64, and 64bit dll's go in the C:\Windows\System32 for 64bit systems. Anyway, the problem is fixed, I am just going to do some more testing and wrap everything up. Sorry for the inconvenience this has caused... it was 3 additional weeks of frustration for everyone. It turned out that the code was fine... the dll's were just in the wrong place .

Here is a link that explains it a little better. My favorite comment was "Ran into this today too ... so confusing - Glut 32-bit dll goes into /SysWOW64, Glut 64-bit dll goes into /System32. Someone should write that down. On the internet."

http://stackoverflow.com/questions/...and-32-bit-dlls-to-syswow64-on-64-bit-windows

 

Does dll location have anything to do with my enumerated problems discussed, and pertaining to my 32bit XP OS ?

 

It shouldn't but I have been working on the XP bugs as well, so they should be fixed also! VS is no longer blocking the Windows Picture and Fax Viewer or the clock, at least on my test systems. And I believe the bug with the settings is fixed as well. I will go back through the posts here and make sure I did not miss anything. Thank you!

 

Below is a post from Jonesome from Stackoverflow giving another method to use from the same link you listed above. Maybe one method works better than the other depending on what task your application needs to perform. I can't speak for the validity of his recommendation since i'm no coder, but I thought it would be worth looking into as well. I know most security applications I use do have most of their dlls in the Program Files directory. I would try switching to the different folders first as you mentioned. I'm looking forward to testing this next build after the changes are made to the location of the dlls.



I should add: You should not be putting your dll's into \system32\ anyway! Modify your code, modify your installer... find a home for your bits that is NOT anywhere under c:\windows\

For example, your installer puts your dlls into:

\program files\\

or

\program files\common files\\

and then sets a registry tag :

HKLM\software\ -- dllLocation

The code that uses your dlls reads the registry, then dynamically links to the dlls in that location.

The above is the smart way to go.

Depending on the content of system32, and its ilk, is dangerous, and, in a sense, evil....

Post by Jonesome on stackoverflow http://stackoverflow.com/questions/...and-32-bit-dlls-to-syswow64-on-64-bit-windows

 

The next beta, will tell us whether those things are fixed.

 

Yeah, I can try to put them in common files too and see what happens. Although, the examples that I have seen that use this method from Microsoft, put them in the system32 and syswow64 folders, but I just did not realize they were reversed . I am not sure why he is saying to not put dll's there... that is what the folders are for. Thank you for the input. I will try it in common files and see what happens!

 

I know, it has been a rough 3 weeks . I think if I had a team of developers working with me all of the time, it might go a little better. Although, I think overall we are in great shape! Thank you!

 

Yes the program is there without extension.

Only happens on start up but not everytime

 

No I'm using it on my Win 7 Ultimate x64 and what Bug is there in x64 for can test it? As I don't see anything wrong at this time. And the Canadian MVP Open day was great!

Daniel

 

I see, which email client is it, "The Bat"? If so, I will install and test it. Thank you!

 

Well, the bug is kind of hard to describe and it does not seem to appear on every computer. Also, it is extremely intermittent, so it is hard to test. But the main thing it does is that it will basically just block everything, even the task manager for example. Then if you right click and exit out of VS, all of the programs that you tried to launch while VS was ON, will all launch immediately. But I think it is responsible for a lot of little issues. I have not seen any of the bugs ever since I changed the location of the DLL's, so hopefully it is resolved now, and I will post a link to the new version in a minute. Thank you!

It looks like you guys had a great time at MVP Open Day, very cool!

 

I just found another bug, I will repost the new version soon.

 

Hi Dan

I am running Win7 64bit...so can certainly test out the fix.

Baldrick

 

Nice picture TH....Canada is back! First hockey (Montreal) and now baseball (Toronto).

 

Cool, thank you, here it is if you want to try it, I would uninstall the old version and reboot first. The CPN dll error that was causing VS to be blind to child processes is fixed. I really, really thought it would fix the other issue with VS starting to block everything out of nowhere, and not prompting or showing a balloon. Then when you close VS, all of the programs you tried to open (that VS silently blocked), open all at once. That is the last remaining bug... I will track it down asap. Well, there is another bug that TH found... VS does not save its settings unless you right click and choose exit. So if you reboot your computer, it will not save certain settings, like user options, email address, password, etc. But it is a super easy fix... I just have to tell VS to save settings after, for example, the registration screen closes, etc.

http://www.voodooshield.com/freeoffer/Install VoodooShield.2.09 beta.exe

 

Boooo! Canadiens!

 

Only, noticed that when I rebooted to complete the VS install, that MBAM tray icon was missing. I only got MBAM reinstalled about nine hours ago, after having had problems with it, recently.





Windows Picture and Fax Viewer only opens when I disable VS, still.

 

Hehehe, thank you, I needed a good laugh!