[1449] in Release_7.7_team
BioSym problems
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Wed Aug 12 12:07:01 1998
To: wdc@MIT.EDU, mbarker@MIT.EDU, ghudson@MIT.EDU, rbasch@MIT.EDU,
facdev@MIT.EDU, nschmidt@MIT.EDU
Cc: release-team@MIT.EDU, mvsilis@MIT.EDU, alexp@MIT.EDU
Date: Wed, 12 Aug 1998 12:06:56 EDT
From: Alex T Prengel <alexp@MIT.EDU>
I think I have fixed the BioSym problems (with help from their tech support).
The trick was to set an environment variable that makes it think it's
running on IRIX 5.3:
setenv BIOSYM_PLAT_OR irix5r3
Could folks try running BioSym 970 and 400 on various machines including O2
/XZ/non-XZ to see if they work everywhere now?
I'm not quite sure what that means internally and clearly somebody screwed
up somewhere. Bill's thought that there might be something wrong with
graphics support on IRIX 6.2 for non-XZ graphics boards is consistent with
observations, and if so it is likely that this could bite us again- we
may not be so fortunate to have such an easy fix in other cases. Can
someone check this out with SGI (and yell at them if appropriate.. Bill?).
One further data point is that the problem showed up on BioSym 970, which
uses GL graphics- it did not when launching BioSym 400 directly, which I
believe does not, so the use of OpenGL may be an additional factor.
One more piece of information- before applying the fix, if you just logged
on and started release 400 directly by doing
add biosym_root
source /mit/biosym_root/cshrc400
insightII
it worked, but if you first tried to run BioSym 970, got the error and
then tried to start 400 by doing
set_biosym_context 400
insightII
it crashed (with the same error and additional X errors). set_biosym_context
is a vendor script that is supposed to let you switch from one release to
another if you launch one and then want to run a different one.
Alex
