HDTenEightyP/NetNews huggingface dataset:
From: jhpb@sarto.budd-lake.nj.us (Joseph H. Buehler)
Subject: Re: NetFax & ZyXEL U-1496E ... are they compatible???
Organization: none
Date: Sat, 29 Aug 1992 06:37:42 GMT

In article <1992Aug27.094518.15764@leland.Stanford.EDU> buc@leland.stanford.edu (Robert Richards) writes:

   I have Netfax 3.2.1 on a SPARCstation.  NetFax seems to run fine but
   does not get far when it starts talking to the ZyXEL modem.

   Has anyone used NetFax with a ZyXEL?

Judging by past net posts and email, Netfax 3.2 is not yet completely
operational with the ZyXEL on *anyone's* machine.  The FAX protocol
used by the ZyXEL has its own peculiarities, when compared to the
Everex Everfax that netfax was written for.  This is because Class II
is not really a standard yet.

If you want to do some tinkering, I can send you a set of patches for
SVR4 for netfax 3.2 (not 3.2.1, I don't have that!) that fixes a
number of incompatibilities with the ZyXEL.  Be warned that my patches
are not fully operational, though.  I have problems with more than one
page at a time sending or receiving.  As I recall, I think it only
sends when I'm running truss to trace the system calls to find out why
it doesn't send. :-(  But I was last working on reception, not
transmission, so I may misremember.

Zero One refuses to provide any documentation to their users for the
FAX mode of the modem (grrrrr...), so this is sort of an ongoing
net.saga.
From: tnixon@hayes.com
Newsgroups: comp.dcom.modems
Subject: Re: ?'s about Class 1 & Class 2 fax
Date: 2 Sep 92 18:13:15 EDT
Organization: Hayes Microcomputer Products, Norcross, GA

In article <1992Aug30.041940.8573@sdf.lonestar.org>,
mo@sdf.lonestar.org (Mohit Goyal) writes: 

> Hello.  In your reply you mentioned that Class 2 was sent for a final
> 30-day ballot about 2 weeks ago.  You also mentioned that you do not
> feel it will pass, and that it will be abandoned.  Do you think that
> if this happens nothing like it will ever be created?  I like the
> idea behind Class 2, to offload some of the work from the software to
> the modem.  I'm just curious.  The software I use right now only supports
> Class 1, and the modem I am about to purchase only supports Class 1.

Actually, I think it will pass, and not be abandoned; the companies 
that voted no on the last ballot have indicated that they will 
support it this time.  If they don't, or if somebody else votes no 
for some reason, then I think everyone will simply be so frustrated 
after four years of work that the project might very well be 
abandoned.  What we'd have left is a "sort of" ersatz "industry 
standard" consisting of the various "Class 2" modems in the field, 
but we'd also have the expanded and enhanced Class "1A" coming very 
soon which I think would be the "real" standard going forward into 
the future.

-- 
Toby Nixon, Principal Engineer      | Voice   +1-404-840-9200  Telex 401243420
Hayes Microcomputer Products, Inc.  | Fax     +1-404-447-0178  CIS   70271,404
P.O. Box 105203                     | BBS     +1-404-446-6336  AT&T    !tnixon
Atlanta, Georgia  30348             | UUCP uunet!hayes!tnixon  Fido   1:114/15
USA                                 | Internet                tnixon@hayes.com
Xref: sparky comp.dcom.modems:12657 comp.sys.dec:4771
From: tls@panix.com (Thor Lancelot Simon)
Newsgroups: comp.dcom.modems,comp.sys.dec
Subject: DS3100 serial ports (was Re: UNIX dcom software.)
Date: 28 Aug 92 03:01:18 GMT
Followup-To: comp.sys.dec
Distribution: usa
Organization: PANIX Public Access Unix & Internet, NYC

In article <1992Aug27.014358.24833@gordian.com> johnk@gordian.com (John Kalucki) writes:
>
>It's simple enough to go into the source for Kermit and hack it
>up for 38400. I did it on a DecStation 3100 in a few minutes.

Pleasepleaseplease tell me what you were using for serial ports on your DS3100?

A SCSI mux, maybe?  I've never seen anything stuck on a 3100 do 38.4 reliably.

-- 
Thor Lancelot Simon	 tls@panix.COM
  "Oh, you have wounded me!  I have very few prejudices, actually.  The
biggest problem is that I am intolerant of fools.  That is why I have
such a low tolerance level for Libertarians."  -- Jim McMaster
Newsgroups: comp.dcom.modems
From: dougs@david.wheaton.edu (Doug Smith - SGA)
Subject: Modem use in Moscow
Organization: Wheaton College, IL
Date: Thu, 27 Aug 1992 22:00:18 GMT

I will be making a trip to Moscow soon and am wondering if my USA modem will
work as is.  Anybody know?
Newsgroups: comp.dcom.modems
From: honey@citi.umich.edu (Peter Honeyman)
Subject: Re: Modems, compression, and SLIP or PPP (was Re: Using Telebit PEP with SLIP)
Reply-To: honey@citi.umich.edu
Organization: Center for Information Technology Integration, Univ of Michigan
Date: Sun, 23 Aug 1992 20:23:09 GMT

sorry about the earlier, abbreviated version of this article.
i sure wish xrn would let me cancel ... oh well.

Bob Sutterfield writes:
|> Whether you use V.42bis depends upon your application.  It will only
|> very rarely (if at all) decrease your throughput, likewise latency, so
|> it's probably safe to turn it on and leave it on for most purposes.

in experiments run here, we have seen very high latencies due to v.42
and v.42bis.  (but since we use the network more for file transfer
than interactive traffic, we do leave them on, as bob suggests.)

|> A typical PPP frame is exactly three bytes larger than a typical SLIP
|> frame.  This expands a typical VJ-compressed telnet packet from five
|> bytes to eight.  So far as I can tell, the difference is unmeasurable
|> and imperceptible.

a typical vj-compressed telnet packet is four bytes, not five -- here
are three quotes from rfc 1144, "compressing tcp/ip headers for
low-speed serial links", by van jacobson:

from section 1 (introduction): the average compressed header is 3 bytes

from section 3.1 (the basic idea): Recognizing a couple of special
cases special cases will get us three byte headers for the two most
common cases---interactive typing traffic and bulk data transfer

from section 3.2.2 (compressed packet format): compressed terminal
traffic usually looks like (in hex):  0B c c d, where the 0B indicates
case (1), c c is the two byte TCP checksum and d is the character
typed.

|> Few connections are error-free.  A V.32bis/V.42/V.42bis modem, clocked
|> at 38400 or better, can easily deliver bits fast enough to overwhelm
|> primitive serial I/O interfaces such as are found in many popular UNIX
|> systems.  Those UART overruns are manifested as line errors, which
|> PPP's 16-bit CRC (not a checksum!) will almost always catch, so that
|> the PPP can drop the damaged packet before passing it up to IP.  This
|> will save your bacon if you're running non-UDP-checksummed NFS, even
|> over a V.42 or MNP4 modem.

there are many errors here.

my home computer is an ibm rt, three or so mips, with a run of the
mill 16550 async card.  i run the interface at 57,600.  uart overruns
are infrequent -- way less than 1%.  if my dinky, five-year old unix
box can do it, so can yours.

crc *is* a checksum -- that's what the second c stands for.

i fail to see the point in having the link layer drop the packet. 
even if it gets past the ip header check, the transport layer will
surely drop it.  the ppp checksum is entirely redundant, wasteful.

should i comment on the utter stupidity of running nfs (or *any
networked application!*) over a non-checksummed udp?  especially in a
low-speed environment, where computational overhead is slight?

	peter
Newsgroups: comp.dcom.modems,alt.bbs,alt.bbs.ads,alt.bbs.allsysop
From: colley@wang.com (Mike Colley)
Subject: Want to Buy FAX CARD
Organization: Wang Labs, Lowell MA, USA
Distribution: USA
Date: Tue, 01 Sep 92 00:19:52 GMT

I'm unemployed and I am looking to buy a ZOOM S/R FAX inexpensively.
If you have a ZOOM FAX (I prefer a FAX CARD) you want to sell,
make me an offer!  I can buy a new one for $75 which includes
shipping, so I expect $40 will be a ballpark figure.

Please make note of the different address to make an offer to: 

uudell.dell.com!sneezy!mcolley or landline (512) 837-2010.

Thanks

Mike Colley
From: ekrimen@wet.UUCP (Ed Krimen)
Newsgroups: comp.dcom.modems
Subject: Re: Word of Advice
Date: 26 Aug 92 17:36:32 GMT
Organization: Wetware Diversions, San Francisco

In article <9208250703.AA04647@ucbvax.Berkeley.EDU> MLPOWE01@ULKYVM.LOUISVILLE.EDU (Michael Powell) writes:
>
>DO NOT BUY A SUPRA!!!!!!!!!!!!!
>
>Resist the temptation and buy something worth your money...not a $350 (or
>whatever the price) paper weight.  I've gone through three and number three
>will probably go out this afternoon...none have worked.  Instead of seeing
>some LD savings (over 2400 baud), I've paid lots more to send this damn thing
>back and forth between here and Oregon....it isn't worth the stress.
>
>Buy a nice USR or something (I hate to say that, seeing as the only contact
>I've ever had with them was extremely poor....awful public relations).

Sorry to hear you've had such bad luck.  I have good experiences with Supra,
even when calling their Tech Support line.  I have a V.32bis with 1.00 ROMs,
and it's been working fine for months.

(Looking forward to those new ROMs though.  <tap> <tap> <tap>)





-- 
   |||    Ed Krimen
   |||    ekrimen@wet.com
  / | \   E.KRIMEN (GEnie)
Newsgroups: comp.dcom.modems
From: bob@MorningStar.Com (Bob Sutterfield)
Subject: Re: Latency Question
Organization: Morning Star Technologies
	<1992Sep3.003250.14571@zip.eecs.umich.edu>
Date: Fri, 4 Sep 1992 14:49:23 GMT

In article <1992Sep3.003250.14571@zip.eecs.umich.edu> dmuntz@quip.eecs.umich.edu (Daniel A Muntz) writes:
   Latency hasn't changed at all between my WB's after upgrading to
   5.01.  Ping settles to ~200ms (56 data bytes).

That packet is so big (~88 octets, counting ICMP headers) that it's a
better measure of in-modem data compression (V.42bis) than of
modem-induced latency, or of the responsiveness that the user feels
when typing in a telnet session that crosses the link.

To test modem-induced latency, you want the smallest packet possible.
To measure what a user feels when typing, you want to send a
single-character telnet packet, and time how long it takes for the
echo to return from the telnetd on the other end.  Happily, these two
goals coincide if the SLIP or PPP implements RFC-1144 "VJ" TCP header
compression.  A typical single-character telnet packet will cause five
octets to cross the wire if you're running CSLIP, or eight if you're
running PPP with TCP header compression.  To conduct such
measurements, we use ftp.morningstar.com:pub/tools/telnetping.c.Z.

For illustration, here's a long distance call with VJ-capable PPP
between SPARCstations over WorldBlazers (the calling end has 5.01, the
answering end is at 5.00) running V.32bis/V.42/V.42bis:

	10:31am> ping -s pike 56 100		(exchanges ~88 octets per packet)
	PING pike.morningstar.com: 56 data bytes
	16 bytes from pike.morningstar.com (137.175.2.38): icmp_seq=0. time=448. ms
	...	
	----pike.morningstar.com PING Statistics----
	100 packets transmitted, 100 packets received, 0% packet loss
	round-trip (ms)  min/avg/max = 253/562/5043
	10:32am>

Sending a smaller chunk of data within the ICMP packet improves the
numbers, but it still leaves a lot of ICMP header overhead:

	10:32am> ping -s pike 8 100		(only ~40 octets per packet)
	PING pike.morningstar.com: 8 data bytes
	16 bytes from pike.morningstar.com (137.175.2.38): icmp_seq=0. time=261. ms
	...
	----pike.morningstar.com PING Statistics----
	100 packets transmitted, 100 packets received, 0% packet loss
	round-trip (ms)  min/avg/max = 221/680/5903
	10:33am>

Here are the numbers reported by several invocations of telnetping,
which uses TCP and therefore is susceptible to the efforts of VJ
header compression in reducing the overhead of the packets it
exchanges:

	10:35am> telnetping pike		(only ~8 octets per packet)
	Opening 137.175.2.38, port 23...
	...
	min/average/max = 0.181/0.195/0.369
	min/average/max = 0.152/0.245/1.533
	min/average/max = 0.161/0.187/0.378
	min/average/max = 0.161/0.191/0.368

These interactive latencies are far better than what you see with ICMP
pings, and they better represent the type of latency that matters:
what a user feels.  It's encouraging that they're generally below the
magical 200ms perceptibility threshhold.

I'd like to know what number telnetping would report over CSLIP or
VJ-capable PPP between USR modems, but I don't have any here.  Would
anyone care to try?
Newsgroups: comp.dcom.modems
From: kevinb@oblivion.csd.sgi.com (Kevin Brokaw)
Subject: Re: Supra V.32bis Fax/Modem questions
Organization: Silicon Graphics Computer Systems 
Date: Thu, 27 Aug 1992 15:48:13 GMT

In article <axa12.154@po.cwru.edu>, axa12@po.cwru.edu (Ashok Aiyar) writes:
|> 
|> I am looking into getting one (and possibly two) of these modems.
|> 
|> I have the following questions about them.
|> 
|> a) What is the latest ROM version?

I've owned my Supra for about 2 months now, and I believe it's the latest ROM...
the level returned is 1.200C


|> b) I keep hearing about Caller ID and a FAX/Modem/Voice switch.
|> 	What is it and does this modem have it?  (I know what
|> 	Caller ID is)

