Re: OEM modems

["Dan Bale" <dbale@xxxxxxxxxxx>]

Carl,

Well, the key _is_, "if you understand data communications", and I did not to
the extent required to deal with this thing.  I can't remember the exact wording
of the original post, but from following the thread, I got the impression,
rightly or wrongly, that James might be at the same level I'm at.

But, still, the question remains, at what point do you cross the threshold of
the cost of time to make a given modem work as opposed to spending a few (?)
extra bucks to get a modem supported by IBM which may (or may not) be as easy as
plug'n'play?  For a expert data comm guy like yourself, _you_ may be able to
setup any modem you come across without a blink of the eye.  For the rest of us
who may come across having to set up a modem once a year, it's not necessarily
something we commit to memory.  That's why we have you guys!  ;-)

Believe me, I wish I had known about MIDRANGE-L when I had to do that async job!

- Dan Bale

_________________________ Original Message _________________________

Dale:
I disagree with your comments.  I you understand data communications, you
should be able to make any modem work as long as you know what you are
doing.  I still feel the UDS modems are FAR superior to the IBM modems,
especially when you have them deployed in an environment where you may have
to talk someone through configuration, the front panel display and the
YES/NO keys allow this very nicely. The Option by IBM modems work well but
the lights on them are too hard to see.  There is no magic to
communications, just have to understand what you are doing.
CJG





+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---