3.5 update is a pain in the ...
Btw, the same thing happened during the last update ... sad thing is that I forgot to write the solution down .... Aaaaaaahhhhhhhhhhhhh :evil:
It is so important to first unplug from the Internet, shut down all real-time apps, including your current Outpost fw version, un-install the current version, re-boot, shut down all real-time apps again (they usually auto-launch after the pc re-boots) run something like CCleaner just to get rid of any stray garbage, then install the new version.
Also, check out the info under Upgrading in this link: http://outpostfirewall.com/forum/showthread.php?t=16486 for more installation tips.
...which does not prevent me from being rash as I`ve now tracked down the 0x2747 error to a winsock problem. The rest stands, though.
I assume that you shutdown the previous before installing over the top? When you do this it should say that it successfully uninstalled and please restart your PC then on restart it gives you three choices....i chose the 3rd one because of the config i had from previos, and finally it asks that you run the spysweeper...
...I dont know how many people know this or haven't noticed it, but regardless of whether or not you run the spysweeper if you hold the mouse pointer on the tray icon you will notice it shows Local and not your IP address (assuming it does this with everyone), if it shows Local then disconnect from the net because you are open to all. At this point you can run the scan then restart the PC (or just restart without doing scan) ....it will then show your IP address when you back in windows and if you check with www.grc.com or PCFlank then you can make absolutely sure that all is okay.
The same thing happened to me, I shut down all instances of Outpost, yet the wizard was stuck after each reboot with "The old version of Outpost was detected, please un-install it first".
Next I proceeded to delete the Outpost Folders manually and installed the new one and next I had the newly installed Outpost crashing with an unspecified error, asking me to do an install /u - reboot - install.
After that i got it working, only to see that my internet applications behaved erratically. DC++ would often not connect, giving me "unknown error 0x2747" (which is "no buffer space").
Then I uninstalled the new version and re-installed the previous one (not without more problems) and found out that the backup configuration where I had pointed the new version to had been converted in its directory instead of having been copied to the Outpost folder and was thus unusable for 557. I`m only glad I had a double backup in the Agnitum Shared folder.
To sum it up: I never had big gripes with previous versions, but new version is a steaming pile of *beep* and NOT ready for public consumption.
Btw, I earn my money as a computer tech since 15 years.
#If you have any other info about this subject , Please add it free.# |
January 6th, 2009 - Posted in hznj.com | edit |
