From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj@www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 14 23:21:55 2006 Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 18:25:16 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 18:25:18 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj@www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Tue Mar 28 18:25:18 2006 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 18:25:18 2006 Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx@linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous@cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces@linuxgrrls.org [mailto:rxtx-bounces@linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj@www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx@linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj@www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx@linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj@www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx@linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj@www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Tue Mar 28 20:17:14 2006 Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj@www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sun Oct 24 08:58:48 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 15:58:48 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Dodger wrote: > Trent, > > I'm so sorry to bother you again, but I need some help with a windows > installation, if possible. > > I can't seem to find reliable information regarding the placement of the > native libraries and rxtx jar file. > > >From a website: "RXTX is installed by simply copying rxtxSerial.dll into > your /bin folder and copying RXTXcomm.jar into your /lib/ext > folder." > > Am I correct in assuming this information is for the application runtime > only? > > I have just installed JDK 1.5.0, and as you may well know, it installs both > a public and a private JRE: > > Public: Java/jre1.5.0 > Private: Java/jdk1.5.0/jre > > Do the files have to go in both locations? > > Please give me simple directions as to where each of these three files > should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). > > Thanking you in advance, > > Glen. I'm not that familiar with what is right on w32. The dll needs to be in your PATH. The jar file needs to be in your CLASSPATH. The ext directory can be used to make sure that the RXTXcomm.jar is in your CLASSPATH without modifying the environmental variable. I assume this would be Java/jdk1.5.0/jre/lib/ext - some java distributions lack the ext directory as I recall. Usually the 'public' directory just points to the private one. Sun may do this with binaries now but they used to be just shell scripts on UNIX in the 'public' bin directory that setup the environment and then called the 'private' copy. So I would think the dll would go in Java/jdk1.5.0/jre/bin. But as long as the dlls are in your PATH and the jar is in your CLASSPATH, rxtx should work. Its not very clear to me that there is a right way to install the dlls for EXTra/javaX packages on w32. I've always just assumed this was the w32 'dll hell' everyone talks about :) > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 23:43 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Hi Trent, > > > > Thanks so much for your assistance so far. > > > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > > as I'm not too clued up on CVS/build files etc., yet. Just copied the > native > > library and the rxtx jar file; I assume that is all that is required for > > serial comms.? > > > > Anyway...It's working; But, I get an error when doing a simple > enumeration, > > the complete output follows: > > > > Version: RXTX-2.1-7pre17 > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File > exists > > /dev/ttyS1 > > > > I can post the source if necessary. It just prints the version information > > and then enumerates the available serial ports. > > > > I think that that port may be being used by my modem, and the modem may > hold > > a lock on it. If this is so, is this normal behaviour? > > > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > > > > > If the program fails to close a port, the file will still be there. If > you have a program running in another terminal or in the background, the > lock file will be there and for good reason. Inside the lockfile is the > PID of the application that left the lockfile. > > ps up `< /var/lock/LCK..ttyS0` > > Should show which application has the lock. > > ps up `< /var/lock/LCK..ttyS0` > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java > BlackBox -p /de > > Make sure your user is in group lock > > /etc/group > > ... > lock:x:54:rm-rf,jarvi,rxtx > ... > > places users rm-rf, jarvi and rxtx in group lock. Full distributions have > locking libraries that rxtx could use but these are not available on all > systems. > > Finally, make sure your application closes the port before exiting. > > If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try > taking the modem. It would have killed your internet connection. More > often, someone runs an application in one window and then runs it again in > another window. The idea is to prevent applications from reading each > others data. The messages are printed so people know why enumeration > comes up with no available ports when something else has them open. > > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 23 October 2004 19:21 > > To: Java RXTX discussion > > Subject: RE: [Rxtx] Question regarding current versions > > > > > > On Sat, 23 Oct 2004, Dodger wrote: > > > > > Thanks Trent, > > > > > > And as far as portability is concerned? In the case of v2.0 does it just > > > mean that you have to ensure 2 different things are setup correctly for > > each > > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > > linux > > > users, or does it only occur under specific conditions? > > > > > > Thanks again, > > > > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > > this is what was causing problems on BSD and slower w32 machines with > > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > > bring the changes to 2.0 CVS yet. > > > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > > for those that need it. So all OSs use Suns CommAPI for Solaris (even > > w32) and a javax.comm.properties file. > > > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > > documented as extensions. These are not recommeneded but are available in > > 2.1 so its under a completely different namespace. Code can move from > > javax.comm to gnu.io with just a change in the package name for the most > > part but code using gnu.io exensions to commapi can not move back to > > javax.comm without modification (removal of the extensions). > > > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > > documented Methods. The package can be changed to javax.comm and comm.jar > > can be used with rxtx 2.0 later. There are a few people chasing each > > other with vacations but I expect the code in 2.1 CVS is going to be > > released as 2.1.7 and 2.0.7 the second week of November after some formal > > testing. > > > > export > > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > > cvs login (mousy for password) > > cvs checkout -r commapi-0-0-1 rxtx-devel > > cd rxtx-devel > > mkdir build > > cd build && ../configure && make install > > > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > > > Glen. > > > > > > -----Original Message----- > > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > > Behalf Of Trent Jarvi > > > Sent: 22 October 2004 09:37 > > > To: Java RXTX discussion > > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > > > Hi again, > > > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > > > I just wanted to start off with a quick question regarding version > > choice, > > > > and later I may (probably will) require some assistance with the > actual > > > > installation if possible. > > > > > > > > Question (1): > > > > > > > > I'm not sure I understand the difference/s between versions 2.0 and > 2.1. > > > Is > > > > it only a change in API? The one API matching that of Sun, and the > other > > a > > > > non-Sun compliant API? Essentially the question is: What version > should > > I > > > be > > > > using? And what are the pro's and con's of each? > > > > > > > > TIA. > > > > > > > > Glen. > > > > > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > > package name is different to avoid conflicting with Sun's namespace but > > > otherwise its the same. The same methods and classes are available. > > > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under > Sun's > > > namespace. > > > > > > Its all the same code underneath. So The choice is just that. You can > > > use either one. There shouldnt be any advantage of one over the other. > > > When the package is released, the same code is just modified to match > the > > > packages. > > > > > > -- > > > Trent Jarvi > > > taj at www.linux.org.uk > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > _______________________________________________ > > > Rxtx mailing list > > > Rxtx at linuxgrrls.org > > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From neil.benn at gmail.com Sun Oct 24 16:04:19 2004 From: neil.benn at gmail.com (Neil Benn) Date: Sun, 24 Oct 2004 22:04:19 +0000 Subject: [Rxtx] Windows CE Message-ID: Hello, I'm looking for a build of the windows CE port. Does anyone have one available that they could send me (including the corresponding properties and jar files). I can't find the windows CE build. Any and all help is greatly appreciated. Cheers, Neil From taj at www.linux.org.uk Sun Oct 24 16:30:09 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sun, 24 Oct 2004 23:30:09 +0100 (BST) Subject: [Rxtx] Windows CE In-Reply-To: References: Message-ID: On Sun, 24 Oct 2004, Neil Benn wrote: > Hello, > > I'm looking for a build of the windows CE port. Does anyone > have one available that they could send me (including the > corresponding properties and jar files). I can't find the windows CE > build. > > Any and all help is greatly appreciated. > Hi Neil I see there are binaries in rxtx-2.1-6 rxtx-2.1-6.tar.gz -rwxr--r-- root/root 30208 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMDbg/rxtxSerial.dll -rwxr--r-- root/root 19456 2002-09-07 16:13:04 rxtx-2.1-6/WinCE/ARMRel/rxtxSerial.dll These may be dated. I dont know if anyone has built them in a while. There are probably fixes needed to build from current source. The binaries in those files go back to 2002-04-05/rxtx-2.1-2. ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-2.tar.gz would probably be the best place to start. There is a copy of the jar in the MACOSX directory. rxtx-2.1-2/MACOSX_IDE/CW/RXTXcomm.jar Michal Hobbit did the WinCE port. He put a page up at: http://www.mhobot.w.pl/java/comm which also links to an archive of the build he did: http://republika.pl/mho/java/comm/RXTX_iPAQ_0211.zip Along with other options he found at the time. I'm not sure Michal has looked at this in a long time and I've never had a build environment setup for WinCE. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Tue Oct 19 13:48:49 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Tue, 19 Oct 2004 21:48:49 +0200 Subject: [Rxtx] Test - Please Excuse. Message-ID: It seems my last message wasn't delivered; Just sending a test message to confirm. Glen. From mikkal56 at hotmail.com Thu Oct 21 13:04:33 2004 From: mikkal56 at hotmail.com (miguel lam) Date: Thu, 21 Oct 2004 19:04:33 +0000 Subject: [Rxtx] Crash in JVM 1.5.0 with 2.1-7pre17 Message-ID: Please give the url where I can find the patch, PLEASE !!!!!!!!! _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/ From lonedesign_2k at yahoo.com Thu Oct 21 16:20:08 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Fri, 22 Oct 2004 00:20:08 +0200 Subject: [Rxtx] Question regarding current versions Message-ID: Hi again, Not sure what happened the first time, but anyway, here goes again... I just wanted to start off with a quick question regarding version choice, and later I may (probably will) require some assistance with the actual installation if possible. Question (1): I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is it only a change in API? The one API matching that of Sun, and the other a non-Sun compliant API? Essentially the question is: What version should I be using? And what are the pro's and con's of each? TIA. Glen. From taj at www.linux.org.uk Fri Oct 22 01:37:07 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Fri, 22 Oct 2004 08:37:07 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 10:52:01 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 18:52:01 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Thanks Trent, And as far as portability is concerned? In the case of v2.0 does it just mean that you have to ensure 2 different things are setup correctly for each installation (RXTX and Commapi), as apposed to one (RXTX) (?) Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux users, or does it only occur under specific conditions? Thanks again, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 22 October 2004 09:37 To: Java RXTX discussion Subject: Re: [Rxtx] Question regarding current versions On Fri, 22 Oct 2004, Dodger wrote: > Hi again, > > Not sure what happened the first time, but anyway, here goes again... > > I just wanted to start off with a quick question regarding version choice, > and later I may (probably will) require some assistance with the actual > installation if possible. > > Question (1): > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. Is > it only a change in API? The one API matching that of Sun, and the other a > non-Sun compliant API? Essentially the question is: What version should I be > using? And what are the pro's and con's of each? > > TIA. > > Glen. > rxtx 2.1 is a full library and does not require any files from Sun. Its package name is different to avoid conflicting with Sun's namespace but otherwise its the same. The same methods and classes are available. rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's namespace. Its all the same code underneath. So The choice is just that. You can use either one. There shouldnt be any advantage of one over the other. When the package is released, the same code is just modified to match the packages. -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 11:21:05 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 18:21:05 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sat Oct 23 15:19:53 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sat, 23 Oct 2004 23:19:53 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Hi Trent, Thanks so much for your assistance so far. I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', as I'm not too clued up on CVS/build files etc., yet. Just copied the native library and the rxtx jar file; I assume that is all that is required for serial comms.? Anyway...It's working; But, I get an error when doing a simple enumeration, the complete output follows: Version: RXTX-2.1-7pre17 RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists /dev/ttyS1 I can post the source if necessary. It just prints the version information and then enumerates the available serial ports. I think that that port may be being used by my modem, and the modem may hold a lock on it. If this is so, is this normal behaviour? Environment: Red Hat 8.0, Java - JDK 1.5.0 Regards, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 19:21 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Thanks Trent, > > And as far as portability is concerned? In the case of v2.0 does it just > mean that you have to ensure 2 different things are setup correctly for each > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all linux > users, or does it only occur under specific conditions? > > Thanks again, > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure this is what was causing problems on BSD and slower w32 machines with earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to bring the changes to 2.0 CVS yet. All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included for those that need it. So all OSs use Suns CommAPI for Solaris (even w32) and a javax.comm.properties file. RXTX 2.1 exposes some methods that are not part of CommAPI and are documented as extensions. These are not recommeneded but are available in 2.1 so its under a completely different namespace. Code can move from javax.comm to gnu.io with just a change in the package name for the most part but code using gnu.io exensions to commapi can not move back to javax.comm without modification (removal of the extensions). What I'd recommend right now is using rxtx 2.1 from CVS with only Sun documented Methods. The package can be changed to javax.comm and comm.jar can be used with rxtx 2.0 later. There are a few people chasing each other with vacations but I expect the code in 2.1 CVS is going to be released as 2.1.7 and 2.0.7 the second week of November after some formal testing. export CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot cvs login (mousy for password) cvs checkout -r commapi-0-0-1 rxtx-devel cd rxtx-devel mkdir build cd build && ../configure && make install w32 bins (minus some 64 bit fixes which are not needed) can be obtained at ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > Glen. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 22 October 2004 09:37 > To: Java RXTX discussion > Subject: Re: [Rxtx] Question regarding current versions > > > On Fri, 22 Oct 2004, Dodger wrote: > > > Hi again, > > > > Not sure what happened the first time, but anyway, here goes again... > > > > I just wanted to start off with a quick question regarding version choice, > > and later I may (probably will) require some assistance with the actual > > installation if possible. > > > > Question (1): > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > Is > > it only a change in API? The one API matching that of Sun, and the other a > > non-Sun compliant API? Essentially the question is: What version should I > be > > using? And what are the pro's and con's of each? > > > > TIA. > > > > Glen. > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > package name is different to avoid conflicting with Sun's namespace but > otherwise its the same. The same methods and classes are available. > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > namespace. > > Its all the same code underneath. So The choice is just that. You can > use either one. There shouldnt be any advantage of one over the other. > When the package is released, the same code is just modified to match the > packages. > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk _______________________________________________ Rxtx mailing list Rxtx at linuxgrrls.org http://mailman.linuxgrrls.org/mailman/listinfo/rxtx From taj at www.linux.org.uk Sat Oct 23 15:42:52 2004 From: taj at www.linux.org.uk (Trent Jarvi) Date: Sat, 23 Oct 2004 22:42:52 +0100 (BST) Subject: [Rxtx] Question regarding current versions In-Reply-To: References: Message-ID: On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the source if necessary. It just prints the version information > and then enumerates the available serial ports. > > I think that that port may be being used by my modem, and the modem may hold > a lock on it. If this is so, is this normal behaviour? > > Environment: Red Hat 8.0, Java - JDK 1.5.0 > If the program fails to close a port, the file will still be there. If you have a program running in another terminal or in the background, the lock file will be there and for good reason. Inside the lockfile is the PID of the application that left the lockfile. ps up `< /var/lock/LCK..ttyS0` Should show which application has the lock. ps up `< /var/lock/LCK..ttyS0` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jarvi 13438 1.6 0.9 1354868 37804 pts/15 T 15:50 0:00 java BlackBox -p /de Make sure your user is in group lock /etc/group ... lock:x:54:rm-rf,jarvi,rxtx ... places users rm-rf, jarvi and rxtx in group lock. Full distributions have locking libraries that rxtx could use but these are not available on all systems. Finally, make sure your application closes the port before exiting. If the modem is using /dev/ttyS0 you should be glad that rxtx didnt try taking the modem. It would have killed your internet connection. More often, someone runs an application in one window and then runs it again in another window. The idea is to prevent applications from reading each others data. The messages are printed so people know why enumeration comes up with no available ports when something else has them open. > > -----Original Message----- > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > Behalf Of Trent Jarvi > Sent: 23 October 2004 19:21 > To: Java RXTX discussion > Subject: RE: [Rxtx] Question regarding current versions > > > On Sat, 23 Oct 2004, Dodger wrote: > > > Thanks Trent, > > > > And as far as portability is concerned? In the case of v2.0 does it just > > mean that you have to ensure 2 different things are setup correctly for > each > > installation (RXTX and Commapi), as apposed to one (RXTX) (?) > > > > Finally, is 'Crash in JVM 1.5.0 with 2.1-7pre17' likely to affect all > linux > > users, or does it only occur under specific conditions? > > > > Thanks again, > > > > The crash in JVM 1.5.0 was more than just a Linux issue. I'm fairly sure > this is what was causing problems on BSD and slower w32 machines with > earlier JVMs too. We have the fix in 2.1 CVS but I have not had time to > bring the changes to 2.0 CVS yet. > > All OSs with rxtx 2.0 are 'UNIX Like' there is a POSIX like layer included > for those that need it. So all OSs use Suns CommAPI for Solaris (even > w32) and a javax.comm.properties file. > > RXTX 2.1 exposes some methods that are not part of CommAPI and are > documented as extensions. These are not recommeneded but are available in > 2.1 so its under a completely different namespace. Code can move from > javax.comm to gnu.io with just a change in the package name for the most > part but code using gnu.io exensions to commapi can not move back to > javax.comm without modification (removal of the extensions). > > What I'd recommend right now is using rxtx 2.1 from CVS with only Sun > documented Methods. The package can be changed to javax.comm and comm.jar > can be used with rxtx 2.0 later. There are a few people chasing each > other with vacations but I expect the code in 2.1 CVS is going to be > released as 2.1.7 and 2.0.7 the second week of November after some formal > testing. > > export > CVSROOT=:pserver:anonymous at cvs.milestonesolutions.com:/usr/local/cvsroot > cvs login (mousy for password) > cvs checkout -r commapi-0-0-1 rxtx-devel > cd rxtx-devel > mkdir build > cd build && ../configure && make install > > w32 bins (minus some 64 bit fixes which are not needed) can be obtained at > ftp://ftp.qbang.org/pub/rxtx/rxtx-2.1-7pre19-i386-pc-mingw32.zip > > > Glen. > > > > -----Original Message----- > > From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On > > Behalf Of Trent Jarvi > > Sent: 22 October 2004 09:37 > > To: Java RXTX discussion > > Subject: Re: [Rxtx] Question regarding current versions > > > > > > On Fri, 22 Oct 2004, Dodger wrote: > > > > > Hi again, > > > > > > Not sure what happened the first time, but anyway, here goes again... > > > > > > I just wanted to start off with a quick question regarding version > choice, > > > and later I may (probably will) require some assistance with the actual > > > installation if possible. > > > > > > Question (1): > > > > > > I'm not sure I understand the difference/s between versions 2.0 and 2.1. > > Is > > > it only a change in API? The one API matching that of Sun, and the other > a > > > non-Sun compliant API? Essentially the question is: What version should > I > > be > > > using? And what are the pro's and con's of each? > > > > > > TIA. > > > > > > Glen. > > > > > > > > > rxtx 2.1 is a full library and does not require any files from Sun. Its > > package name is different to avoid conflicting with Sun's namespace but > > otherwise its the same. The same methods and classes are available. > > > > rxtx 2.0 is the same code but works with Sun's commapi and is under Sun's > > namespace. > > > > Its all the same code underneath. So The choice is just that. You can > > use either one. There shouldnt be any advantage of one over the other. > > When the package is released, the same code is just modified to match the > > packages. > > > > -- > > Trent Jarvi > > taj at www.linux.org.uk > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > _______________________________________________ > > Rxtx mailing list > > Rxtx at linuxgrrls.org > > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > > > -- > Trent Jarvi > taj at www.linux.org.uk > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > > _______________________________________________ > Rxtx mailing list > Rxtx at linuxgrrls.org > http://mailman.linuxgrrls.org/mailman/listinfo/rxtx > -- Trent Jarvi taj at www.linux.org.uk From lonedesign_2k at yahoo.com Sun Oct 24 08:31:35 2004 From: lonedesign_2k at yahoo.com (Dodger) Date: Sun, 24 Oct 2004 16:31:35 +0200 Subject: [Rxtx] Question regarding current versions In-Reply-To: Message-ID: Trent, I'm so sorry to bother you again, but I need some help with a windows installation, if possible. I can't seem to find reliable information regarding the placement of the native libraries and rxtx jar file. >From a website: "RXTX is installed by simply copying rxtxSerial.dll into your /bin folder and copying RXTXcomm.jar into your /lib/ext folder." Am I correct in assuming this information is for the application runtime only? I have just installed JDK 1.5.0, and as you may well know, it installs both a public and a private JRE: Public: Java/jre1.5.0 Private: Java/jdk1.5.0/jre Do the files have to go in both locations? Please give me simple directions as to where each of these three files should be placed (rxtxSerial.dll, rxtxParallel.dll and RXTXcomm.jar). Thanking you in advance, Glen. -----Original Message----- From: rxtx-bounces at linuxgrrls.org [mailto:rxtx-bounces at linuxgrrls.org]On Behalf Of Trent Jarvi Sent: 23 October 2004 23:43 To: Java RXTX discussion Subject: RE: [Rxtx] Question regarding current versions On Sat, 23 Oct 2004, Dodger wrote: > Hi Trent, > > Thanks so much for your assistance so far. > > I decided to go with the binaries on the download page, 'rxtx-2.1-7pre17', > as I'm not too clued up on CVS/build files etc., yet. Just copied the native > library and the rxtx jar file; I assume that is all that is required for > serial comms.? > > Anyway...It's working; But, I get an error when doing a simple enumeration, > the complete output follows: > > Version: RXTX-2.1-7pre17 > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyS0: File exists > /dev/ttyS1 > > I can post the