New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confirm serial connections are working properly on Windows 11 #233
Comments
I have a similar issue, while it appears to be possible to select a null modem in the gui, this doesn't seem to pass back to the command line. There is no way to set line [device name], I am using a usb to serial cable, which Window Control Panel says is Com3: |
Further investigation has determined that the port assignment can be found in device manager (COM3) and can be set in C-Kermit by |
I think the USB-Serial device I was originally having trouble with may just be faulty (PuTTY couldn't use it either). Around that time one or two other people had raised issues with using USB-Serial devices on modern windows too though so figured a bit more testing was warranted. I did a bit of that a few days back with another less generic USB-Serial device and it worked fine so might just be a combination of user error or specific devices having issues with recent Windows releases. The old GUI Dialer app does have a selection of issues but unfortunately they're all a bit tricky to solve the app is pretty firmly trapped in the 90s due to a few 3rd party things it depends on. I plan to just rewrite it from scratch eventually. |
I had some difficulty when trying to use a USB Serial device on Windows 11 recently. PuTTY would connect to it but CKW Beta.04 just reported an error.
Could be user error, or a windows 11 incompatibility, or perhaps there really is a bug - perhaps 64bit related if so.
The text was updated successfully, but these errors were encountered: