Parity bit error in v1.5.0.0?
The virtual serial port driver for Windows.
Brought to you by:
vfrolov
Using:
* com0com version 1.5.0.0.
* Two HyperTerminal sessions connected at 9600 baud, 8
data bits, no parity, 1 stop bit, Xon/Xoff flow
control.
Three or more repeated characters appear to cause a
toggling of the parity (most significant) bit in the
output.
eg An input of:
00000000000
produces an output of:
00°0°0°0°0°
ASCII value of '0' is 48, '°' is -80. (48 - 128 = -80)
Logged In: YES
user_id=918965
I can't reproduce this bug.
Possible HyperTerminal do it.
Check terminal emulation options.
Logged In: NO
Thank you for the quick response.
Tried again with HyperTerminal default settings:
2400 baud, 8 data bits, no parity, 1 stop bit, hardware
flow control.
Following input:
11110000000011111111
produces the following output:
111100°0°0°011±1±1±1
Error occurs with HyperTerminal emulation set to "Auto
detect" as well as "ANSI".
Not sure if it is relevant, but used the registry to rename
the ports to COM5 and COM6.
Logged In: NO
[Posted a comment already, but it didn't seem to show up]
Thank you for the quick response.
Tried again with HyperTerminal default settings:
2400 baud, 8 data bits, no parity, 1 stop bit, hardware
flow control.
Following input:
11110000000011111111
produces the following output:
111100°0°0°011±1±1±1
Error occurs with HyperTerminal emulation set to "ANSI" as
well as "Auto detect".
Not sure if it is relevant, but have used the registry to
rename the ports to COM5 and COM6.
Logged In: NO
[Posted a comment already, but it didn't seem to show up]
Thank you for the quick response.
Tried again with HyperTerminal default settings:
2400 baud, 8 data bits, no parity, 1 stop bit, hardware
flow control.
Following input:
11110000000011111111
produces the following output:
111100°0°0°011±1±1±1
Error occurs with HyperTerminal emulation set to "ANSI" as
well as "Auto detect".
Not sure if it is relevant, but have used the registry to
rename the ports to COM5 and COM6.
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).