This link to the outpost forum pretty much sums up the current state. http://www.agnitum.com/forum/showthread.php?s=&threadid=6529 sounds like we're going to have to wait a bit longer.
I really like Outpost but can't switch over to it because of this "known issue": I tested tons of Firewalls, all except ZoneAlarm suffer from this problem... so I'll have to wait for v2
root seems to be having problems on his win2k machine. Maybe he will now go to win XP? I have applied three time to beta version 2 and never even got an e-mail in return. I am guessing you really need to be an elite computer user to be on this beta team But then again, I am not russian. root are you russian? or a MOD at Outpost forum? the link states , only russians or outpost forum mods got the Beta 2.0
white blood cell ? you mean all this? GPF during PC shutdown under Win95 Outpost Service Terminated’ in event viewer under Win2000/XP Outpost freezes during intensive UDP traffic (ex. online games) Unauthorized stopping of Outpost Firewall service is possible. Norton Antivirus and Outpost causes a Blue Screen Error on some configurations. PC-Cillin and Outpost causes a Blue Screen Error on some configurations. VMWARE and Outpost causes a Blue Screen Error on some configurations. VPCNET and Outpost causes a Blue Screen Error on some configurations. Outpost causes a Blue Screen Error on some configurations under Windows 2000/XP. Outpost causes a Blue Screen error after a resume from hibernate in Windows 2000/XP. Excessive memory and (or) CPU consumption when many connections are established or after hours of intensive data exchange. Outpost silently quits without an error message. Errors during startup ‘Error Loading driver 1056’ (or driver 1058, or 3, or 5, or 80) ‘XXXX Device driver could not be loaded’ error on startup After installation I see a “tower” icon instead of the default Outpost icon in the systray. Outpost does not work after reinstallation of TCP/IP stack in Windows. ‘DNS Bufferlength >= 1024’ error on startup. ‘Agnitum Outpost: Invalid Handle’ error on Win2000 or WinXP startup. Outpost service fails to start under WinNT/2000/XP Application functions not work properly Outpost service doesn't stop during PC shutdown under 2000/XP. No application integrity check (MD5) when Outpost runs without GUI. The Content and Active Content blocking plug-ins do not block some content. The advertisement blocking plug-in does not block some banners. Active Content does not block JavaScript “file://”. Outpost does not check if access to remote port 53 is a proper DNS request or not. Debug plug-in shows a lot of [FIN ACK] packets after disconnecting from a remote host. Attachment filter does not rename attachments having non-English file names. Active Content does not block JavaScript “onload()”. Outpost incorrectly handles some long filenames. Outpost allows all network communications before its GUI loads. Attachments filter does not rename attachments if Netscape's e-mail client is used. Wrong byte count for NetBIOS connections. Attachment filter does not rename attachments if Mozilla's e-mail client is used. DNS Cache does not work under WinXP. Outpost cannot correctly perform an integrity check if the app name contains invalid characters. False detection of “Short Fragments” attacks by the Attack Detection plug-in. False detection of “My Address” attacks by the Attack Detection plug-in. Incorrect handling of peculiar fragmented packets. Local connection logged with 'Undefined rule' or 'Unknown' as a reason Connection logged before the GUI start is logged with 'Undefined rule' as the reason. Activating ‘Run application’ action in rules creation dialog does not launch the application. Same Application listed twice in the Options->Applications dialog. Activating ‘Report It’ action in rules creation dialog does not report the connection. Loss of Outpost settings if PC crashes/freezes. Outpost window is visible in taskbar regardless of “Minimize to systray” setting. Outpost has errors on NT/2000/XP unless you have Admin privileges. Outpost settings are not saved automatically on some configurations. Outpost has errors on NT/2000/XP unless you have Admin privileges. Trashcan does not work with Opera. Design flaws Outpost cannot filter localhost connections Outpost cannot filter localhost connections. Outpost cannot create rules for two or more applications having the same name Outpost cannot create a rule with a symbolic remote host name if that remote host has several IPs. Outpost does not show licensing information (expiry date, type and owner). Graphic User Interface Errors “Outpost Firewall on the Web” links in upper menu do not work. ‘Cannot find the *.HLP file’ error when click on ‘?’ in Outpost dialogs. Multiple listing of ‘NetBIOS connections’ in My Internet tree. ‘Learning mode’ as a ‘Block reason’ in Blocked log. “Something is blocked” errors Passive FTP mode blocked when using some clients/servers. Outpost Firewall blocks all traffic on ICS gateway under Win2000+SP2(3)/XP Outpost causes some web page to be blocked. Outpost blocks all traffic because it fails to determine the correct IP address. Outpost blocks everything after a resume from hibernate in Windows 2000/XP. Update and registrations errors ‘Fault to create VBScript engine’ when running Agnitum Update under Win95 ‘Can't load aupdate.dll’ when running Agnitum Update under Win95 Outpost is not accepting valid registration key under Win2000/XP «Overwrite?» Error message when running Agnitum Update Agnitum Update constantly queries the registry Other Security Leaks. Exiting Outpost is not password protected. ‘Could not open (or find) INSTALL.LOG file’ error during uninstall of Outpost. Incompatiblies Outpost block everything after ‘Fast User Switching’ under WinXP. When no user/admin logged under Win2000/XP Outpost runs in Allow Most mode. Outpost can work incorrectly if installed on a 3rd party NAT-proxy (ex: Sygate Home Network). Running Outpost with other firewalls results in system instability. Install/Uninstall issues
Controller, you know I'm a Mod at Agnitum. SuperMod as a matter of fact. I'm not Russian and don't speak the language, but I used to drink a lot of Vodka before I quit drinking. I am having trouble with version two, but I think its because I'm using Wingate for ICS purposes. Even with the Wingate firewall not running, and Wingate not even loaded. Tomorrow I am going to do a fresh install of 2k I think and start adding programs to see what the problem is. It runs great on other machines with Win2K. The Mods only have version 2 as a present for their hard work. We cannot report problems at this time. I understand Mikhail wanting the Russian speaking beta testers to try to clean up the big problems first, because his coders do not speak English. It really doesn't look like its going to take a lot more debugging, but that could change as the English speaking testers start running it with different programs than the Russians use (maybe). As for XP. I would not install that program again if M$ paid me to. They are going to find it very difficult to terminate supporting Win2k I think. It would not be a popular move and would surely drive thousands to Linux or similar. Last, it should be noted that the list of problems you posted was pretty much a summary of all reports, and in many cases may have been only on one or two machines. They did fix many many bugs and all of the serious ones in version two. I am currently using version one with Wingate and it serves me very well. When I combine that with SSM, I feel as safe as a person can get with the limitations of Winblows in mind.
I to really like outpost but can't change from ZA because I use fast user switching. I'm hoping to take advantage of my free, lifetime outpost upgrades very soon. Of course I quit holding my breath a long ago.
Well, I have good news and I have bad news. The good news is that I found out what was driving my CPU to 100% when I surfed. The bad news is that it is AVP 3.5. With just the scanner installed, the cpu goes to 100% when I surf. With the monitor installed, the CPU goes to 100% and stays there. That is not a good thing. However, I'm sure as soon as I can start submitting bug reports, Agnitum will find the problem. This type of thing is to be expected with beta versions, and since I now have it running ok, it looks to be a great firewall. My loyalty lies with Agnitum as we debug this version and I will be doing most of my work there, but I will try to keep any interested parties informed here at Wilders.
Glad to hear your up and running root. Please keep us informed, I don't like to install buggy software so I pay a lot of attention to forum's like this one to know when the kinks have been worked out.
