View Full Version : Beta 5.0 and ZoneAlarm Syute 7.0.302
tig2020
01-30-2007, 04:33 AM
BSOD at boot if ZASS 7.0.302 is allowed to start with windows xp pro sp2
The above captioned programs do not work well together - if beta 5.0 is started while ZaSS is running then excessive cpu time (100%) You can run one or the other program but you can't run both at this point. Screen and all other function become very very very slow. Beta is not playing well with nvidia desktop manager 6.14.10.9145. System will hang and/or become so slow that the computer becomes usless.
ZoneAlarm Security Suite version:7.0.302.000
TrueVector version:7.0.302.000
Driver version:7.0.302.000
Anti-virus engine version:3
Anti-virus signature DAT file version:20070129205000
Anti-spyware engine version:5.0.162.0
Anti-spyware signature DAT file version:01.200701.875
AntiSpam version:4.9.1.8203
Windows XP Pro Sp2
AMD Athlon 64 FX 60 X2
Mobo - Asus A8N32-SLI Delux
Memory - Cosair Matched 2gig
Simon Clausen
01-30-2007, 04:47 AM
Thanks for the report.
Strange, I tested this myself and it worked fine (screenshots and details in another thread), we'll push this back to QA to investigate further. Perhaps it's a combination of things causing the problem.
Apparantly, according to some forums, the Kaspersky in ZoneAlarm is causing problems with a lot of security software.
Simon
tig2020
01-30-2007, 02:27 PM
If I don't allow either prog at startup and then start in sequence, SD beta 5,nvidia desktop manger and then ZASS 7.0.302 (in that order) all seems to work well. Additionally, onguard protection showing as limited - is this because SD anti-virus not installed and/or run scan at windows startup disabled? Using ZASS 7.03 antivirus.
tig2020
01-30-2007, 02:46 PM
If I don't allow either prog at startup and then start in sequence, SD beta 5,nvidia desktop manger and then ZASS 7.0.302 (in that order) all seems to work well. Additionally, onguard protection showing as limited - is this because SD anti-virus not installed and/or run scan at windows startup disabled? Using ZASS 7.03 antivirus. If I start beta5 after my ZaSS is up - crashes my system:rolleyes:
Menorcaman
01-30-2007, 07:16 PM
I too am having problems with SD 5.0 Beta and Zone Alarm Security Suite 7.0.320.00.
Installing SD5 Beta with ZASS running in the background cause system to reboot near end of install. After system has rebooted into Windows, starting SD causes the ZASS event warning shown in attachement 1. Choosing "Allow" causes the system to reboot again. If I choose "Deny" SD seems to start OK. However, if I then opt to shutdown SD I receive the error message shown in attachment 2. After this the SD system tray icon contains a red X and attempting to restart SD results in the error message shown in attachment 3.
If I uninstall ZASS 7.0.320.000, installing and running SD 5 Beta proceeds without a hitch.
Regards
Win XP Home SP2 + latest MS updates
Athlon XP 2600+ (Barton core)
2 X 512MB DDR RAM
tig2020
01-30-2007, 10:46 PM
Yes, I see you were/are having the same problems that I did. First, it is not necessary to uninstall ZaSS before install of SD beta. Kill the startup feature in Zone, reboot and then install XD beta.. Then see my reboot and boot sequence with all progs installed. I t is kind of a pain but hell, I am very glad just to have SD working again. The prob as you have seen has been reported and I feel certain that they will get it resolved. Have a great day
Menorcaman
01-31-2007, 09:20 AM
Yes, I see you were/are having the same problems that I did. First, it is not necessary to uninstall ZaSS before install of SD beta. Kill the startup feature in Zone, reboot and then install XD beta.Indeed, I had already tried that but as soon as I started SD after enabling ZASS again the same problems I reported above reoccurred.
Regards
Amaspain
01-31-2007, 10:27 AM
SD also blocked my ZoneAlarm from downloading it's anti-spyware updates
tig2020
01-31-2007, 06:41 PM
Just discovered that I did not have my startup guard enabled. Once I enabled that the whole system went bonkers - as in absolutely to a crawl. Disabled that feature and all returned to normal except for my opera. Something about opera and SD beta. They just don't play well after that start guard has been enabled and even more one I disabled it opera is still not working properly. Reboot in order here. Hmmmmmmmmmmmmmmm
Support
01-31-2007, 06:57 PM
Amaspain and Tig2020,
Thank you for letting us know about the problem that you are experiencing. This is just to let you know that we have escalated this issue to our Technical Support Department and will advice you with the solution as soon as possible.
Regarding issue with Opera browser, you can see thread http://www.pctools.com/forum/showthread.php?t=44960
tig2020
01-31-2007, 07:27 PM
It is the onguard protection that appears to be causing the instability - if off all is well and if on all hell breaks loose. I did have this activated prior to the update this morning and all seems to have started after that update. Love this program but daaaaaaaaaaaaaayum this is a little frustrating. But then again it is in beta- LMAO
robst247
02-15-2007, 04:15 PM
I'm having the same problem (reported above) after recently updating to ZASS7.0.302.000. Every time I try to run or install SD4.0 I get the dreaded BSOD :mad: with the following error message:
STOP: D0000144 Unknown Hard Error
See this post (http://www.castlecops.com/postp675255.html) and this (http://forum.notebookreview.com/showthread.php?t=99651) for evidence of a possible connection with Kaspersky Anti-Virus (which is integrated in v.7 of ZASS).
I can run either SD4.0 or ZASS7.0, but not the two together.
Support
02-15-2007, 04:23 PM
Tig2020 and Robst247,
Thank you for this extra information.
I have escalated these extra report's to the Technical Support team.
They will respond to your query soon.
Kind regards,
Nicholas
PC Tools Support Services
AChen
02-16-2007, 04:35 AM
I'm having the same problem (reported above) after recently updating to ZASS7.0.302.000. Every time I try to run or install SD4.0 I get the dreaded BSOD :mad: with the following error message:
STOP: D0000144 Unknown Hard Error
See this post (http://www.castlecops.com/postp675255.html) and this (http://forum.notebookreview.com/showthread.php?t=99651) for evidence of a possible connection with Kaspersky Anti-Virus (which is integrated in v.7 of ZASS).
I can run either SD4.0 or ZASS7.0, but not the two together.
Hi robst247,
The developers are currently investigating this. Will provide you with more info asap.
Peter G
02-19-2007, 11:46 PM
I too have experienced a conflict between Spyware Doctor 5.0 beta and ZoneAlarm Security Suite 7.0.320.000. Any attempt to turn OnGuard Protection off while ZASS is running, causes SD to hang.
AChen
02-20-2007, 01:19 AM
Hi Peter_G,
I have escalated this and we will investigate this further.
Will fill you in once I receive more info.
Saxel
02-20-2007, 06:35 AM
Please see Zone Alarms particularly unhelpful and arrogant response to this issue its this attitude which lead me to stop using ZA a while ago, the ZA incompatibility issue seems to relate not only to SD but a number of other widely used programmes & utilities.
http://forum.zonelabs.org/zonelabs/board/message?board.id=inst&message.id=63509&query.id=64213#M63509
Dave
awesome1
02-20-2007, 04:44 PM
If you look at Zone Labs forum at the moment most users are experiencing major problems with ZoneAlarm Security Suite version:7.0.302.000! The Antivirus is no longer working properly and the engine version is chaging by the hour when it should simply say AV Engine version 3! It is also scanning up to 200,000 files in 60 seconds :confused: !!
I am one of these with NO response from Tech Support so for now I have turned the AV off and am running SD 5 Beta 5 with Antivirus on and all is well!
AChen
03-02-2007, 02:25 AM
Hi Guys,
Just to let you know that the conflict with SDv5 Beta and ZASS has now been resolved.
Please download the latest version - Spyware Doctor Beta 5.0.0.165 (http://www.pctools.com/spyware-doctor/beta)
If you are having any problems with SDv5 Beta and ZASS, please let me know asap.
Menorcaman
03-02-2007, 06:05 PM
Thank you. This latest beta appears to have solved my previously reported problem. So far the only fault I've found is that of some incomplete text in the Scan Setting screen. See attached image.
Regards
AChen
03-04-2007, 11:41 PM
Hi Menorcaman,
Thank you. This latest beta appears to have solved my previously reported problem. So far the only fault I've found is that of some incomplete text in the Scan Setting screen. See attached image.
Regards
Thats great to hear :)
Regarding the incomplete text, could we please get the size of your font as it appears that the font is not the usual size. Once we receive this information, we will investigate this further.
Menorcaman
03-08-2007, 10:11 PM
Hi Menorcaman,
Thats great to hear :)
Regarding the incomplete text, could we please get the size of your font as it appears that the font is not the usual size. Once we receive this information, we will investigate this further.Hello Achen,
My Display Properties are as follow:
Screen Resolution = 1280 x 1024 (19" LCD monitor native resolution)
Display DPI setting = Large Size (120 DPI)
Font Size = Large Fonts
I have found two other cases of missing or incorrect text. Please see attached screenshots.
Best Regards
Jitney
03-08-2007, 11:34 PM
Me too! Screen res = 1440x900, 120 DPI, and 12 pt font. My screens look identical to Menorcaman's.
AChen
03-09-2007, 01:18 AM
Thanks for the info.
We have looked into this and there seems to be a bug with SD if you set the DPI to 120. For it to be displayed properly, you will need to change the DPI setting to 96.
Please be assured that this does not affect the functionality of SD, however, leaving the settings on 120 will not display the text correctly on SD. We will implement a fix for this shortly.
Menorcaman
03-10-2007, 02:44 PM
Hi Anthony,
I realise it's a minor cosmetic bug that doesn't impact on SD's functionality. However, with the proliferation of hi-res screen displays, 96 DPI isn't really an option for those of us with less than perfect eyesight. :) Anyway, no worries - I will just await the future fix.
Best Regards