@Gelip

I did step by step exact what you wrote.

Does not work.

On second boot step of XP there is no connection to the PCIe slotcard on the Asrock z370 k6 board, no matter which (now I have 5 different cards) you use for this

Dietmar

PS: Sundos shows D000 & COM1

and an extra test confirm this with

debug

-d 40:0 confirms Com port on COM1 with 00 D0.

 

@Dietmar

Then it must be the motherboard's fault. It is definitely not the fault of WinXP or the SER5427A PCie card

@Dietmar

12 hours ago, Dietmar said:

On second boot step of XP there is no connection to the PCIe

What second boot? If you want to use the RS232 PCIe card under DOS you cannot restart the computer! The BIOS cannot configure the COM port on the PCIe card by itself. You have to do it manually by inserting the I/O address into memory, e.g. with debug -e 40:0 xx xx

Edited February 7, 20223 yr by Gelip

@Gelip

Hi,

I do not mean restart of compi. Just the second boot stage of XP,

when you see the running bar. Then, connection is lost

Dietmar

@Dietmar

3 minutes ago, Dietmar said:

when you see the running bar. Then, connection is lost

How do you know the connection is lost?

@Dietmar@Gelip

Have either of you tried Windbg via firewire? - there is a kd1394.dll - I'm assuming that's firewire?

@infuscomus

I am happy that with my RS232 cards - ExpressCard and PCIe works WinDbg for WinXP 32/64-bit 😀

I also checked KDNET for WinXP 32-bit and works and I am more interested in KDNET 64-bit: KDNET for WinXP/2003 64-bit

FireWire and USB do not interest me.

Edited February 8, 20223 yr by Gelip

@Gelip

I just notice, that normal serial Windbg does not work on new motherboards with z690 chipset: Not on the Biostar z690A and also not on the Gigabyte z690 ud ddr4 .

Crazy, because they have onboard serial COM and sundos shows COM1 port at 3f8h on both of them

Dietmar

Edited February 8, 20223 yr by Dietmar

2 hours ago, Dietmar said:

Crazy, because they have onboard serial COM and sundos shows COM1 port at 3f8h on both of them

This is not crazy. If there are COM ports on the motherboard and they are enabled in the bios, sundos.exe detects these ports:

@Dietmar

I have good news. So far, I have tested the SER5427A card with WinDbg + modified kdcom.dll in legacy bios only. Today I decided to check under UEFI (CSM disabled) and it does not work.

I noticed an important thing when the card driver is not installed in Windows. In UEFI mode, the lspci utility under WinXP shows that the I/O ports are disabled, while in legacy bios they are enabled:

For WinDbg to run under UEFI, you need to enable ports under UEFI Shell and run WinXP without restarting from UEFI Shell:

mm 03000004 1 -pci
efi\boot\bootx64.efi

Maybe your motherboards disable I/O ports in legacy bios mode?

Check in WinXP with lspci that the I/O ports are enabled. If they are disabled, enable them in MS-DOS with the setpci utility and run WinXP with GRUB4DOS without restarting the computer:

setpci -s xx:xx.x command=1
grub.exe

Edited February 15, 20223 yr by Gelip

@Gelip

My pic looks exact like your first, where you write, that Windbg works.

But does not work on Asrock z370 k6.

I set in boot.ini /baudrate=14400

in Windbg 115200

and I use the for D0 00 modded kdcom.dll.

I even try Windbg with setpci -s, same result.

 

On the z690 boards, even with integrated COM port, serial debug does not work any longer but serial mouse works

Dietmar

 

@Dietmar

Are you sure you are configuring the correct device for the bus:slot.func ??? In this post link you showed that all PCIe RS232 cards are under 02:00.0 and 03:00.0 is your SATA controller

At 03:00.0 is my PCIe card!