🚀 go-pugleaf

Well,

Assuming this is a decent PnP device, and you've
run hardware detection after its installation,
then rmview /dc from the commandline SHOULD
show you where the modem was configured.

It should NOT be needed to redo detection on
EACH boot however (if this is a good PnP 
device) as we (my code) will reconfigure
it to the SAME place as last time detection
was run..

Now.. I have a tweak to the ISAPNP configurator
I'd like you to try, and will send you an offline
note with code and instructions..

In answer to your 'specific' question,

Os/2 System->System Setup->Hardware Manager-Properties,
Default Detection level, full Hardware Detection..

(only time I've seen this is on a Crystal 
based sound card where the .SNP programs
the adapter)



Stan Koper wrote:
> 
> 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?
> 
> 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.
> >

-- 
Sam Detweiler
IBM OS/2 Development
Device Driver development and Support
OS/2 Advisor