puder@burdvax.UUCP (06/15/83)
On line 25 of warp.c is a #define TCSIZE 256 which we changed to #define TCSIZE 512 /* was 256 * kop 6/14/83 */ because we have a couple of long termcap entries here. The symptom that you need to do this fix is that warp is that nothing happens after you say 'n' to "Do you want instructions? " Karl Puder burdvax!puder Paoli, Pa. (215)648-7555
chris@umcp-cs.UUCP (06/16/83)
Oh ho! Change TCSIZE to 1024. That's what all the library routines
use. I've even exceeded 1024, but then VI didn't work, so I had to
eliminate some stuff. 1024 should always be safe.
- Chris
--
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet: chris@umcp-cs
ARPA: chris.umcp-cs@UDel-Relaynewman@utcsrgv.UUCP (Ken Newman) (06/17/83)
While we're on the subject of warp bugs, here's a doozy. I won't explain the consequences just in case, but you want to change "cat" in the shell file wsc to "/bin/cat". I agree with the good points raised in recent articles. The reason warp can't be killed after you ^Z it is that at that point, the process is owned by daemon and you can't kill it. People here have been trying this because of the stupid way warp hangs onto you when you want to get out. Break doesn't seem to work right on many terminals, plus the fact that it won't let you save the game in mid-wave.
wessels@utecfa.UUCP (Ron Wessels) (06/17/83)
Ken Newman is correct with his statement that "cat" should be changed to "/bin/cat" in wsc & wscore. In addition, change "echo" to "/bin/echo". Without giving details, I can say that this was the reason that utcsrgv's scores over 200K magically disappeared.