[rc5] feature not yet implemented?
void at null.net
Sat Aug 9 00:29:15 EDT 1997
Mike Silbersack wrote:
> A while back, I remember people requesting a feature that would make
> rc5 go
> into a mode so that it wouldn't do *any* network communications, and
> run off the buffer file. I didn't used to think this was necessary
> now when I setup my 486/66 (which is still running windows 3.11, and
> be for a while) with the rc5v2b4 win16 client. The problem currently
> that rc5v2b4 seems to require the TCP stack to be initialized before
> will ever start running! As a result, when I start the client, it
> auto-starts trumpet winsock, which I must let dial and connect before
> will start running. (Luckily, I can disconnect once RC5 starts
> Since I have my 486/66 system networked with my primary computer
> (which I
> use to report blocks with on a daily basis), it would be much nicer if
> could simply start the client on the win 3.11 machine and not have to
> through the trouble of getting internet communications working first.
> there any plan to have this buff-file-only feature in rc5v2b5?
> Mike "Silby" Silbersack
> silby at execpc.com
Yes, this feature is needed for machines sharing a networked directory
that don't need to do their own communications.. P.S. I'll add it if you
guys are too busy to...
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.
More information about the rc5