1.7.3 release notes

From Jmri

(Difference between revisions)
(MacOS X with Locobuffer USB: Added Info.plist note)
m (MacOS X with Locobuffer USB)
Line 15: Line 15:
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet.  If it doesn't ask to restart, that's OK too.
# Run the FTDI installer. When it asks you to restart, don't click yet.  If it doesn't ask to restart, that's OK too.
-
# In the Terminal window that opened in (2), type the following two commands.  Each one is followed by hitting the return key.  You might get prompted for your password; if so, type the password for the account you're currently using.
+
# In the Terminal window that opened in (3), type the following two commands.  Each one is followed by hitting the return key.  You might get prompted for your password; if so, type the password for the account you're currently using.
       sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
       sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/

Revision as of 06:24, 22 February 2006

Please note that test version 1.7.3 is not yet generally available. This page will be updated with additional links when it is. In the meantime, the rest of this page is being developed in advance of the general release.

The original release note contains a list of changes in the release. This page contains more recent information.

Recent experience suggests that you need to be aware of a few gotcha's if you're installing for the first time. Specifically:

Windows XP with Locobuffer USB

An important note about this configuration.

MacOS X with Locobuffer USB

For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

  1. Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
  2. Download the Info.plist file from hereto this account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present) Note - When you select this file download link use a 'control-click' and ensure that the file is named 'Info.plist' - Some browsers will append a '.txt' extension if you're not careful, and that will break things. Also note Info.plist (first 'I' is uppercase....)
  3. Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
  4. Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
  5. In the Terminal window that opened in (3), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
     sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
     sudo touch /System/Library/Extensions

Note the 'space' between 'Info.plist' and '/System' in the first command line. [The other 'spaces' are hopefully easily read]

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

Digitrax Command Station Editor

This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values very quickly, so it's probably working even if you think it isn't! (Don't ask) - When you write anything back to a Zephyr command station you should see (something like) --CS-- flash very briefly in the command station display.

Personal tools