Re: [proxyTools-users] Windows binary release of proxyTools available

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

> From: Michael Foord <Mic...@tb...>
> To: "pro...@li..." <pro...@li...>
> Subject: Re: [proxyTools-users] Windows binary release of proxyTools available
> Date: Thu, 05 Dec 2002 11:45:52 +0000
> 
> My long silence has been for two reasons.
> 
> First off our heavy interent restrictions were relaxed for a long while 
> - needless to say this has come to an end.

I guess the arguments were still there.
Maybe relaxing the restrictions was a test?
It sounds like you (plural) failed :-)

> Secondly the distribution of localproxy I was working with has been 
> corrupted, probably by me, and I never got around to fixing it. 

The config file?
Or the hosts.zip?
Surely not the perl stuff.

> On top 
> of that my startup has started complaining that my SET PATH command is 
> now too long and stopped implementing it. This means it no longer 
> understands perl  commands. (I.e. perl master.pl returns unknown 
> command). I have tried various means of fixing it - without much success 
> - why it should suddenly start complaining is anyones guess. 

There's a limit to each command line. 
Is this in an autoexec?
You can append pieces to the PATH in separate statements. 
IIRC, something like 
set PATH=%PATH%;<extra bits>

> Anyway I`ll 
> have to have another fgo I guess or just set it manually from a script 
> everytime I run localproxy. *damn*
> 
> The new distribution sounds top notch - but unfortunately my IT man has 
> sussed my cheat for retrieving .zips via the web. My next technique is 
> to retrieve via email (various methods) - lets hope that works.
> 
> As soon as I have it (as this is a binary - non perl dependant it should 
> work even without the correct path parameters) I`ll test it !!

Mmm ... that's a pretty weird solution to your problem X-}

> 
> Many Thanks Wayne

Hope my previous message helped.

> Miek

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