Article View: comp.os.os2.setup.misc
Article #59Re: Plug and Pray problems in Warp 4
From: Charlie Jager
Date: Sat, 08 Nov 1997 00:00
Date: Sat, 08 Nov 1997 00:00
71 lines
3579 bytes
3579 bytes
In message <63a458$qg0@interserv.etn.com> - wellner@pop.mke.etn.com writes: :> :>In <637nse$qb0@tandem.CAM.ORG>, zeus@cam.org writes: :>>In <DtMT0UjRQE7f092yn@netcom.com>, skoper@netcom.com (Stan Koper) writes: :>>>I just picked up an internal Philips k56flex modem. I have a :>>>dual boot system, Win95 and OS/2 4.0. The modem set up under :>>>Win95 as Com3, Irq 10. I have the SIO drivers under OS/2, and :>>>they don't recognize the modem *unless* I stop the boot at the :>>>white square and select full hardware detection. :>>> :>>>When it does work under OS/2 it's still com3 (since the :>>>motherboard has two serial ports), but the Irq is 7. I haven't :>>>tried it under WinOS/2. :>>> :>>>What I'd like to know is, is it possible to establish full :>>>hardware detection *without* interrupting boot up? Is there :>>>some line I can add to config.sys or is there some other process :>>>(like selective install) that I can use to get the modem :>>>recognized by OS/2? :> :>If you go to the Properties setting of the Hardware Manager you can set for :>full hardware detect. (OS/2 System>System Setup>Hardware Manager and right click). :> :>>> :>>> :>>>In article <342F3E86.4012@focus.winternet.com>, :>>>Trev Peterson <tpeterso@focus.winternet.com> wrote: :>>>>I am having problems with a Boca Office Communicator FDV34SVD PNP :>>>>fax/modem. When the modem is in the mouse locks up in OS/2 V4.00. I :>>>>checked this using Win95 to verify that it worked there and it did. :>>>> :>>>disable one of your comports if it is an internal modem :>> :>> :> :> :> :>------- :>Ed Wellner :>Yes, these are my opinions, not those of the company I work for. :> There are a couple things you can try. First, if there are jumpers on the modem for com port and irq make sure you have them set correctly. If you have and OS/2 still doesn't recognize it, reboot with full hardware detect and then look at the Hardware Manager. Find out what hexadecimal port address the modem is using, and what irq. If these aren't reflected in the hardware manager, bring up an OS/2 window and type: rmview/dc |more then scroll through all of the details until you find the modem and write down the port address and irq. Next you can revise your com.sys line in your config.sys file like this: device=x:\os2\boot\com.sys (n,addr,irq) n=com port addr=port address irq=irq So if you want com3 at port address 3E8H to use irq 7, then type: x:\os2\boot\com.sys (3,3E8,7) This should work as long as nothing else is using this address and irq.
Technical Details
Message-ID:
<640oht$af3@dfw-ixnews8.ix.netcom.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<c1.01.2GzH8q$03A@warped.connexus.apana.org.au> <DtMT0UjRQE7f092yn@netcom.com> <637nse$qb0@tandem.CAM.ORG> <63a458$qg0@interserv.etn.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 129949,d31bbea4bf0ece5e X-Google-Attributes: gid129949,public X-Google-Thread: 10a752,d31bbea4bf0ece5e X-Google-Attributes: gid10a752,public X-Google-Thread: f9960,d31bbea4bf0ece5e X-Google-Attributes: gidf9960,public X-Google-Thread: f4337,d31bbea4bf0ece5e X-Google-Attributes: gidf4337,public X-Google-Thread: 107fbf,d31bbea4bf0ece5e X-Google-Attributes: gid107fbf,public From: cjj@ix.netcom.com (Charlie Jager) Subject: Re: Plug and Pray problems in Warp 4 Date: 1997/11/08 Message-ID: <640oht$af3@dfw-ixnews8.ix.netcom.com> X-Deja-AN: 287812359 References: <c1.01.2GzH8q$03A@warped.connexus.apana.org.au> <DtMT0UjRQE7f092yn@netcom.com> <637nse$qb0@tandem.CAM.ORG> <63a458$qg0@interserv.etn.com> Organization: Netcom X-NETCOM-Date: Fri Nov 07 10:07:25 PM CST 1997 Newsgroups: comp.os.os2.setup.misc,aus.computers.os2,comp.os.os2.setup,comp.os.so2.bugs,comp.os.os2.multimedia,comp.os.os2.setup