| Ticket UUID: | e67618079ff8e8c6b3b4c92fd9b59fb0cf117595 | ||
| Title: | Win rdp forwarded serial port: setting -sysbuffer gives "can't setup comm buffers: invalid argument" | ||
| Type: | Bug | Created on: | 2020-04-22 13:39:55 |
| Submitter: | oehhar | Assigned to: | jan.nijtmans |
| Subsystem: | 27. Channel Types | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2020-04-22 14:37:36 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | 8.6.10 | ||
| Description: | ||||
|
A Windows 10 computer screen is forewarded to a ThinClient (Linux) via rdp protocoll. A physical serial port on the Thin Client is forewarded to the WIndows 10 computer by the same rdp connection. Wish8.6.10 is started on the Windows computer:
% set h [open COM2 RDWR]
file3903678
% fconfigure $h -mode 19200,n,8,1 -buffering full -blocking 0 -translation binary
% fconfigure $h -sysbuffer 32768
can't setup comm buffers: invalid argument
% fconfigure $h
-blocking 0 -buffering full -buffersize 32768 -encoding binary -eofchar {{} {}}\
-translation {lf lf} -mode 19200,n,8,1 -pollinterval 10 -sysbuffer {4096 4096} -xchar { }
% fconfigure $h -sysbuffer 4096
can't set comm state: no such device
Setting the option "-sysbuffer" for the forewarded serial port causes different error messages:
Thank you all, Harald | ||||
| User Comments: | ||||
jan.nijtmans added on 2020-04-22 14:14:17:
Please try: [8b444e9115ef688c] According to Microsoft's documentation, SetCommState() has some restrictions. This might help, but I cannot test it. oehhar added on 2020-04-22 14:27:38:
Light speed, will test. To add, the option "-handshake" also fails in this situation. All other options are ok. Thank you, Harald oehhar added on 2020-04-22 14:37:36:
Sorry, but it is still the same error. Thank you, Harald | ||||
