Author Topic: PSCOM.SYS problem  (Read 4820 times)

Igor

  • Jr. Member
  • **
  • Posts: 99
  • Karma: +12/-0
    • View Profile
PSCOM.SYS problem
« on: December 15, 2022, 10:22:19 pm »
When loading the system, I see:

DEVICE=C:\OS2\BOOT\PSCOM.SYS (1,A010,21) (2,A000,23) /V

COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO
COM2:    0xA000      23    No    16450    1

The parameter is determined here UART: 16450
This is not true.

From output pci.exe:
 Bus 6 (PCI Express), Device Number 0, Device Function 0
 Vendor 125Bh Asix Electronics Corporation
 Device 9100h Unknown
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 00h, Header Type 80h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Simple Communication, type Serial - 16550
 Subsystem ID 1000A000h Unknown
 Subsystem Vendor A000h Unknown
 Address 0 is an I/O Port : A010h
 Address 1 is a Memory Address (0-4GiB) : F0803000h
 Address 2 is not present or not configured!
 Address 3 is not present or not configured!
 Address 4 is not present or not configured!
 Address 5 is a Memory Address (0-4GiB) : F0802000h
 System IRQ 21, INT# A

 Bus 6 (PCI Express), Device Number 0, Device Function 1
 Vendor 125Bh Asix Electronics Corporation
 Device 9100h Unknown
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 00h, Header Type 80h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Simple Communication, type Serial - 16550
 Subsystem ID 1000A000h Unknown
 Subsystem Vendor A000h Unknown
 Address 0 is an I/O Port : A000h..A007h
 Address 1 is a Memory Address (0-4GiB) : F0801000h
 Address 2 is not present or not configured!
 Address 3 is not present or not configured!
 Address 4 is not present or not configured!
 Address 5 is a Memory Address (0-4GiB) : F0800000h
 System IRQ 23, INT# B

How to make two comports with correct parameters (UART: 16550) be determined?

Tom

  • Full Member
  • ***
  • Posts: 197
  • Karma: +5/-0
    • View Profile
Re: PSCOM.SYS problem
« Reply #1 on: December 15, 2022, 11:16:44 pm »
When loading the system, I see:

DEVICE=C:\OS2\BOOT\PSCOM.SYS (1,A010,21) (2,A000,23) /V

How to make two comports with correct parameters (UART: 16550) be determined?

Try using two 'device=' lines: one with (1,A010,21) /V and one with (2,A000,23) /V

device=c:\os2\boot\pscom.sys (1,A010,21) /V
device=c:\os2\boot\pscom.sys (2,A000,23) /V


Roderick Klein

  • Hero Member
  • *****
  • Posts: 665
  • Karma: +14/-0
    • View Profile
Re: PSCOM.SYS problem
« Reply #2 on: December 16, 2022, 12:27:59 am »
As try adding /F (I think that was the switch). that forces the driver to scan the PCI bus for serial controllers.

Roderick

Igor

  • Jr. Member
  • **
  • Posts: 99
  • Karma: +12/-0
    • View Profile
Re: PSCOM.SYS problem
« Reply #3 on: December 19, 2022, 12:14:46 pm »
Try using two 'device=' lines: one with (1,A010,21) /V and one with (2,A000,23) /V

device=c:\os2\boot\pscom.sys (1,A010,21) /V
device=c:\os2\boot\pscom.sys (2,A000,23) /V

It is very strange to me. Previously, I have never seen two lines when loading the drivers of comments.
When trying to add two lines, the load stops on the first line with the message SYS1201 and Press Enter to continue.

After pressing the Enter, the system works even more strange. The next line loads 2 ports, but the interruptions are not specified correctly and the UART is different for different ports!

DEVICE=C:\OS2\BOOT\PSCOM.SYS (1,A010,21) /F /V
COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO

DEVICE=C:\OS2\BOOT\PSCOM.SYS (2,A000,23) /F /V
COM.SYS: Asynchronous Communications Driver v1.21
COM.SYS:   Addr     IRQ   Sharing    UART   FIFO
COM1:    0xA010      3    No    16550    16
COM2:    0xA000      23    No    16450    1


UPD
In the case of two lines after loading, the core is 14.203 when contacting comports, it goes into a trap.
The nucleus of the OS4 remains stable and even allows you to set the speed of 115200 for the port, where UART 16550 is determined.
Further tests were not carried out. It seems to me that still somewhere there is a mistake when loading drivers.
« Last Edit: December 19, 2022, 04:51:25 pm by Igor »

Wim Brul

  • Sr. Member
  • ****
  • Posts: 295
  • Karma: +25/-0
    • View Profile
    • Wim's home page
Re: PSCOM.SYS problem
« Reply #4 on: December 21, 2022, 10:04:04 am »
Blonde Guy has some notes on Serial Cards on eComstation.

It say a.o. and I quote "The PSCOM.SYS driver supports the /F option, and along with specifying the built-in motherboard ports makes this and a lot of other serial cards work."

Reading the notes I think you will have just to specify:

DEVICE=C:\OS2\BOOT\PSCOM.SYS /F /V (1,3F8,4) (2,2F8,3)

even when there are no built-in motherboard ports.

Igor

  • Jr. Member
  • **
  • Posts: 99
  • Karma: +12/-0
    • View Profile
Re: PSCOM.SYS problem
« Reply #5 on: December 22, 2022, 10:08:34 pm »
Blonde Guy has some notes on Serial Cards on eComstation.

It say a.o. and I quote "The PSCOM.SYS driver supports the /F option, and along with specifying the built-in motherboard ports makes this and a lot of other serial cards work."

Reading the notes I think you will have just to specify:

DEVICE=C:\OS2\BOOT\PSCOM.SYS /F /V (1,3F8,4) (2,2F8,3)

even when there are no built-in motherboard ports.
Thank you so much. That helped.
However, I received two fake comports with numbers 1 and 2. Real comports took numbers 3 and 4. The attempt to change them failed. As I understand it, this is the only way to use external ports.

Among other things, it goes only with the original core. The core of OS4 does not find external comports.