This is a multi-part message in MIME format.
--------------A15BA64295A770BCF2ADD8AF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
[I wonder if the fogo http archive supports HTML attachments? ...]
--
Dan Connolly, W3C
http://www.w3.org/People/Connolly/
--------------A15BA64295A770BCF2ADD8AF
Content-Type: text/html; charset=us-ascii;
name=",fogo-modem.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=",fogo-modem.html"
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>No title</title>
<meta name="GENERATOR" content="amaya 5.1" />
</head>
<body>
<p>A while back I put together this little <a
href="
http://dev.w3.org/cvsweb/2001/telagent/">telagent</a> hack to support
tel: URIs on my desktop. In mid June, I accidently unplugged the machine, and
the modem didn't work after rebooting. Linux and the BIOS evidently play a
little game of IRQ roulette every time the machine boots, and I usually
lose.</p>
<p>Well, I set it aside for a while... after all: everybody else dials the
phone with their fingers, why can't I?</p>
<p>Well... I'm lazier than most, I suppose. I simply cannot bear to do things
that I know the machine could do for me. Plus telagent makes logs, and the
loss of all the log data is bugging me.</p>
<p>So I got it working again this weekend. Short version: it works fine using
standard COM3 (IRQ3, IO 0x2e8) setting, once eth0 is moved to IRQ 5.</p>
<p>Details... I took the modem out to look at it (<a
href="
http://www.w3.org/2001/08/dc-modem/MAVICA.HTM">photos</a>) then
switched to plug-n-play (<a
href="
http://www.linuxdoc.org/HOWTO/Plug-and-Play-HOWTO.html">Plug-and-Play
HOWTO</a>, <a
href="
http://www.roestock.demon.co.uk/isapnptools/">isapnptools</a>) to get
it working. Found out that this modem is quite a nice one. Here are the
clues, as I remember them:</p>
<ul>
<li>The modem itself (<a
href="
http://www.w3.org/2001/08/dc-modem/MVC-010L.JPG">photo</a>) says
Model 1105L and FCC ID BDN...; Looking up the specific FCC ID failed, but
the FCC says BDN is Zoom Telphonics. Big clue, since "zoom" is nowhere on
the product packaging nor the modem itself.</li>
<li><a href="
http://www.google.com/search?q=Zoom+1105L">Zoom 1105L
search</a> gives a <a
href="
http://www.modem-help.freeserve.co.uk/mfc/zoom.html">Zoom page</a>
in the <a href="
http://www.modem-help.freeserve.co.uk/">Modem-Help,
UK</a> stuff where we learn that model 1105L is better known these days
as 2919. We follow the "AT Commands" link to <a
href="
http://www.zoomtel.com/techsprt/docs.shtml">Zoom Telephonics:
Product Documentation</a> where we get <a
href="
http://www.zoomtel.com/techsprt/docs.shtml">VenusCRM.pdf</a>,
documentation on the Lucent Venus chipset; we discover the ATI command,
which gives the magic token...</li>
<li>I052099gV and <a
href="
http://www.google.com/search?q=I052099gV&btnG=Google+Search">plugging
that into google</a> gives handy stuff, including success reports with
vgetty, a nice review etc.
<ul>
<li><a
href="
http://www.umanitoba.ca/campus/acn/remote/reviews/zoom2919.html">Zoom
Model 2919 Faxmodem 56K Dualmode Modem</a> Bob Todd and Brian Goodman
ACN March 2000</li>
</ul>
</li>
</ul>
<p>My wireless setup is still broken since the firmware upgrade; I'm stuck
trying to get a linux 2.4 kernel to recognize my ISA-to-PCMCIA adapter. More
on that separately...</p>
</body>
</html>
--------------A15BA64295A770BCF2ADD8AF--
