In , on 02/10/06
   at 02:26 AM, "kish_44"  said:


>COM.SYS  Data:  8-02-02 4:20p  Size:  25,431
>I started with eCS 1.24 and upgraded to 1.25 last Fall.  But, I haven't
>touched COM.SYS.

This is probably

bldlevel F:\OS2\BOOT\COM_PCI.SYS
Build Level Display Facility Version 6.10.480 Oct  6 2000
(C) Copyright IBM Corporation 1993-2000
Signature:       {at}#IBM:10.078#{at} COM Port Driver-UNI
Vendor:          IBM
Revision:        10.78
File Version:    10.78
Description:     COM Port Driver-UNI
dir /km F:\OS2\BOOT\COM_PCI.SYS
 8-13-02  14:20          25,431           0  COM_PCI.SYS

This is the PCI capable version of com.sys.  The last ISA only version
that I am aware of reports itself as

bldlevel F:\OS2\BOOT\COM_ISA.SYS
Build Level Display Facility Version 6.10.480 Oct  6 2000
(C) Copyright IBM Corporation 1993-2000
Signature:       {at}#IBM:10.036#{at} COM Port Driver-SMP
Vendor:          IBM
Revision:        10.36
File Version:    10.36
Description:     COM Port Driver-SMP
dir /km F:\OS2\BOOT\COM_ISA.SYS
 6-16-00  10:46          18,719           0  COM_ISA.SYS

>Now, here's an Alice in Wonderland finding:

>Along with my modem problems, I've been having trouble getting my system
>to recognize my Adaptec AHA-2940 card, so I pulled it out tonight before
>booting up.  When eCS came up, I ran an RMVIEW /DA and compared it to the
>previous RMVIEW /DA that I had used to get the address for the PCI modem. 

Did you reboot with full hardware detection?  If not, the rmview output
can be misleading.

>The compare showed that a number of IRQ's had changed from '5' to '10' -
>mostly for USB devices.  (At the moment, I'm not using any USB devices,
>so that's irrelevant.)  But, it didn't show any indication of the Adaptec
>card,

I happen to have one of these installed.  rmview /da reports is as

Driver: AIC7870.ADD  -  Adaptec 7800 Family Driver for OS/2
Vendor: Adaptec  Version: 1.1  Date (MDY): 10/15/2001
Flag:   STATIC     Type-Subtype: ADDDM - ADD

  Adapter: AIC7870_0 Adaptec 7800 Family SCSI Adapter
  Device Type: MS-SCSI        Bus/Width: PCI 32 BIT
  I/O = 0XB000  Len =  16  Flg = EXCLUSIVE   Addr Lines = 16
  IRQ Level = 10  PCI Pin = NONE  Flg = SHARED

Of course, the driver needs to be loaded for this data to appear.

>However, to my dismay, I saw that the values for the PCI modem had
>changed from I/O = 0XDC00 to I/O = 0XE000 and from IRQ5 to IRQ10.

This is not unusual.

>Of course, I said to myself the modem isn't going to connect without
>going into CONFIG.SYS and changing COM.SYS (5,DC00,5) to COM.SYS
>(5,E000,10).  But, just for the heck of it, I decided to try to dial out. 
>And it DIALED!

Take a look in pcidev.tbl.  If your modem is listed, com.sys will detect
it without your help.  Based on what you are saying, this appears to be
the case.

>Oh, yeah, MODE COM2 still reflects the status of the modem.

Now that I know you are using the pci capable com.sys, this is expected. 
The driver assigned com1 to the internal serial port and com2 to the pci
modem.  It may have also attempted to assign com5 to the same modem
because you told it too, but the assignment appears to have failed, as it
should.

I recommend you try deleting the command line options from the com.sys
device statement and see if the modem continues to work as com2.  I expect
it will.

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/
 




---