Well after trying all day and thinking ive got v2 stable i have to admit defeat.One minute it behaves well ,the next minute applications that are in partially allowed become blocked (and show as such in blocked logs) for no reason whatsoever.I even had the scenario of ICQ which was allowed preset rules being blocked and allowed at same time.Im going back to v1 which to be honest i didnt have much trouble with at all.It seems to behave erattically at any given moment and for no apparent reasons.One minute ICQ is allowed to connect.The next its being blocked as shown in logs even though it has preset rules afforded it.And it isnt just that application either.Its blocking browser at erratic times too.I hope there might be a simple answer that causes these things,but im of the opinion now that there isnt.I will be tryin v2 in a few months i think ,when maybe some issues have ben resolved (on98se at least).It may be a good idea for a link to V1 download be provided until V2 problems can be further investigated as many people would have lost that version with the v2 upgrade /install.
me
Ferri, the "Invalid page fault" message may be a result of having renamed the op_log.dll file (did you rename this rather than the op_data.dll file?) - several Win98 users have reported this as happening whenever Outpost or the PC is shutdown. This is now mentioned in the relevant FAQ (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=7392). Reinstating logging and trying a shutdown on Outpost would be a simple way to check this.
yup i found allow most mode works too ....but i dont like using that.I think you are correct that 98 seems to be getting most of the deeper problems.Im back to v1 for now and am quite pleased to see all those familiar plugins back too :).With 98 a dying OS i honestly think that it will be a long time in the sorting though as there seems to be some deep seated problems there....hope im wrong...but if im not i will still continue to use v1 for the forseeable future.
me
[QUOTE]Originally posted by MTDay
[B]@chrisclu - 98SE and AVG antivirus! - yes, me too!
One other point - during the fail...
In Rules Wizard - it ends up in blocked log, with the RULE as the reeason.
In "Block most", it's blocked, with the reason as block ALL activity
mtday..i had same problem as that initially.I also use avg and 98se.My problems seem to have stopped (at least the last 24 hrs firewall has been working perfectly).It could be one of these 3 things that has made it work.
1.Install the mdac /jet drivers as has been advised by posters
2.Before you install V2 over the top of V1 uninstall any plugins like debug ,http,blcokpost etc ( i forgot to do that in my first install of v2)
3.put your own isps DNS addresses in the global settings rather than the default as suggested by root.
In my own case and because im on dial up and dont need outpost to start with windows i also deleted the 2 registry entries (service /wait service) though if you are always connected you may need them left.
Universal RAM memory up graded, but failed! [Archive] - xda-developers::
23 posts[Archive] Universal RAM memory up graded, but failed! He could add, but OS can read it at all. he tried to many modules and also many way. but still
http://forum.xda-developers.com/archive/index.php/t-248985.htmlHOME |
After following the above i have had no problems for last 24 hours and i dont think im likeley too now as all the problems i had before were basically within a few minutes or when opening closing applications or when reopening outpost.
hope this helps.
me
Bassbag, some users have found that updating the MDAC (MicroCruft Data Access Component) and Jet drivers (as detailed in MegaHertz's v2 FAQ here (www.outpostfirewall.com/forum/showthread.php?s=&threadid=7221)) does resolve the "System" problem (like in this thread (www.outpostfirewall.com/forum/showthread.php?s=&threadid=7282)). Have you tried this? (doing a system backup would be prudent first though as one person reported Registry corruption after doing this update).
Hi paranoid...yes i have those updates.I can workaround most of the problems i had like the tds3 update.exe problem ,but the one thing i cant work around is v2 continually and erratically deciding to block applications at "system" with the same reasons(in reasons column) that are given when they are allowed under preset rules.It gets to be a pain when i have to continually remove apps and use preset rules again only for that app to be blocked again at the next boot or the next day(even though they are all in partially allowed).In v1 all i get blocked is ICMP traffic usually which is what i expect on my setup.In v2 im getting naviscope being blocked ,myie,yahoo messenger,icq all intermittently and even though all (except naviscope which ive given browser preset rules)have the preset rules.
me
Hi bassbag. Sorry you're having such problems. I think there are some problems with Win98 that are being worked on but I'm not sure about your specific issues.
Did you turn in a support ticket to Agnitum? When there is a bug involved, Agnitum Support will handle it.
hiya chris :)....
I start outpost with net launch and not with windows.Maybe thats why i havent had the shutdown issues that some people have had,although i have had many other issues that other posters have had.I can totally understand outpost working on yours and not on someone elses.Its down to setups ,components,configurations,programmes used etc.The list is endless really.At present it doesnt work correctly on my setup(erratic blockin of previously allowed applications)plus the windows protection error ..though i will say that it always achieved complete stealth and security when ive tested it including the leaktests.Hopefully the teething problems can be ironed out shortly.In the meantime im confident in the protection that v1 is giving me. :)
MySpace.com - Kujo [Tried but failed awesome!] - 20 - Female ::
MySpace profile for Kujo [Tried but failed awesome!] with pictures, videos, personal blog, interests, information about me and more.
http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendID=15350582HOME |
Have you tried to quit smoking but failed. Then why not smoke to quit::
Dec 29, 2008 Have you tried to quit smoking but failed. Then why not smoke to quit - $79 (www .AnyKineStuffs.net). Reply to: sale-972813655@craigslist.org
http://honolulu.craigslist.org/oah/bfs/972813655.htmlHOME |
me
@chrisclu - 98SE and AVG antivirus! - yes, me too!
And I have had suspicions that AVG may be one of the trouble points.
On the last fail - doing a FULL scan with AVG broght it back after several boots when it was bad - I believe that changes the way the on-access scan treats it, if there is a current full-scan database entry to verify it to, then I believe it ONLY verifies and doesn't actually have to scan.
One other point - during the fail...
In Rules Wizard - it ends up in blocked log, with the RULE as the reeason.
In "Block most", it's blocked, with the reason as block ALL activity
Not sure it's worth making it an official fault ticket, as my machine has been a bit touchy for a while - I've run memory tests, HOPING to find some bad bits, but no such luck!
Yeah! I think it's getting time to nuke it and start over and clean.
- and make a backup the moment all the essentials and relevant updates are installed!
Chrisclu Beta'd on 98SE, and since he can get here , it works...
but is 98SE throwing more problems than XP - as perhaps in V1, Xp issues semed to be more troublesome.
I'm running 98SE, and with V2 - it works, it doesn't work - when it doesn't, "allow most" usually works.
I shuffle the start order, and it works - NOW there's a thought....
I wonder if there's some multiple DLL versions somewhere, and it's a race to see which one starts.
For a supposedly deterministic system, the load order of the systray is not always consistent.
It's driving me round the BEND!
Still betan'g on 98 SE.
So of us three One doesn't work at all. One works sometimes and mine works always.
Maybe it is a timeing issue. I have disabled all start up items except AVG and Outpost. I start programs when I want to use them, not automatically at startup.
Chris
hi root :)...no i didnt turn in a support ticket.I bought outpost during the lifetime upgrades so anything like V2 is purely an extra benefit to me , and V1 works so well that im satisfied with that really.There seems to be many problems on my setup.Ive probably experienced nearly all other posters problems like the firewall suddenly blocking applications (using the "system" label) for no reason when they are in preset configurations.As i said i had icq showing in allowed logs and being blocked at same time.I also experienced the windows protection error.Something that i can in all honesty say that ive never had before.Funny thing is that id already shutdown and exited outpost and proceeded to to do a cyberscrub cleanup.The only thing i havent experienced is the shutdown issue.Even a clean install does not go smoothly as outpost is running (using 95% cpu) but theres no icon showing in system tray unless i reboot a second time after installation.Also trying to use update.exe (tds3) crashes outpost.I think that the reason as shown in my other post is that "system" once again blocks the update request while outpost pop up asks me to make a rule for it at same time.Im quite happy to wait a few months and try again then :) and keep updated here :)
me
Well at least the "SYSTEM" logging problem is solved. Now if everything else worked right! Chrisclu - you must either have a "virgin" 98SE setup or perhaps all the programs we have running an you do not is one of the reasons for the problem with OP. We DID notice that if we mark the log as corrupt and delete and create new on next bootup it seems to really help for awhile right after the next boot.
One more thing - are there any FAQs or info on the Component Control function? We noticed there are some dlls listed with some apps that are definitely not correct.
Yes, it's probably the running apps. I have only Outpost, AVG and RegProt running right now.
Close to virgin system because I take a drive image before I install anything. If it doesn't work right I restore the image. That way even a bad uninstall routine won't affect me.
I haven't seen a better way to keep a system clean.
Chris
Sorry Paranoid. I actually renamed op_data.dll. My memory is not so good as it used to be (sigh). I get the "invalid page fault" with op_data.dll renamed or not, if I try to exit windows without closing Outpost before. I've not had this error twice; when I "repaired and compacted" op_data.mdb (after shutting and opening windows, the next time I closed windows everything seemed correct), and when I marked the log as corrupt and delete and created a new one. I've seen this only once each but I'll try to reproduce it, although this days I don't know how many times I've rebooted my system trying different ideas (of my own and from this forum) to get rid of this problem but none worked until now. I've already reported it to Agnitum, also.
Originally posted by QSection
We DID notice that if we mark the log as corrupt and delete and create new on next bootup it seems to really help for awhile right after the next boot.
I've seen the same behaviour. If I create a new log, I've no shutdown problems the first time I exit again Windows 98SE. I've also seem the same if I open the log using Access and use the "compact and repair" option (somebody suggested this to make the log smaller).
However, I've tried to disable the log (renaming op_log.dll, as also suggested in the forum) and the "invalid page fault" I get every time I shutdown didn't disappear.
The good thing is that OP2 is performing well in my sistem :) , besides the shutdown issue. I also a small problem losing my previous rules, but as I posted before, I found a backup (done by the installation program) that allowed me to restore them.
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home
|
HOME