3.1D Upgrade problems
"Gary S. Moss", VLD/VMB
moss at BRL.MIL
Wed May 10 01:06:48 AEST 1989
< We have recently installed the "maintenance tapes" to bring our IRIX up to
< 3.1D on 2 personal irises and a 4server8. Now 4sight seems to be broken in
< a wierd way: Most of us here have user.ps files to remap keys, put up tools,
< and fire up toolchests. Those of us who do have these things in our directories
< now find that the tools and chests fail to come up one time in 3.
I have a similar problem with IRIX 4D1-3.14711181642 (3.1A?), so I suspect
that it is not a new problem, but may have gotten worse. My /RestartActions
are defined as follows, but about every other time, the console window does
not appear, when I attempt a 'restart' from the 'Max' menu:
% specify window constraints, font and colors for console window
/RunConsole
{
(/etc/gl/startconsole -r1000 -s80,40 -m80,60 -fIris12.fm -C 0,7,4,1)
forkunix
} def
% specify customized 'wsh' procedure
/forkwsh
{
(wsh -t \$LOCHOST -r1000 -s80,60 -m80,60 -fIris12.fm -C 0,7,4,1
-n wsh)
forkunix
} def
/RestartActions [
% Caps-lock Ctrl (`/~) F1 -> Ctrl Caps-lock Esc (`/~)
[ 28420 28419 28471 28562 ] [ 28419 28420 28423 28471 ] replacekeys
{ (ical) forkunix }
{ forkwsh }
{ RunConsole }
] def
I have only included the part of my user.ps, but since this works
some of the time, and is straightforward usage, I suspect a 4Sight bug. If
someone wants to look into this, I'll gladly send them the entire source.
-moss
More information about the Comp.sys.sgi
mailing list