Xref: utzoo comp.protocols.tcp-ip:6990 comp.dcom.lans:2764 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!lib!watson!sob From: sob@watson.bcm.tmc.edu (Stan Barber) Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans Subject: Re: Telnet problems with Bridge CS/1's Message-ID: <138@lib.tmc.edu> Date: 3 May 89 18:52:19 GMT References: <7502@charlie.OZ> <1805@ccnysci.UUCP> Sender: usenet@lib.tmc.edu Reply-To: sob@watson.UUCP (Stan Barber) Followup-To: comp.protocols.tcp-ip Organization: Baylor College of Medicine, Houston, TX Lines: 28 In article <1805@ccnysci.UUCP> dan@ccnysci.UUCP (Dan Schlitt) writes: >We also have problems with Bridge telnet handling of . >On some versions of their software it is broken. They know about it >but refuse to supply fixed software. More recent versions are capable >of doing the "right thing". It is configurable in case you want to do >the wrong thing. This is a confusing paragraph. 3com has fixed the problem, but refuse to supply the software. Is that the point? Perhaps you don't have a service contract. They are reasonable good about suppling updates if you are on a service contract. Most companies will not just give software away (check out Sun's dot-dot releases), but they will give it to service-contracted sites and usually sell it to others. Is this not your experience? >-- >Dan Schlitt Manager, Science Division Computer Facility >dan@ccnysci City College of New York >dan@ccnysci.bitnet New York, NY 10031 > (212)690-6868 Stan internet: sob@bcm.tmc.edu Baylor College of Medicine Olan uucp: {rice,killer,hoptoad}!academ!sob Barber Opinions expressed are only mine.