Open MarkJeronimus opened 6 months ago
I just tested 2.11, which is not on the main webpage, and it works on Windows.
Maybe your Windows is 32bit? I have seen issues related to 32bit systems recently (e.g. https://github.com/Fazecast/jSerialComm/issues/555 and others).
You are absolutely correct, but for me it seems to be fixed in 2.11.
You are lucky then :) As I read in the comments the issue is a tough one :( If you are not in a hurry maybe wait for and test the final 2.11.1 version as well...
Yes, 2.11.1 will fix what appears to be a compiler optimization issue for Win32 users. Just for clarification, you said that 2.11.0 works for you, but not from the main webpage...what do you mean by that (i.e. what page are you referring to, and are you saying that 2.11.0 is working differently depending on where you got it from?)
I mean that on the main web page I downloaded 2.10.0 today. I only found out about the existence of 2.11 when visiting the repository.
Very odd. Are you still seeing 2.10.0 on that page? It's showing 2.11.0 for me (and it gets auto-updated upon each new release).
It was showing 2.11 at the time I wrote the previous reply.
When invoking
SerialPort.getCommPorts()
on Windows 10 [edit] 32 bit, the program exits without exception or any other message, as if by System.exit(). I have no idea how to check if there's an errorlevel.On Linux, 2.10 works. On Windows, 2.7 works. [edit] On Windows, 2.11 works.
Test case:
Output:
Additional information: