Laboratoire ICAR » Plateforme TXM

Diagnostic A¶

On some Windows, depending on the network account type used, TXM may run the post-installation-java sequence at start-up for each Windows session and then compels the user to set TXM user home, etc. preferences.

Hypothesis A-1¶

For some network accounts, possibly different kind of network account profiles, when TXM starts it can see four different configurations that produce the observed behavior:

• the post-install-bat has been executed because (and the preferences has been reseted):
  • the APPDATA\.txm directory was not found (eg C:\Users\<login>\AppData\Roaming\.txm or \\server\share\users\<login>\.txm)
    • an administrator or the user deleted the .txm directory
    • an automated administrator task cleaned the APPDATA directory
  • the APPDATA\.txm STAMP file is older than the TXM installation STAMP file
• TXM start sequence tests:
  • the TXMHOME preference is not set
  • the System.getProperty("user.home")+/TXM directory is not found or not readable or not writable (C:\Users\<login utilisateur>)

Hypothesis A-2¶

If the user modifies the TXMHOME preference, it is not restored during the post-installation-java because the post-installation-java always reset it using the 'System.getProperty("user.home")+/TXM' path.

Solution¶

The post-installation-java must restore the TXMHOME preference of the previous "org.txm.rcpapplication.prefs" installation preference file.

Diagnostic B¶

It has been observed that post-install-bat, the C:\Users\<login utilisateur>\AppData\Roaming\.txm\.metadata\.plugins\org.eclipse.core.runtime\.settings directory is emptied during TXM startup.

Hypothesis B¶

When TXM starts it can see one configuration that produce the observed behavior:

• the STAMP file found in C:\Users\<login utilisateur>\AppData\Roaming\.txm is older then the STAMP file found in the TXM installation directory

h3. Solution 1

On Windows, use a standard Windows environment variable or Windows API in TXM.bat giving a correct/stable path accessible to the user (the user home directory) to use or create by TXM jar:

• for network accounts, the path should look like \\servdfs.ens-lyon.fr\whomes\%USERNAME% for some account types and \\something\else\%USERNAME% for other account types
• for local Windows, the path should look like C:\Users\%USERNAME%

h3. Solution 2

• for an "all users" installation type of TXM on Windows on machines used by network accounts, the administrator patches the TXM.bat script after installation to point to the correct user home directory variable.

Annex¶

On Windows, use an instruction in TXM.bat giving a correct/stable path accessible to the user (the user home

See #1931 or #2092.