Not able to access internal modem

The problem that I'm having is I can't get my internal Hayes 33.6 DSVD modem to work under Linux. I can get it to work under DOS, and Windows 3.1 by using a TSR program that runs under DOS. Is there anyway that I can run the DOS configuration program to set the IRQ and IO address under the Linux shell.
Like how Windows3.1, Windows9x  uses the DOS window when you execute a DOS driver or program.
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

biardConnect With a Mentor Commented:
DSVD modems are not compatible with Linux.  See:

Near the bottom of this section DSVD is listed as incompatible.
You can use the program setserial to give irq and io to the port ..
Is your modem plug and play?  Is it a PCI or ISA?  If it is PNP and ISA, there is a program called isapnp that may help you.
EqualizerAuthor Commented:
I don't get it. I've had this DSVD modem for over 2 years, I've never had any non-compitablity problems at all under all Windows plate forms.. I had a little problem with DOS using a AMI BIOS which conflicts with the SETCOM16 DOS modem driver which sets up the IO and IRQ. I discoved under Windows3.1 and DOS that I didn't need to use the SETCOM16 driver at all with the AMI BIOS.
With Linux I don't use any type of driver except for the isapnp.conf. When I run the isapnp command on the /etc/isapnp.conf the file accepts the IO and IRQ and outputs:
Hayes 288 DSVD  IO: 0x2f8  IRQ 3 -----enabled     OK..
I have the IRQ locked in at 3 inside the BIOS.
This modem is very unusual.  It's a stand Hardware modem but it has a upgradable BIOS to were it goes from 28.8 to 33.6 inside the Windows9x. plateform.  It's not  one of them software modems or modems that use the DSP from your CPU. I've used this modem playing DOOM II without even installing the TSR program called SETCOM16. So I'm pretty sure that it should work fine with Linux. What I think the problem is, is either I don't know how to get Linux to reconigize the modem as a modem or I'm just to stupid and I don't know what I'm doing
EqualizerAuthor Commented:
I figured it out.

I disabled COM2 inside the BIOS Plus I have the modem locked in at IRQ 3 and IO 2e8 inside Windows98 plus I have the IRQ 3  locked in the BIOS.
The port inside LINUX the modem is under is COM 4.

/etc/isapnp.conf reads as follows:

#Board 1 has serial identifier  bd 00 00 41 66 17 56 39 20
(READPORT 0x020b)
(CONFIGURE HAY5617/16742 (LD 0 (BASE 0x2e8))
(INT 0 (IRQ 3 (MODE +E)))
(NAME "HAY5617/16742[0]{Hayes accura 288 V.34 DSVD    }")

The INIT string for this modem is:
AT &F &C1 &D2 &K0 &MO &Q5 S46=136
If you want DSVD support use the following INIT string:
AT-SSE &F &C1 &D2 &K0 &M0 &Q5 S46=136

I think I need to give Redhat support a swift kick in the ass because I just installed LINUX on my computer Wednesday December 29 and I just proved them wrong about the DSVD modems not working with LINUX.
I've only been studing LINUX for 6 days now and I'm wondering what I will know about the operating system a year from now.
All Courses

From novice to tech pro — start learning today.