I am using XP, cable modem free version of outpost (latest). Last few days Microsoft tells me that I have just recovered from a serious error and the crash report thinks I am using Outpost Firewall Pro and to visit the website. Any ideas? I can only think that I did install Pro unintentionally and have since uninstalled it and reverted to the Free version.
hibernation can affect connectivity as well depending on how the network card is affected...
Yeah - cpme to think of it it could have been when I have sent it into hibernation - I'll try it one more time and then avoid it from now on. Thanks
I have a suspicion which I can't totally verify that there is some ACPI compliance problem with the OP kernel driver. I've experienced some difficulties with later versions which make me believe that there's some kind of interaction. It's not exactly straightforward but somehow the power settings, particularly hibernation, plus some other unknown conspire to make OP crash. Further, it doesn't happen consistently although that may be that that actual events that cause the crash aren't set up properly all the time. I know that doesn't help but maybe you can fiddle with your power settings some since V1 is a done deal and no more work will be done on it.
'subsequent versions' refer to the paid for v2.0 thru 3.5 which were released afterwards and contain the fixes to earlier problems (and some new bugs to fix in future ones as well). the free version is just the original full featured version one with the licensing requirement turned off. any fixes to problems in v1 are in v2 and beyond. there has been no further work to fix anything on the v1 free version and agnitum does not support it and there will never be any new v1.x. we do support v1 here luckily for users. we are hoping that agnitum will provide one of the now superceded version 2.x as the new 'free' version in the future, but we've not yet heard anything. you may have a look thru the v1 FAQ for help, but without any system logs or ms error codes our ability to help is limited... A Serious Error Suspected Mainly Caused By Windowsxp Rndis Driver::
Hi guys,I encouter a seriouls driver error and I suspected it is caused by Next Oldest · Windows XP Home and Professional · Next Newest
http://www.bleepingcomputer.com/forums/topic60319.htmlHOME |
hibernation can affect connectivity as well depending on how the network card is affected...How's does it do that? I hibernate my PC all the time and don't lose connectivity when it wakes up. What did I do to set it up right?
You know now that I think about it there have been instances where on waking up the PC required a reboot. I didn't think about the lease expiring. I'll keep that in mind and check that next time it happens. Thanks.
i think part of it may be the network card properties, nowadays they can be set to either, on hybernation or standby, stay turned on or to turn off to save power. leaving it turned on may keep the lease active, but causes a lot of network traffic as your pc confuses the system by not responding normally, turning it off saves power & cuts out the traffic but may cause lease problems. mine has some additional settings & a warning, see attached.
You know now that I think about it there have been instances where on waking up the PC required a reboot. I didn't think about the lease expiring. I'll keep that in mind and check that next time it happens. Thanks. minidup error::
minidup error : Archived from groups: microsoft.public.windowsxp.newusers () I have emachine with win XP home edition,5.1/2600 dial up,keep getting serious error r
http://www.tomshardware.com/forum/103074-45-minidup-errorHOME |
Error beep from every item on start bar ? ?::
Error beep from every item on start bar ? ? : Hi all, , Heres a strange one for ya all ! !Have an AMILO A1650 laptop with xp pro on it and its a few years old now
http://www.geekstogo.com/forum/Error-beep-every-item-start-bar-t220265.htmlHOME |
hi nigel,
please read Read this First (http://www.outpostfirewall.com/forum/showthread.php?t=7209) as it contains guidance on what info you can add to help us help you. the 'free' version is rather old now and has some bugs that have been fixed in subsequent versions, tho many people who are still using it have no troubles. info on your system inc. system log & event log info, any OP logs that may apply, and more info an any MS errors, error codes, error text, etc. may help.
there is a thread here on manually deinstalling outpost if you wish to try that, and reinstall OP v1. please note the update function in v1 will install the pro version which will only be a 30 day trial, so be careful not to.
if the error is repeatable, any info on how & when it happens, what you were doing, etc. may also help. if it was a one-off occurance, it may be ignoreable.
The 'serious error' only came when I switched on the machine or it woke up from hibernating and there is not other info except that MS tracked it down to a Outpost and just gave me your website to go to. It has happened about 3 times in the last couple of weeks. I will look for the uninstall thread and re-install 1.0.1817. My version of oupost.exe is 1.0.242. You mentioned subsequent versions but Ireckon I have the lastest.
Nigel
on an adsl or dialup & with a recent bios, probably wouldn't, or on a small fixed ip network: on a LAN (or cable i suspect as it appears to be a big loosely controlled lan) i've seen some laptops refuse to connect when awoken, required a reboot or an 'ipconfig /renew' to get it's lease back. they didn't seem to like suspend either. might have been due to losing it's dhcp lease while it was sleeping, then trying to use the same ip when it woke up to discover someone else had snatched it meanwhile. we had fairly short lease times. we also seemed to have some troubles with some network cards and the autodiscovery of the lan speed on reawakening.....
 Where's The Advantage In Windows Genuine Advantage?
 Stocks Bounce After S&P Joins Bear Market
|
HOME