Subj : Re: Firefox ?
To   : Holger Granholm
From : Mike Luther
Date : Wed Apr 06 2005 09:51 am

Hej!

 HG> Thank you Herbert, Peter, Rich and Mike for the most valuable
 HG> advice/information regarding Firefox and other browsers.

 HG> I have read and saved all this information for futher investigation.

And in all that trash word post I forgot one of the most important files you 
might want to pick up re trash!  Although it can on rare occaisions lock up 
your CPU 100% and you'll need to kill it with SETKILLFEATURE or MOLE or 
whatnot, you really ought to try PRIVOXY.

Using port 8118, even the standard configuration feature now works darned good 
at munching all the visual clutter when you use your browser.  Look for it at:

     http://www.privoxy.org

Version 3.0.3 stable works and installs just fine except for a rare instance 
when there is a major error thrown by a poorly written site you may hit.  It 
looks to me like when you shut down MOZ after hitting one of these rare site 
mungs, the proxy filter keeps looking for the response to the site past the 
error, leaving a thread open in it which should have been squelched by the drop 
off of MOZ.  That can contaminate serial port applications if some rare 
coincidental I/O or even TCP/IP I/O in other tasks is taking place at just the 
right moment where PRIVOXY's thread gets lost.  The only way out is to shut 
down PRIVOXY and re-open it.  It isn't system fatal, but can lead to failure in 
the other comm port applications via DOSCALL1.DLL or non-trapped failures in 
other OS/2 native TCP/IP applications.

I've worked with the reponsible party for the OS/2 drop of PRIVOXY and much of 
this is cleaned up in 3.0.2/3.  But as you might imagine all the parts to this 
are very complex and hidden that I see in the complex box top operations I use 
here.  I'm sorta positive you could avoid this if you could spawn PRIVOXY just 
before a session of MOZ and kill it afterward, say in some kind of a .CMD file 
or whatever.  But haven't done that yet because of the inter-related lockup 
issues that rarely are there internally which can be killed by killing it 
manually and then simply re-opening it with MOZ running.


In later OS/2 operations you add the following as the first line in your 
CONFIG.SYS file:

     SET SCKILLFEATUREENABLED=1

When you hit the applications tab on the WPS for open applications with your 
CTRL KEY pressed, you can kill a running thread by hand this way. Very useful 
for doing what I used to use MOLE for and I guess the other applications like 
WATCHwhatever are for.

The PRIVOXY file is also on my BBS in the OS2DEV area along with two other 
related files that helped with earlier versions for filters:

       3-04-04  6:12a   1751100      0  privo303.exe
      11-30-03  8:22a      8540      0  privofil.zip
       7-19-03  2:31a     28915     29  privoxy.cfg

The standard configuration filter now with the 3.0.3 version is pretty good for 
most purposes now.  It comes set up for use with the LOCALHOST version on your 
LAN that is normally enabled.  But you can set it up to use a common private 
address in the 192.168.1.## situations behind a router or whatever.   Your 
setup in MOZ is normally simply to set it up in the proxy data as the standard 
127.0.0.1 address with a port of 8118 and for the first two lines in the 
configuration pane.  Away you go with the standard configuration.

If you wanna see what it is worth try looking at www.debka.com, the Israeli 
intelligence spill over file for the middle east, with and without the proxy 
turned on, chuckle!


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)

.