Problem With COM ports in Toolkit 1.1.4

[Charlie Crackle]

When I edit the network and Select type Serial I have no comm ports in the Address Box.

Old V2 work fine and can see comms ports.

If I reinstall Old Release version of tool kit works fine.


If I connect via CNI in version 1.1.4 Works fine.


Running XP SP2

Charles

[Duncan]

When I edit the network and Select type Serial I have no comm ports in the Address Box.

Old V2 work fine and can see comms ports.

If I reinstall Old Release version of tool kit works fine.


If I connect via CNI in version 1.1.4 Works fine.


Running XP SP2

Charles

No COM ports is generally indicative of javax.comm.properties missing from the appropriate Java JRE runtime LIB Dir.

If you type "java -version" at a Command Prompt you can see which JRE is the default one, navigate to the LIB dir of that JRE and there should be a file called javax.comm.properties

Can provide more detailed info if required.

[Charlie Crackle]

If you type "java -version" at a Command Prompt you can see which JRE is the default one, navigate to the LIB dir of that JRE and there should be a file called javax.comm.properties

Yes you were right the javax.comm.properties file was missing all together from the running Java. I copied the file from the old one and all works.

any ideas why this file was not installed or disappeared ?

Charles

[Duncan]

Yes you were right the javax.comm.properties file was missing all together from the running Java. I copied the file from the old one and all works.

any ideas why this file was not installed or disappeared ?

Charles

Had you recently updated your Java Runtime?

[Charlie Crackle]

Yes I remember now the little "Auto Runtime Updater" said there was a new version. I did update.

Does the Java runtime your installer installs different from the one you would down load from SUN ?? (ie it copies this special file)

This is what java -version produced

java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)

What is the version that the toolkit installer would have installed ?

Charles

[Duncan]

Yes I remember now the little "Auto Runtime Updater" said there was a new version. I did update.

Does the Java runtime your installer installs different from the one you would down load from SUN ?? (ie it copies this special file)

This is what java -version produced

java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)

What is the version that the toolkit installer would have installed ?

Charles


Hi Charles,

Toolkit would have installed 1.4.2_05.

I can see that javax.comm.properties is going continue to cause a few issues as people, rightfully, keep their JRE up to date. I think we need to improve Toolkit's detection of this file missing and offer to install it if required..

I've been digging around the Sun site and have a few ideas that I will discuss with the Team when we all get back to work.

Thanks for the further info Charles.

[JackD]

The Toolkit software uses a component which uses the Java Runtime Environment (RTE) to interface with the actual computer. For some inexplicable reason the Java RTE doesn't include support for serial ports and you have to copy this javax.comm.properties file to the lib directory each time you upgrade. If you trawl through google searches on this you find that this is a worldwide problem which apparently affects all Java applications. Thankfully the fix is to simply copy a file but it's still surprising. As Duncan says, we are currently considering different approaches to this problem.

[greig]

I encountered the same problem with an inability to access COM ports this morning and headed straight to the forum...

Thankfully same problem, same fix, so I'm back on-line already. This forum is great - thanks to all for their contributions and support!!


Greig.

[Duncan]

I encountered the same problem with an inability to access COM ports this morning and headed straight to the forum...

Thankfully same problem, same fix, so I'm back on-line already. This forum is great - thanks to all for their contributions and support!!


Greig.

We've identified a way to solve this problem 'properly' in future releases so updates of the JRE shouldn't affect Toolkit (provided the JRE itself doesnt break something).

Thanks for the Forum feedback as well!

[gazza]

I stumbled upon the comms issue yesterday and the forum has become the first port of call. I really appreciate knowing if a problem is universal instead of feeling like the village idiot ! And of course, I appreciate the instant solutions. :)

Gazza

[nella]

I should have known to check the forums first. I have been dicking around trying to fix this error for a week. I appeared when I installed a wireless network at the office so I was blaming that. Anyway well done guys. Your fix worked perfectly. Weird how the javax.comm.properties file is not in the update.