[PROXYPER] Windows NT problem

Mark Hill HillMW at august-systems.co.uk
Mon Oct 5 17:28:12 EDT 1998


On 5 Oct 98, at 7:25, Diggs, Steve wrote:

> Would you give the EXACT command string to make this happen? I use NET START
> <Bovine Service Name> and it works...then substitute STOP for START using the
> command buffer <same thing as DOSKEY> and it fails. There is something here more
> than you think. I know this is a command line problem because the same thing
> <does not> occur when I start and stop the service using the SERVICES applet.

Try the short service name instead of the long one. In the case of 
the pproxy, the short name is "bovproxy". Eg:

NET STOP bovproxy
NET START bovproxy

HTH

> SD
> 
> -----Original Message-----
> From: Mark Hill [mailto:HillMW at august-systems.co.uk]
> Sent: Friday, October 02, 1998 4:40 AM
> To: proxyper at lists.distributed.net
> Subject: RE: [PROXYPER] Windows NT problem
> 
> 
> On 1 Oct 98, at 14:18, Diggs, Steve wrote:
> 
> > Glad to hear someone else trying to use PProxy on NT. I haven't changed the
> > settings from their defaults other than the # of blocks downloaded at one
> time.
> > Meanwhile, I've been trying to find a way to set up a RASDIAL event that would
> > call my ISP, then kick the PProxy service and cause it to do a flush and
> fetch.
> > After several months of trying, I have nothing to show for it. The most
> logical
> > way I can see to do it is to do a NET STOP <PProxy> followed by a NET START.
> > PProxy can't seem to be started and stopped that way. Any ideas?
> 
> Yes it can. However, I've noticed that the nt proxy (and nt client 
> service for that matter) gets in a mess if they are started too 
> quickly after they are stopped. And vice versa. So stop the proxy, 
> wait a few seconds, then start it.


-- 
Mark Hill, Software Engineer
#include <std\disclaimer.h>
Terminal glare:  A look that kills...
--
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net



More information about the proxyper mailing list