Hi tbbeta'ers, My apologies in advance, but I am a TBBETA DIGEST subscriber so I fear any replies I give will screw up a lot of people's threading. I may be a bit verbose in this submission (my second ever) attempting to preempt potential questions about what I did procedurally to lead up to my dilemma. I am also not sure whether this is a ZoneAlarm Pro issue, The Bat! issue, or a combination of the two. Here are some basics about my system:
Registered version of The Bat! (version and system specs in signature) ZoneAlarm Pro 5.5.094.000 - Registered version I was running along and updating my betas perfectly up through the stable :) version of TB 3.5 release. I installed updates periodically over time using both simple replacement via RAR contents -- and complete installers via the MSI's. The most recent installations were as follows: 3.5 Release Version installed via MSI 3.5.26 version installed via MSI 3.5.27 version installed via RAR contents replacing only thebat.exe and props.dll (the props.dll version was the same going from 3.5.26 to 3.5.27 btw) TB! application files are installed in the default C: drive path, and TB! data/working files are installed on my D: drive (a separate, physical drive). Typically, I let ZoneAlarm Pro automatically recognise the new version upon execution ... THEN set the "access" permissions for Internet to ALLOW and "server" permissions to DENY, and email permission of course to ALLOW. Why I deviated from this pattern, I don't really know! :P Upon replacing the props.dll and 3.5.26 thebat.exe with the 3.5.27 thebat.exe, and before running thebat 3.5.27 for the first time, I went into ZoneAlarm Pro's "Program Control" settings and removed the entry for thebat.exe 3.5.26 -- then manually added thebat.exe 3.5.27 and set permissions. When I looked down in the Program Control tab's "Entry Details" box in ZoneAlarm's window, I noticed that thebat.exe's version was reported either as 3.5.26 or 3.5 (but definitely not 3.5.27), I can't recall which. So, I manually removed the entry and again manually added thebat.exe ... which caused the Entry Details version to go back to the next prior version. I repeated this process a couple more time, each time noting that the version reported in the Entry Details was going backwards, although no other executables in the Program Entry tab suffered a similar fate. When I actually ran TheBat! 3.5.27, the HELP:ABOUT reported correctly that the version was 3.5.27, however my filters had rolled back to settings I used quite a long while ago. I am not sure whether the filters matched the settings I used corresponding to the ZoneAlarm Program Control Entry Details reported version or not. I uninstalled TheBat! via Add/Remove Programs -- keeping intact my working files and directories. There were two entries, one labelled TheBat! (Professional Edition) and one labelled TheBat! 3.5.26. I removed both, then reinstalled TheBat! 3.5 release version. I then RESTORED from my 3.5 release version backup all settings that were available via checkbox ticks. My filters came back up-to-date just fine. HELP:ABOUT reports the version as 3.5 ... but ZoneAlarm Pro is still reporting thebat.exe version as 3.5.27! oomph. Why did repeated manual additions of thebat.exe 3.5.27 to ZoneAlarm Pro cause regression of all of my filters and version number as reported in the Entry Details box on the Program Control tab of ZAP? I would be curious if you all think this is a ZAP issue or not. If so, I suppose I should move this over to the ZAP support forum. Thanks for any insight you may shed. Daniel -- Kindest Regards, Daniel Nelson, President Calderus Corporation MerchantIPS Services [EMAIL PROTECTED] GnuPG Public Key: <http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xADFE407E> Powered by The Bat! v3.5 Professional [POPFile] on Windows XP 5.1 Build 2600 Service Pack 2 - Antivirus scanned by NOD32 Enterprise. ________________________________________________________ Current beta is 3.5.27 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
