RmscopII

Raphaël Leplae © 2000,2001,2002
Release 2.2

News

About

Back

Overview

Supported platforms

Tcl/Tk compatibility

RasMol recognition

Zombie process(es)

Tcl/Tk crash when quitting RmscopII

Overview

RmscopII is written in Tcl/Tk and should run on most UNIX and MSWin platforms, however, we haven't tested them under all possible Tcl/Tk versions and on all possible platforms. I am aware that there are possible problems depending on these factors and other external ones. This page will be used to collect these problems and propose possible solutions. Please, let us know if you encountered problems in running RmscopII by sending an e-mail with as much as possible information like:

Error message: if an error message is produced by RmscopII (or the interpreter running the script), this information will be of course indispensable.
Operating system name and version.
Tcl/Tk version.
Libraries: possibly (be sure to be allowed to do this!) include in the e-mail the content of the directory /usr/local/lib by typing /bin/ls -l /usr/local/lib/ which can greatly help us in solving problems.
The RmscopII Tcl script, shell script (UNIX) or batch file (MSWin).
And of course any other information that might be relevant or specific to the problem like the file (result of the url) used with RmscopII, on which web site (SCOP, CATH, 3Dee, ...), etc...

Supported platforms

Here is a summary of the platforms where RmscopII is known to be running on. Please let me know if other platforms can be added to the list:

Platform	Model	Operating system
SGI	O2	IRIX 6.3, 6.5
SGI	Indigo2	IRIX 6.3, 6.5
Compaq/Digital	Alpha	OSF1 4.0, 5.0
Sun	UltraSPARC	Solaris 8
PC	PII/PIII	All Linux flavors
PC	PII/PIII	MS Windows 98, NT, 2000 and XP
Mac	PPC/G3/G4	MacOS 8.6, 9.x and X

Tcl/Tk compatibility

RmscopII needs Tcl/Tk version 8.3 or higher.
Two notes about Tcl/Tk:
1) Tcl/Tk is quite easy to install, provided basic experience with computers. On MSWindows and Mac, an installer will take care of the job. On UNIX platforms, the compilation and installation is straightforward under most operating systems.
2) Most Tcl/Tk scripts written under an earlier Tcl/Tk version are most likely compatible with newer versions.

RmscopII hasn't been tested under all possible Tcl/Tk versions above 8.3. If you have problems, see the top of this page for bug report. Often the problems are related to the Tcl/Tk installation itself or its configuration.
The installer coming with RmscopII ensures that the Tcl/Tk configuration is ok and the rmscop2 shell script on UNIX or batch file on MSWin should use the proper executables. In case you perform an upgrade of Tcl/Tk, it is highly recommended to re-install RmscopII too.

RasMol recognition

One major feature of RmscopII is the ability to manage multiple RasMol windows on screen. This means that every time RmscopII is executed, it will show a list of buttons corresponding to each RasMol window on your screen. There is a known issue with RasMol on Alpha OSF1 where the RasMol windows might not be properly "registered" on the X server and RmscopII will detect only one RasMol. If you have such a problem, the solution is simple: recompile RasMol.

Zombie process(es)

On UNIX only with RmscopII version 2.0.
In case a problem occurs when processing an input file, RmscopII might leave one or several process(es) running as zombie on the machine. The consequence is that the next call to RmscopII either from a shell or through a web page will not produce any result. To check this, exit RmscopII and in a shell type:

ps -u <your login name>

where <your login name> corresponds to your user name. If one or more RmscopII jobs are running, kill them:

kill -9 <process id>

where <process id> is the process identifier corresponding to the RmscopII zombie processes.

Tcl/Tk crash when quitting RmscopII

On MSWin and Mac with Tcl/Tk version 8.3 only. With Tcl/Tk 8.4 and therefore with higher versions, the problem seems gone.
When exiting RmscopII, an error message is given about Tcl/Tk crashing. Just close the window and the problem shouldn't interfere with the OS.

Back