I still have the problem, that Outpost 2.0 don'T start at 80% of the starts of Windows. I have tried the tip in the Outpost FAQ to run the intall.exe, but this dosn't solve the problem. I've startet a support request to agnitum but I dosn't get any answer! :mad:
A reintall of Outpost (after a complet deinstall of the Firewall and a regclean) dosn't help, too (every Antivirprogramm was deactivated during the install).
Because the free Outpost 1.0 don't show this problem I have uninstallt Outpost 2.0 and use once more Outpost 1.0. It is better to have less securety as a Firewall I can't depend on.
I would be lucky for every tip to solve the problem withs Outpost 2.0.
PS.: I use Windows XP Home Edition with Service Pack 1.
I have configurate Outopost 2 to start normal at the boot up (not in the background).
During the boot up (at about 6 from 10 boot ups) I got the Error #0000002. The Outposticon in the Systemtray is visible, but if I open the Outpost window, the firewall dosn't work (No active connections or aplications are shown, even if I'm in the Internet).
When shutdown outpost and restart (without rebooting windows) it, I get the same error. I've tried the tip running the install.exe in the Outpost dir before rebooting, but I get no effect. After several reboots Outpost starts without the problem, but only one reboot later the same problem might occure.
If I configure Outpost to start in the backgroung, I have the same problem. So I think the problem comes from the outpost service.
regards
Frank Lauer
Hi Frank,
I don't understand the problem. Is it that outpost isn't starting when you boot up? Sometimes? always?
Please explain what is happening.
Chris
I've thougt once more about the problem. The strange thing is, the Outpost 1 Free don't have the same Problem. Sometimes Outpost 1 dosn't start, but after the system is runnig I can start Outpost 1 Free by hand. If Outpost 2 shows the error 000002, then it isn't possible to start it later by hand. It seems to be the same problem, but outpost 1 Free don't react as critical as Outpost 2. The big question is, what is the differens between otpost 1 an 2. Have anybody an idea?
Make sure to let us know. I'll bet it is an AV or AT program.
Chris
Unfortunately, the tests brings no result. I have started Outpost while I have deactivated all other autostart programms (registry started or in the autostart folder). The problem wasn't solveld. Maybe, that some of the automatic started services cause the problem, but I have not the expirience to make same same test with the services. At the moment I will unsistall Outpost 2.0 and reinstall Outpost 1 Free, because it don't have the same problem.
Maybe I try Outpost 2.0 once more after my next reinstall of Win XP.
regards
Frank Lauer
Good Idea. I will reinstall Outpost 2 on the weekend and deactivate step by step every other starup application. I hope I will find the one which makes trouble with outpost.
Thank you
Hello,
has anybody an idea to solve that problem?
regards
Frank Lauer
Hi,
I have the same problem.... :-(
Greetings
Georg
The problem sounds like a boot priority problem. 2 or more programs trying to start at the same time. Usually happens with firewalls and AV, AT programs as they work at a very low level in the OS. The problem started getting a little more serious with WinXP. You could try a little program like Startup Cop (http://www.windows-startup-cop.com/) to control the starting of apps.
That may solve the problem for you.
Chris
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home
|
PRINT
Add to favorites