TIP: Click on subject to list as thread! ANSI
echo: os2hardware-l
to: All
from: `Steven Levine`
date: 2006-02-07 01:51:52
subject: Re: [OS2HW] Need an internal PCI modem

In , on 02/07/06
   at 05:18 AM, "kish_44"  said:

>From what you have been saying, it seems clear that I need to set up
>DEVICE=C:\OS2\BOOT\COM.SYS  Where I need help is in setting the
>parameters that follow at the end of that line. As far as the IRQ is
>concerned, '9' is available and '4' is not being used
"exclusively" in my
>environment.

You need to figure out what port and irq the BIOS has assigned.  This is a
job for pci.exe, as I stated previous.  Get a copy of

 pci104vka.zip    526703 2005/10/13  PCI+AGP bus sniffer

from Hobbes.  Install it and run it and look at the captured output.  Your
modem will be reported along with the port and irq you need to use. 
Specify this on the com.sys command and you are one step closer to being
done.

>The format for the COM.SYS parameter is (P,AAAA,I), with 'P' being the
>COM Port number, 'AAAA' being the address location, and 'I' being the
>IRQ.  Right?  Thus, I would have something like '(5,AAAA,9)', with you
>giving me some guidance about determining the value of 'AAAA'.

This is the format you need to use.  Pci.exe will tell you the values of
AAAA and I.  It's not my hardware.  There's no way I can know the values
that your hardware is going to choose. :-)

>Is there a WebSite that defines the possible values of 'AAAA'?

There are thousands of them.  For PCI devices, AAAA is typically between
A000 and FFFF, but knowing this will not help you.

>Do they
>have a direct relationship to 'P', the COM port value?

Only the one you specify on the command line.

>As long as I can
>press  to see the BIOS information for the modem as it scrolls
>across the screen, do I need to download and run 'pci.exe'?

If you can read off the values from the BIOS display, it's going to be
same values pci.exe  would report.

>And,
>finally, when you refer to the "SIO 2.x version shipped with
eCS", how do
>I make use of it?  Has it just been combined into 'COM.SYS', or is there
>something I have to do in a DEVICE or BASEDEV statement?

It's a complete replacement for com.sys and vcom.sys.  I recommend you try
to get up and running with com.sys.  I'll be somewhat surprised if it does
not work.  If it doesn't work, then give SIO 2.x a try.  Here's one way I
used to used to set it up

 device=f:\sio2k\uart.sys logfile=f:\sio2k\sio2k.log
 device=f:\sio2k\vsio2k.sys logfile=f:\sio2k\sio2k.log vIrqList(4)
 device=f:\sio2k\sio2k.sys logfile=f:\sio2k\sio2k.log

Steven

-- 
----------------------------------------------------------------------
"Steven Levine"   MR2/ICE 2.67
#10183 Warp/eCS/DIY/14.103a_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------



 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---
* Origin: Waldo's Place USA Internet Gateway (1:3634/1000)
SEEN-BY: 633/267 270 5030/786
@PATH: 3634/1000 12 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.