These functions are billed as "low cost future upgrades", due out in 4th quarter
of this year.


|> c) I have heard both bad things and good things about them on
|> 	the net.  Does anyone have trouble connecting to
|> 	US Robotics Courier V.32bis modems with these modems?
|> 	What about Telebit T-3000 and US Robotics Dual Standards?

I've been using mine for a BBS which is heavily involved in network mail 
activites, and places about 20 outbound calls daily to various locations,
with a variety of modems, including the two USR ones you mentioned. To date,
the only problems I have had is in calling other Supra's or older (first
ROM level) releases of other Rockwell chipset clones (ie, Zoom, Twincomm, 
etc). This was forwarned to me on a leaflet inclosed with the modem docs, 
and once the other modem owner upgraded their ROM, all was well. This apparently
only happens when calling modems with the very first ROM level for the chipset,
and does not happen often in my case. As for the USR's, I have never had a 
problem calling any USR modem, including HST's (albeit I only get 2400 baud
when calling an HST) - this is more than I can say when I was using a loaner
IBM V.32 modem... it failed to connect to a plain HST about 50-60 percent of the
time. My only general complaint of the modem is that it seems to be VERY unforgiving
to line conditions, and will fall back to 9600, 7200, or even 4800 on a few occasions
that the IBM V.32 modem would maintain a 9600 connect on, even with V.42 or MNP error
correction enabled. It needs a pretty clean line to stay at 14.4k, and where I used 
to live (extremely rural area), this was a problem about 1 out of every 6 or 7 calls.
  All in all, though, I'm happy with it, as I paid $249 for it on their sysop
