SCOUG-HELP Mailing List Archives
Return to [ 09 |
May |
2002 ]
<< Previous Message <<
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Harry Chris Motin wrote:
>
> "Benedict G. Archer" wrote:
> >
> > An actiontec PCI modem and onboard 3com NIC insisted on using the same
> > IRQ. That was OK until I found that using the modem caused the LAN
> > connection to be lost--can't ping the DHCP server. After trying lots of
> > things, I finally got the NIC using IRQ11 and the modem to use IRQ10 (as
> > determined by a DOS utility, pmdmcfg, that came with the modem) by
> > adding a reserve.sys line to config.sys. If I set hardware detection to
> > anything but off, the system won't boot. The pmdmcfg utility tells me
> > that the modem is using IRQ 10 and address 1800. So, I added the
> > explicit argument (4,1800,10) to the device = ... com.sys line to set up
> > com4 for the modem. But I can't get the modem to work. Incharge (the
> > only need I have for the modem) returns an error on trying to initialize
> > the modem. Spent a lot of time trying different BIOS setups too, but
> > nothing I've tried there has any effect. Where should I look? Is the
> > problem in InCharge, in com configuration or somewhere else? It's an
> > all SCSI system so there are spare IRQs.
> >
> > Ben A.
> Ben,
>
> What driver are you using for the modem serial line and does the modem
> share IRQ 10 with any other device? I had a problem getting my modem to
> work about 2 years ago, after I got a new system. Steven Levine was kind
> enough to point out that some versions of COM.SYS do not like to share
> IRQ's. I updated to a newer version of IBM's COM.SYS and that did the
> trick. I believe you can also use Ray Gwinn's SIO.SYS.
>
> HCMotin
>
Harry,
I should have mentioned that I had tried com.sys that comes with eCS,
com.sys for OS2 that came with the modem, and Sioecs drivers--all with
similar results. With more empirical fiddling, I somehow caused the
modem to want IRQ11 instead of IRQ10. The modem works (on com3), sort
of, that is, it will dial, connect and transmit data, but on attempting
to hang up, the system locks up requiring a power off or hard reset.
IRQ11 is also used by both SCSI adaptors in the system. Could that be
the reason for the lock up. When the modem was using IRQ10, which is
also used by the NIC, using the modem would disable the NIC. What else
can I try.
Ben A.
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
Return to [ 09 |
May |
2002 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|