rackow@anl-mcs (Gene Rackow) (09/21/85)
there is definitly a problem and it appears terminal type dependent. the vtrek works on an adm3a with Unix4.2bsd on an 11/780 but has alot of ones on the screen with an zenith or heathkit 19 terminal
oleg@birtch.UUCP (Oleg Kiselev x258) (09/26/85)
> there is definitly a problem and it appears terminal type dependent. > the vtrek works on an adm3a with Unix4.2bsd on an 11/780 but has alot of > ones on the screen with an zenith or heathkit 19 terminal I have found that vt52 terminals on our Pyramid 90x ( 4.2 & V5, in 4.2 BSD univerce) work just fine. vt100 on the other hand did not. I traced the problem to TERMCAP : vt100 entry contains the length of character sequence in front of "cm", "cl" and some other sequences. That I fixed by setting environment var TERMCAP to be the modifyed vt100 entry from /etc/termcap ( without sequence length : "cm=\E[..." instead of "cm=5\E[...") The other problemis the sizes of the cm[] and cl[] buffers. I just set them (arbitrarily) to 16 bytes each ( i.e. cm[16]). That is more than enough for vt100 and should fit even hp terminals. Another bunch of complaints has to do with the bad design : 1) You often start the game in a quadrant with klingons with no shields. The result is your immediate death 2) The game allows the klingons to shoot twice per round at the same target. 3) You can't shoot torpedoes or move in any other than 8 given directions 4) Game is verbally obusive. All this can be ( and should be) fixed IFF it was a good game... I won at the highest level of difficulty one hour after getting the game to run. And there really isn't anything good about this version. I like warp a lot more.
peter@baylor.UUCP (Peter da Silva) (10/03/85)
> > there is definitly a problem and it appears terminal type dependent. > > the vtrek works on an adm3a with Unix4.2bsd on an 11/780 but has alot of > > ones on the screen with an zenith or heathkit 19 terminal > > I have found that vt52 terminals on our Pyramid 90x ( 4.2 & V5, in > 4.2 BSD univerce) work just fine. vt100 on the other hand did not. > I traced the problem to TERMCAP : vt100 entry contains the length of > character sequence in front of "cm", "cl" and some other sequences. That's not quite what they are, and it's probably not a good idea to zap them. They are the delay times (in seconds/10) for the terminal... the VT100 can easily confused on a fast line if you leave these out. The solution is to use tputs() instead of printf() (or whatever) to display these strings. -- Peter (Made in Australia) da Silva UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter MCI: PDASILVA; CIS: 70216,1076