program, and do NOT feel I did not not get my my money's worth.
  


-- 
Kevin Brokaw - Product Support Engineer   | 
Silicon Graphics Computer Systems         | All wight, rho sritched
Internet: kevinb@sgi.com                  | my kegcaps awounf?
                                          |

Newsgroups: comp.dcom.modems
From: keith@ksmith.uucp (Keith Smith)
Subject: Re: What's a good 14400 modem??
Organization: Keith's Computer, Hope Mills, NC
Date: Mon, 31 Aug 92 14:29:02 GMT

And the MultiTech 1432 is a very good mid-priced V.42bis, and has UUCP
spoofing, and FAX capability.
-- 
Keith Smith          uunet!ksmith!keith            5719 Archer Rd.
Digital Designs      BBS 1-919-423-4216            Hope Mills, NC 28348-2201
Somewhere in the Styx of North Carolina ...
From: krc@ecl.psu.edu
Newsgroups: comp.dcom.modems
Subject: Modem Price List.
Date: 30 Aug 92 12:48:43 EDT
Organization: Engineering Computer Lab, Pennsylvania State University

Awhile back someone posted a listing of 9600 baud modems. with the
manufacturers name and features.  They had a list of companys that
offered these modems and there prices..  If anyone out there has an updated
list, please reply....thanks!!

