| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | KTX modem |
Craig, at 22:10 on Thu, Mar 20 1997, you wrote to Bill Grimsley ...
CP> Quite likely. The way I see it is.. The KTX will never work properly,
CP> as it has all of the universe working against it. You see, nature
CP> abhorrs a vacuum, and KTX's SUCK! :>
That's one opinion not necessarily shared. It's not possible that a Netcomm
could be at fault (Oh my, no!).
CP> I've had the pleasure of calling two different KTX's so far {at}V32. One
CP> would retrain after no more than 5s connected. Constantly. The other
CP> just plain wouldn't connect unless the baudrate was locked down to
I ran my BBS on a KTX modem and it worked just fine. A friend down the road
uses the same KTX internal modem and he has no trouble connecting to
anything now that he has his phone line fixed.
... and why in God's name would you call anything at V32? Not that any of
my users had trouble connecting at that speed.
CP> 2400. The only people I've heard say anything nice about KTX's were
CP> of the form:
CP> "i got my new ktx modem the otheday form harvy normen and it works
CP> relly good"
... and then there are those who have nothing but bad stuff to say about
lots of things because they can't figure out how to make them work. For
what it's worth I don't have a real lot of faith in Netcomms.`
Regards, Peter
@EOT:
--- Msgedsq 3.10
* Origin: Montezuma's Revenge -= 61-7-3398-4288 =- (3:640/306)SEEN-BY: 50/99 54/99 620/243 623/630 625/155 640/201 206 230 305 306 311 702 SEEN-BY: 640/820 821 822 823 829 711/401 413 430 934 712/311 407 505 506 517 SEEN-BY: 712/623 624 628 704 841 888 713/317 714/906 772/20 800/1 @PATH: 640/306 305 820 712/624 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.