From:	"Bob Jonkman" <bjonkman AT sobac DOT com>
Organization:	SOBAC Microcomputer Services
To:	opendos AT delorie DOT com, "Paul O. Bartlett" <bartlett AT smart DOT net>
Date:	Mon, 30 Oct 2000 00:16:07 -0500
MIME-Version:	1.0
Subject:	WinModems and BEOS [was: Public Buying]
Message-ID:	<39FCBDC7.22060.4DEAD96@localhost>
X-Confirm-Reading-To:	"Bob Jonkman" <bjonkman AT sobac DOT com>
X-pmrqc:	1
References:	<39FB751A DOT 9410 DOT C349BD AT localhost>
In-reply-to:	<Pine.LNX.4.10.10010291835340.24455-100000@smarty.smart.net>
X-PM-Encryptor:	QDPGP, 4
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	opendos AT delorie DOT com

-----BEGIN PGP SIGNED MESSAGE-----

I want to tell you what Paul O. Bartlett <opendos AT delorie DOT com> said
about "Re: Public Buying" on 29 Oct 2000, at 18:56

[him]
> > >  First I think I need to get a new modem, as what came with my box
> > > was apparently one of those cheesy "Winmodems."  (BeOS would not
> > > use it, and somebody on a BeOS list called it a Winmodem.) 

[me]  
> > Some WinModem manufactures (USR, aka 3Com) have come to realize that 
> > Open Source is where it's at, and are releasing the programming specs 
> > for the WinModems to the Open Source community.

[him again] 
>     If I recall correctly (I might not), US Robotics is the only such
> modem that BeOS will use right out of the package.  When I booted a
> trial version of BeOS, it *recognized* that I had such-and-such a modem
> installed in this-or-that location, but BeOS refused to use it.

[me again]
Check to see what the WinModem has configured for its I/O port and 
IRQ.  The Windows drivers like to use IRQ10 and an I/O port in outer 
space somewhere, and that's not normal.  If you can get the thing 
configured to use the standard COM1 or COM2 settings then BEOS might 
be able to make use of it.  It's possible the WinModem has non-
volatile memory to store its settings.  If that's the case, and you 
have trouble getting the config program to run under BEOS, you may be 
able to plug the WinModem into a computer running a Windows OS, set 
the configuration for the WinModem using the Windows-based software, 
then take it out and plug it into the computer witn BEOS...  Of 
course, using the WinModem under BEOS DOES require WinModem drivers 
for BEOS...

For what it's worth, if your computer has enough spare CPU cycles 
then using them to power a WinModem is not a problem.  The trick here 
is to find either a sufficiently powerful computer, or an OS that 
doesn't suck the life out of it.  I have found that Win31 on a 486-66 
gives perfectly acceptable performance for the WinModem.  As you 
upgrade the OS, so must you upgrade the CPU (to maintain acceptable 
performance).  Using an OS like GEOS on a 486 should let the WinModem 
fly.  I don't know how BEOS compares in the OS-as-molasses race with 
Win9x...

For reference I include:

COM1:   IRQ=4   I/O=03F8
COM2:   IRQ=3   I/O=02F8
COM3:   IRQ=4   I/O=03E8
COM4:   IRQ=3   I/O=02E8



-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: Ensure confidentiality, authenticity, non-repudiability

iQCVAwUBOf0EFaLoCveuM+mJAQFpkwQAsLXz8NZcCriiTc9xOsxbAltqqC9RiCOH
TFmLvI3OwWqQhhBGRvB6Xn1+vHQTqggWCF994idAVENcqGP37GFSg+imEI8fmYMd
XB7W8/DwWKflxvJICwjx3Nupj25jc+p0XRvAY+qF0+VY6vMIHjr+rrQ0vjpcMcUD
/tTaKWLAfas=
=yVam
-----END PGP SIGNATURE-----

=====
Bob Jonkman                               Voice: +1-519-669-0388
SOBAC Microcomputer Services              E-Fax: +1-603-308-6118
6 James Street                         mailto:bjonkman AT sobac DOT com
Elmira    Ontario    N3B 1L5    Canada
Networking   --   Office & Business Automation   --   Consulting
RSA Fingerprint:  9FAF  A6AC  B567  BC10  8973  7CF0  CB27  0317
RSA ID: 0xAE33E989    mailto:bjonkman AT sobac DOT com?subject=send_key

Web site temporarily at     http://members.home.com/bjonkman

- Raw text -