Keith Connors
krc@eclx.psu.edu
Newsgroups: comp.dcom.modems
From: spyder@admiral.uucp (Eric Liu)
Subject: I NEED HELP with my Pract. Peri.  PM14400FXSA Modem...
Reply-To: spyder@admiral.uucp (Eric Liu)
Organization: The Grid/Waffle BBS, 203-661-2873, -1279, -0450, -2967
Date: Fri, 28 Aug 1992 16:31:45 GMT

I can't get this modem to work properly, so that I connect with v.42bis 
and LAP-M.......please help...

--
spyder%admiral.uucp@yale.edu (Eric Liu) <yale!admiral!spyder>
The Admiral's Public UNIX - Greenwich, CT - System Administrator: Doug Fields
(HST/V32) (203)661-2873 -- (PEP/V32) -1279 -- (V32) -0450 -- (V29/MNP6) -2967
>FREE!< Unix shell accounts, Usenet access, and Internet-style mail available
From: bjdunlop@shamash.cdc.com (Bruce Dunlop)
Newsgroups: comp.dcom.modems
Subject: Re: Cheap 14.4Kbps modems
Date: 27 Aug 92 16:58:29 GMT
Organization: Control Data, Arden Hills, MN


I just bought an external Forval modem for $275 + $12 shipping.  The internal
version is the same price, except it is $6 for shipping.  This modem has
14.4Kbps, V.everything, MNP2-5 and LAPM. The internal modems have the TURBO
board implemented, which makes for data integrity up to 115KB/s (has 32
byte buffer).  Here are some features:
	5 year warranty
	Hayes AT command protocols 100%
	FAX upgade FREE later this year
	19.2Kbps upgrade for $100 within 90 days (Forval unique protocol)
	V.fast upgradeable when standard is finalized.
	All upgrades done by phone via BBS download of new firmware!
		(don't have to install a new EPROM)
	External has LCD display panel with menu system to set it up manually

This modem works great.  It has gotten rave reviews in the RIME communications
conference.

Order from Mikro Tek,
	619 North 4th Street
	San Jose, CA 95112

	Terms: Money orders, cashiers checks, or certified checks
		No credit cards.

Call Chris Von Motz - 	408-294-0526 voice
			408-294-3056 BBS
			408-286-5702 Fax
to order or ask questions.

Jim Dahlberg
jad@verdin.gsd.cdc.com
From: john.navas@uttsbbs.uucp (John Navas)
Newsgroups: comp.dcom.modems
Subject: ANY COMMENTS ON THE USR S
Date: 3 Sep 92 21:37:00 GMT
Reply-To: john.navas@uttsbbs.uucp (John Navas)
Organization: The Transfer Station BBS, Danville, CA - 510-837-4610/837-5591


 > Well, needless to say, I now have a Hayes and PPI modem instead,
 > and am happy with both (although I did have some problems with PPI
 > support also, but not half as bad as USR).
 > So be warned... USR may have a good product, but good luck if you
 > need customer support!

I also have had problems with USR support.  Nevertheless, the USR
Sportster is a very good product.  I have had equally bad or even
worse support from several other modem vendors, particularly Intel.
The difference is that the Intel "Satisfaxtion" is flawed, whereas the
Sportster is rock solid ( at least in my experience :).

Best regards,
John
From: gtoal@ibmpcug.co.uk (Graham Toal)
Newsgroups: comp.dcom.modems
Subject: Re: Supra Roms???
Date: 28 Aug 92 01:14:43 GMT
Organization: The IBM PC User Group, UK.

In article <19919@plains.NoDak.edu> myhre@plains.NoDak.edu (Robert Myhre) writes:
:
:  Hi.  I would like to know how to open up a Supra 1.4k Fax/Modem external
:to determine which ROM it contains.  There seem to be only two screws on the 
:bottom but when I removed them nothing would come undone.  I don't know if I
:need to use a little more force, but I would rather get some info before I
:do that.  Thanks

Yes!  Be gentle!  (I have a vested interest ;-) )

