Well, having had a cable modem now for just over 2 months, I can’t imagine
that there is any value in supporting any modem at all, let alone the low
ROI one would get from doing a bunch of DSP work in software.
btw: I have had experience with WinModems under Windows, and quite frankly
they suck, throughput wise (I don’t really know what other criteria really
matters with modems) compared to real modems.
“Bert Menkveld” <bert@cormantech.com> wrote in message
news:9973qt$oqb$1@inn.qnx.com…
And yet…
I’m afraid I have to admit that I rather like these “soft” modems, even
though they’re not “REAL” modems. I’ve used a couple of different ones in
my Windoze machine at home, and they work wonderfully well. This seems
particularly amazing to me given the difficulties Windows generally has in
keeping up with anything in real time. If it can be done in the Windows
environment, then it should be a breeze to run a soft modem in the
wonderfully predictable QNX environment, shouldn’t it?
The driver software will obviously be more complicated, but if someone
could
convince Motorola/Rockwell/Winbond or whoever to release specs (or better,
code), then there’s no reason we shouldn’t be able to use these dirt cheap
“soft” modems under QNX.
Just my thoughts. Comments?
–
Bert Menkveld
“Michael D. Burkey” <> michael.burkey@nexwarecorp.com> > wrote in message
news:9959lr$lnh$> 1@inn.qnx.com> …
The key here should be “SM56”.
SM stands for “Soft Modem” – i.e. it is a HSP (host
signal processing) based modem. Which is to say a
“WinModem”. All of the work that would normally
be done by a DSP is done in software using a driver
on the PC under Windows. Which is to say, there is
NOT a QNX driver for this modem nor is their likely
to ever be unless Motorola writes one.
(or unless someone subscribing to this new group
has the appropriate contacts at Motorola to get
the specs and write one – which I don’t really
expect since I assume all that information would
require scads of NDA’s)
The WDM driver under Windows is emulating the
serial port for DOS applications and handling all the
signal processing needed for the modem functionality
(and sapping performance from your CPU in the process
while you are online – fine for web browsing, awful
for gaming).
Anything HSP, SM, WinModem, etc is NOT a REAL
modem. Its a simple analog to PCI interface that lets your
CPU get to the phone line and forces it to do all the work.
QNX works great with REAL modems.
If you need a good PCI modem, go look at the
3Com/USR 56K Pro Series. They work nicely with QNX.
My modem is a Motorola SM56 PCI Speakerphone and it’s internal.
In
Windows ME and 98 it works on COM3 and IRQ 10. I tried using the
devc-ser8250 and they
appear new devices: ser3 and ser4 on /dev/
Then, I go to the Dialer to try the new devices. I select ser3 and
push
Connect. But when it attemps the ATZ it does nothing… nothing but
saying
“Connection failed” in a few seconds waiting.
Well, I think my modem it’s unsupported. In Windows ME uses a rare
driver in addition to the common modem driver: it’s called Motorola
SM56
WDM
Device. According the de Devices Manager this is a WDM Modem
Enumerator
device (with a chip saying WDM in the icon representing it).
What’s the problem? Have I to remain disconnected in this Operating
System?
Are these the GOOD features I’ve heard from QNX?
Thank you very much.
Simply JMN
\