Known Issues

Phantom Windows

Phantom windows can be created on both client-server and standalone installations of IN-SPIRE.

Client-server Installations (data sets resident on a server, not your workstation):
If you use both a dual-monitor workstation and a single monitor workstation to run IN-SPIRE, some windows may not be visible or reachable on the single monitor system because of the way window positions are saved. Suppose you are using a dual monitor workstation and exit IN-SPIRE with windows located on the secondary monitor. As you would expect, when you relaunch the application from that workstation, the windows will reappear where they were when you exited.

If, however, the next time you launch IN-SPIRE you use a single monitor workstation (a laptop, for example), the windows positioned on the secondary monitor will not be visible. Neither can you make them visible, because they can only be made to appear in a location which is off-screen for the system you are working on.

There are three workarounds for the problem of phantom windows in client-server installations:

If you anticipate using a one-monitor system:
On the two-monitor system, move all IN-SPIRE windows to the main monitor before you exit the application.
If you're using a one-monitor system and cannot use a two-monitor system to retrieve windows that had been displayed on the secondary monitor:
Edit the pixel locations of the missing windows. Open <IN-SPIRE install directory>\DatasetRoot\config\user\<userid>\preferences.ini and edit the pixel locations of the missing windows. The default IN-SPIRE install directory is C:\Program Files\INSPIRE\. Refer to the locations of the visible windows to assign locations to the missing windows that will be visible on the single monitor.
Reset all window locations to their defaults:
Delete the preferences.ini file and restart the application. This is an easier solution than editing the pixel locations of missing windows, but all window location preferences will be lost.

Standalone installations (data sets as well as the application are saved on your personal computer):
Changing the monitor resolution can also create phantom windows. This is one way: You positioned windows toward the periphery of your display, quit IN-SPIRE, changed the monitor resolution to something less than it had been before, and relaunched the application. There's a chance that those peripheral windows will now be off-screen.

Solution:

Change the monitor resolution while IN-SPIRE is open. During the "trial" period, observe whether all the windows are visible. If not, cancel the change and readjust the windows.

Log File Size

No provision exists to automatically trim the size of the log file, and if left unattended, it can grow quite large. Users should periodically check <IN-SPIRE install directory>\DatasetRoot\log.txt to ensure that this file is not consuming too much disk space. If the file is found to be large and there is no known reason for keeping it, it may be deleted. When the application launches, a new log.txt file will be created.

IN-SPIRE Unresponsive after Long Idle Periods

In some cases, after long periods of idle time after the screen saver and/or power save has been active, IN-SPIRE may be unresponsive when the computer is brought back to an interactive state. If this occurs, you may need to use the Task Manager to terminate the javaw.exe and HappyHelper.exe processes, which will close IN-SPIRE. Then relaunch IN-SPIRE.

Data Files with Non-Latin Characters

Files containing non-latin characters must have the appropriate “byte order mark” predefined in the source text file(s), or certain characters may not be interpreted properly by IN-SPIREs statistical analysis programs, and will not display properly in the document viewer.