G
-- 
Newsgroups: comp.dcom.modems
From: s37756d@puukko.hut.fi (Casper Gripenberg)
Subject: Supra FAX bug! (?)
Summary: DCD Does not follow Carrier? 
Organization: Helsinki University of Technology, Finland
Date: Tue, 25 Aug 1992 22:08:37 GMT



Hello!

I got my Supra FAX v32bis with the 1.200C ROMs and the modem works perfectly
except for this very annoying bug:

I have my modem setup as follows (if I remember correctly)
AT&F2 &D L0 M0

Ok now &F2 includes &C1 which says that DCD ON indicates data carrier
from remote modem, ok so far. Then I have &D which tells the modem to
ignore the DTR signal. Now, when I connect DCD goes on like it should,
but if I drop DTR (like exiting from my terminal program) DCD also drops!!!

This is really strange...The only way to get DCD back on is to do for
example +++ at\o. 

Do I have a one in a million bug in my Supra or does this happen 
for all of you Supra owners? If it is a bug, does Supra know about it?

Also +++ at\o only works for v42bis connections, if I try it on a
MNP4 connection I get TE and the modem just hangs..What is the
proper way to get back on-line after +++ ???

Thanks,

   Casper (s37756d@puukko.hut.fi)



Newsgroups: comp.dcom.modems
From: uri@watson.ibm.com (Uri Blumenthal)
Subject: Re: Microcom modems?
Date: Thu, 03 Sep 1992 17:13:34 GMT
Distribution: usa
Reply-To: uri@watson.ibm.com
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM  T. J. Watson Research Center

