开云体育

I downloaded all the RXTX development package and tried to build it but it looks like it is intended to be built using a Linux system that maybe cross compiles for win32. So I didn't get very far with

This is great! We've been hacking around in some quite complicated code trying to fix this. It's only (so far) a problem on Windows, and I've be very happy to add the JNI code to call that

apps? The problem is that the javacomm package uses the serial driver's list of valid baud rates which doesn't include 16457. You can get around this under windows (don't know about unix) by getting

Bob, I'm not very competent in UNIX or Java so I am wondering if it will be possible to get the Windows RXTX API code from the jmri download site. I am interested in trying it out if I can get it.

The RXTX folks have two versions of their library, called 1.4 and 1.5. The member function names and arguments, classnames, functionality, etc, are identical between the two. Version 1.4, which is

I'm not an expert on this topic, but I did do some related work for Linux and as a result suspect that rxtx will replace the suncomm library on Windows. This is how it is used on Linux - remove

I've downloaded both the RXTX stuff and the MinGW package that appears to be the Win32 development package for RXTX on Win32, which thankfully does not require the while MS Developer Studio (virus) to

That would be _great_! The code comes from http://www.rxtx.org. It's what Mike Davison set up for comms on Linux. I've been working with the 1.4 version 15 from rxtx-1.4-15.tar.gz on their download

I have got a long custom HotSync cable for my Palm to do something with Java and JMRI on it. I wondered about just displaying a throttle Widget on the Palm with most of the work being done on the

Got a URL for this one - I may be able to have a look, we have the MSDN kit at work with _all_ the MS dev tools and libraries. Only problem is your machine just isn't the same after you load it

I have a loptop that won't set teh correct serial port speed for JMRI either. It does run the MS100 correctly using WINLOK. Dale. apps? this.

Sounds like an interesting project. Although I've not looked at it in any detail, I think most of the communications stuff should go over pretty cleanly. So you'll be able to talk to the various DCC

The LocoBuffer will almost certainly work. It uses standard serial speeds. I've never heard of somebody having trouble with those. The MS100 needs a non-standard speed, or a specific alternate. On

Greg, You need to check the settings for the port. It is probably defaulting to 9600 speed, and just needs to be reset to a higher maximum setting. Assuming you have Windoze installed, look at

My hunch is that this is an operating system rather than a hardware issue. PC serial ports have been doing 56K for man years. I assume you're using Windows. I know nothing about Windows so I can't

Bob: Would "Typical" work for "General"? Jim Hanna

widget. Maybe a scrollable list of decoder names, with up to 10 showing? That would make it clear that there are multiple choices, because you could see the alternatives. The scroll bars would

I think there are several causes of confusion that are really different. Maybe it would help to think about them seperately? a) "The Ident button picked the wrong decoder!" Some of these are

Well, I installed JMRI on my 1 year old laptop and it says that my COM port can only be set to 9600. I don't understand the reasons why. Anyway, if this is true for JMRI, what about other loconet

I've already ordered my Zephyr with the guy who did the obsolete Digitrax list. He doesn't take CC's you need to send a check. I think this is probably the best deal out there. Paste from his