i tried dosbox this way:
serial1=nullmodem server:127.0.0.1 port:5555 transparent:1 rxdelay:0
serial2=nullmodem server:127.0.0.1 port:6666 transparent:1 rxdelay:0
vspe with two serial ports: com1 port 5555 and com2 port 6666 in tcpserver mode
i use two usb-serial adapters (one is ch340 chip based and the other is prolific2303 chip based)
i tried on xp with uniscan visa 1.83, when i select car, ecu and fault code, L-line led blinks ok trying to wake up ecu for some seconds (although my 1993 corsa-b c14se doesnt have L-line) then K-line led should start blinking but it doesnt (different unsupported baudrate?)
i tried usb-serial adapters in different usb ports (the same adapter as com1 and then as com2), l-line led always blink, if i unplug adapter from interface it stops blinking, when i replug it continues blinking so tcpserver mode is working, interface communicates through usb-serial adapter with visa software
maybe it will never work:
"You cannot run Uniscan software from any version of Windows even in a command window due to com port referencing in the Uniscan software not being Windows compliant.
I have not heard of anyone who has managed to get the Uniscan to work with a USB to serial lead, DOS does not recognise these adaptors.
I have it running on a desktop with 2x com ports and dos/windows 98 installed and also on a laptop with one onboard com port and 1x ruggedized 16bit PCMCIA to serial card made by SOCKET.
16 bit PCMCIA cards are harder to find but you can still buy them, they are marketed more towards commercial buyers who are still using powerful DOS software in industry, also some people use them to get a second com port for weather station software running in DOS.
32bit PCMCIA cards will not work with Uniscan."
source: http://www.obd-codes.com/forums/view...p=14979#p14979
Bookmarks