In article <1992Sep2.184539.25029@inel.gov>, sfr@wcusv1.NoSubdomain.NoDomain (Steven Schaeffer) writes:
|> I just started reading this group about a week ago and I'm surprised that I
|> haven't seen a single article on Microcom modems. Is it that nobody uses them? Is
|> it that nobody has any questions about them after reading the manual? Am I the
|> only one who ever bought one? :-) I have a QX-3296 and I've been quite pleased
|> with it.

I own several Microcom modems, and I'm rather DISPLEASED with them.
Two of three got broken within one year, Microcom Tech SUpport was
NOT a great help, the modems are very bad on noisy phone lines, as
bad as it could be... BTW, these are QX/v.32c beasts.

And when I asked Microcom for upgrade (because I don't think 
there's another idiot who will take that trash away from me,
and I hate to see those coffins lying under the desk) -  try
to guess what they responded:

	"Yes, sure, it will cost about $670 per modem".

Of course I pointed out that I can get a brand new modem for
less, and of course there was no answer.

Bottom line:  if you want to be as sorry as I am - go 
ahead and buy Microcom. Bad quality, bad Tech Support, 
bad Upgrade Policy.
-- 
Regards,
Uri.		uri@watson.ibm.com
------------
<Disclaimer>
From: jong@boole.seas.ucla.edu (Jong Y. Lee)
Newsgroups: comp.dcom.modems
Subject: Re: 16550 vs. 16550AFN
Date: 30 Aug 92 08:55:04 GMT
Organization: SEASnet, University of California, Los Angeles



In article <Btnw8I.55H@animal.gcs.co.nz> lchiu@animal.gcs.co.nz (Laurence Chiu) writes:
>
>Yes I do have caching on. I use the 3.1 smartdrv with 2M of cache. I turned
>off write caching since I was a little worried about that. Perhaps your
>drives are not fast enough? I use 17ms Seagate IDE drives (1144A and 3144A)
>
>Laurence Chiu


That's strange.  That's the exact cache program I'm using with the same amount 
of cache.  And I never got more than 1300cps with cache on.  So I just do 
smartdrv c- to turn off cache on drive c: entirely.  Anyway, I'm using 
Maxtor 7120A and 7080A whose avg. access times are supposed to be 
15ms and 18ms, respectively.  But I get around 11-12ms with sysinfo program 
from Norton Unility which isn't bad at all.

Jongyoon

Newsgroups: comp.dcom.modems