开云体育

I've uploaded a version 0.9.4 for those of you without Windows:

MacOS X:

MacOS 8/9:

Linux:

OS/2:

People didn't like the "one size fits all" distributions, mostly because they contain lots of irrelevant & confusing files on any given machine, so I've gone back to creating separate distributions. The tools to create these are new, however, so I'd appreciate it if people could try the download for their particular machine and let me know if it works.

Having separate installers also lets us see how many people use each one. That will be interesting. Vote early and often...

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Hi Bob,

Can you confirm that we are now using both the Sun commapi and the new
SerialIO packages or are we just using the new SerialIO
I just did a CVS update/compile and it looks like it uses both. It all seems
to work on my PC when I put the commapi bit back. Is this expected
behaviour?

Alex

At 1:32 PM +1200 7/14/02, Alex Shepherd wrote:

Hi Bob,

Can you confirm that we are now using both the Sun commapi and the new
SerialIO packages or are we just using the new SerialIO
I just did a CVS update/compile and it looks like it uses both. It all seems
to work on my PC when I put the commapi bit back. Is this expected
behaviour?

The MS100 class is the only one that uses the Serialio. It tries to reference the Serialio class; if that succeeds, it uses it. If that fails, it falls back to using the javax.comm. All of the other serial adapters (LocoBuffer, EasyDCC, Lenz/Atlas, NCE, C/MRI) only use the javax.comm stuff. So on Windows, both should be present; on anything else, just the javax.comm is needed. (Serialio would work for the MS100 on other platforms, but its not really needed, and we don't have either a license nor the code)

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)