Torsten ..

 TB> Hallo Kevin!

 TB> Sonntag, den 10. April 2005 17:53, Kevin Nunn schrieb an Mike Luther:

 KN> SIO setup in the config.sys file is generic, posting just in case
 KN> DEVICE=C:\SIO\SIO.SYS (COM1,3F8,4,-) 
 KN> (COM2:115200,INTERNET:2F8,NONE:3,-)
 KN> (COM3:115200,INTERNET:3E8,NONE:4,-) 
 KN> (COM4:115200,INTERNET:2E8,NONE:3,-)
 KN> DEVICE=C:\SIO\VSIO.SYS
 KN> DEVICE=C:\SIO\vx00.sys

 KN> If there is anymore info that I can provide, let 
 KN> me know and thanks for
 KN> helping me try to figure this out.

 TB> I think, you are useing the serial ports of your
 TB> motherboard. Afaik sio can't access irq-shared com-
 TB> ports. So, just give every com-port a different irq in 
 TB> your bios. Or, use one of the serial-multiport-cards 
 TB> as they are listed in sio.inf.

I think I see what you are saying.  That by specifying that the IRQ is hard
coded in the setup line for IRQ3 and IRQ4 like that, you suggest that is
where the conflict arises?  As I understood his post, he had only ONE
actual hard cable connected modem in this setup.  That was the COM1 device.
 It normally is on IRQ4 and has to be known as that way to SIO or SIO2K per
what I think I understand.

I, in fact, use a four port hard coded serial board on this BBS box here. 
While it is an ISA-type card, and it has the ability to define and set up
each COMM port with a different IRQ specified and that is the way I used
it, it also *CAN*, share the same IRQ for all the ports, even in an ISA
slot.  That because of special design and driver work. However, I don't do
that common IRQ driver operation.  I use separate IRQ's for each port.  As
has been posted for a long time, OS/2 can share the same IRQ for different
driver purposes.  However that is dependent on the fact that the drivers
which do this stunt have all been coded very carefully to allow this.  You
saw this heavily on the old COMPAQ computer systems which were shipped with
OS/2 long ago and also were shipped with custome made Adaptec SCSI
controller cards, as well as hard disk drives that were carefully specified
to be compatible with these common single IRQ use techniques.

I never caught that conflict IRQ use in his post.  But SIO and SIO2K both
don't normally care about merged IRQ assignments for multiple internet
ports, as I understand this.  Thus, here are the two different CONFIG.SYS
lines for my system here with four hardware ports and the additional
internet ports that work just fine here:

  DEVICE=C:\SIO\SIO.SYS (COM1:57600,03F8,4,-) (COM2:57600,02F8,3,-)
  (COM3:9600,03E8,15,-) (COM4,02E8,12,-) (COM5,INTERNET:02A8,11)
  (COM6,INTERNET:02B8,11)

Obviously that above is all on one line.  Or in the case of SIO2K here:

  device=C:\sio2k\uart.sys logfile=C:\sio2k\sio2k.log
  device=C:\sio2k\vsio2k.sys logfile=C:\sio2k\vsio2k.log
  vIrqList(1=4,2=3,3=15,4=12)
  device=C:\sio2k\vx00.sys
  device=C:\sio2k\vmodem.sys logfile=C:\sio2k\sio2k.log NoPause nPorts=1
  device=C:\sio2k\sio2k.sys logfile=C:\sio2k\sio2k.log

I don't use a PS/2 style mouse.  It is a serial port mouse that is fed to
my beloved ROSE rack mount KVM switch operation.  Thus in this case the
IRQ12 is available for that COM4 use above which otherwise would be in
conflict with the PS/2 type mouse.

Notice the two internet ports configured in that COM5 and COM6 SIO
operation above that use different ports but the same IRQ?  As far as I
know the software simulated ports in SIO and SIO2K can handle the internet
port creation stuff just fine with a common IRQ specified.  But I don't
assign that to an IRQ which is used elsewhere in hard coded ISA or hardware
board level COMM port work.  And I do not use any of the normal
communications ports for an internet port with SIO either,


--> Sleep well; OS/2's still awake! ;)

Mike {at} 1:117/3001


--- Maximus/2 3.01