Re: [proxyTools-users] New Windows Localproxy

[wayne <wa...@ny...>]

> From: Michael Foord <Mic...@tb...>
> To: "pro...@li..." <pro...@li...>
> Subject: [proxyTools-users] New Windows Localproxy
> Date: Fri, 06 Dec 2002 08:41:39 +0000
> 
> Immediate reaction on extracting the distribution :-

I'm just back - sorry for the late reply.

> It doesn`t look at the configuration files (can`t see them) from the 
> directory it is run from

True, so they have been included in the distribution. If you have 
your own config file, you'll need to copy it into the new directory.
LPbin can't really know where you have them.

> It doesn`t pick up the authentication environment variables

Ahh, that's a new report. Presumably you can use the authentication 
mechanism though to work around, right?

I've just checked mine, and it finds any environment proxy ok.
How do you set those variables? 
Are you using win9*/ME, or an NT series Windows?
If you just start a command shell and type 'set', do you see the 
auth variables?

> The readme.html documentation on installing and running is still for the 
> perl based version

True. Was there some point that was misleading? I took a quick look 
to see where there might be problems, but basically I though it 
all applied pretty well to both.
Corrections/suggestions are welcome.

> The following was reported from running autoconfigure : (The tests 
> master.pl ran got an A - authentication unsurprisingly)

You mean statProxy, I guess.

> I did delete some of the configs I neevr use such as the KSA ones etc - 

No problems, but you need a copy of your own in the same directory 
as the binary.

> I note it is trying to default to syria-scs-net which might be the cause 
> of *some* of the problems..... (I left template, user0/1, minimal 
> services etc and the perl version copes with this fine)

It's defaulting to syria because they use private addresses (as you do).
You are not in firewalls.xml, while syria is.
The right way to handle it is to put a 'useFirewall' tag in your 
configuration, and specify your firewall there too. 
I have this in my copy of your original configuration. Is it all 
still there? If so, and you copy that one into this directory as 
mentioned above, it should be ok.

> This is localProxy GUI (the 'front end'), version: 4.106

This is strange. The two binaries I released were versions v4.111 
and v4.113. Yes, I forgot to get the version numbers in synch with 
the Perl versions :-(. What you're seeing here is the localProxy.tas 
version number, which is propagated to the localProxy.pl until I 
CVS synch them.
The current perl version is v4.247
I wonder where v4.106 came from?

> Proxies found in environment: 192.168.4.1:8080

It found this, but failed to find the authentication info?
You can see what it thinks it knows about authentication in the 
advanced window.

> I'm assuming this IP address is 192.168.4.103
> Bad command or file name

Hmm ... that's a problem.
I'll wait to hear which O/S.

> I'm assuming this IP address is 192.168.4.103
> Setting default config syria-scs-net
> Use of uninitialized value in array element at C:\PROGRAM 
> FILES\WINBIN\LOCALPROX
> Y.EXE line 1318.
> Tk::Error: wrong # args: should be ".toplevel1.frame.listbox selection 
> option in
> dex ?index?" at PERL2EXE_STORAGE/Tk.pm line 228.
>  Tk callback for .toplevel1.frame.listbox
>  (command bound to event)

I think this was fixed in the second binary. 
I remember being uncertain if I had it nailed down on all systems 
though.

[...]

> Hmmm.... so initially not a very positive sign but a decent idea !! 

The idea of producing a Windows binary? There was a lot of demand, 
but I never really understood why. These things are still 
incomplete and are still 4.5MB! The full thing would be 5MB at 
least, and the whole Perl + proxyTools download is only a few MB 
more! And then new versions are only a few hundred KB.
You can't even argue they are much easier to set up, since the 
modules are automatically installed in the Perl version. 
I guess your case is exceptional though, since you have such 
restricted access.

I'm (slowly) learning that a lot of effort on my part to make even 
a tiny improvement in ease of use is appreciated :-)

> Will 
> try reloading the perl version and getting that working again as I 
> corrupted my last distribution !!

Recommended. I've never been happy with the binaries. You already 
have Perl, so I'm not sure why you even tried the binary.

> Mike

--
wa...@ny...
http://proxytools.sourceforge.net/