Re: COMMS OVERRUNS

Article View: demon.tech.pc

Article #71380

#71380

From: David Lawson
Date: Sun, 03 Dec 1995 00:00

18 lines
1181 bytes

In article <131348098wnr@garioch.demon.co.uk>, andy nicol
<nd@garioch.demon.co.uk> writes
>>
>When this happened to me, I discovered it was due to an evaluation copy 
>of Turnpike.  The Turnpike installation is claimed to co-exist with your 
>existing Winsock, but this screws up Trumpet Winsock somehow.

 In your case, maybe. But why generalise? I ran several Winsocks
(including Trumpet) on my system with Turnpike.

>  When I got 
>sick of Turnpike (it only took a few days) I had considerable trouble 
>with comms overruns.  I fixed this by removing the (expired) winsock which 
>Turnpike had left in my startup scripts. Not impressed.
>
  But many others are.
-- 
David Lawson - London

Technical Details

Message-ID: <NQSZ4AA64iwwEAo7@artful.demon.co.uk>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <68015832wnr@voltdrop.demon.co.uk>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1036bc,6bc09f23c5e1acad
X-Google-Attributes: gid1036bc,public
From: David Lawson <david@artful.demon.co.uk>
Subject: Re: COMMS OVERRUNS
Date: 1995/12/03
Message-ID: <NQSZ4AA64iwwEAo7@artful.demon.co.uk>
X-Deja-AN: 120939401
distribution: world
x-nntp-posting-host: artful.demon.co.uk
references: <68015832wnr@voltdrop.demon.co.uk>
organization: Scribbler
mime-version: 1.0
newsgroups: demon.tech.pc

Reply to Parent Message