philb@shark.UUCP (Phil Biehl) (04/06/84)
I have not been able to get the recall function of rogue to work for me. It appears to work for others on the system that use the same game. I have had gurus come by and see if they can help but to no avail. I suspect it might be in my environment but am at a loss to know what it might be. I run in C shell, 4.2BSD. Any suggestions on how to remedy this problem??? Phil Biehl Tektronix, Inc.
gwyn@brl-vgr.ARPA (Doug Gwyn ) (04/08/84)
In Rogue 5.3, at least, you cannot restore a game whose saved image has been "touched" (e.g. modified or a copy of the original). This is an attempt to forestall fraud. Perhaps this is the problem. Otherwise, run "rogue $HOME/.rsav" to restore the game (use the pathname of your save file).
gary@mit-eddie.UUCP (Gary Samad) (04/09/84)
I have had the same frustrating problem! After typing 'rogue rogue.save' I get a message 'Game has been touched' and either will be allowed to play on without the possibility of my score making the 'board' or I will make one move and the game will be resaved, ad infinitum! I have certainly NEVER touched a file since learning of rogue's smarts a couple of years ago! Even a single game may be played, saved, and restored several times before this happens; it is then irreversible. Helllllp!!!
notes@iuvax.UUCP (04/09/84)
#R:shark:-68000:iuvax:9800018:000:426 iuvax!apratt Apr 8 20:14:00 1984 The problem of not getting the recall method (do you mean "rogue -r"?) to work could stem from the fact that the game was saved under a name other than the name in your ROGUEOPTS variable. Also note that, in 5.2, a touched game will still be played, but you will not go into the high-score list. It says, "This game has been touched, so your score will not be recorded." -- Allan Pratt ...ihnp4!inuxc!iuvax!apratt
bmdp@dciem.UUCP (Dave Sweeney) (04/11/84)
In 3.6, the current date is written at the beginning of the save file. If the clock ticks while the game is being saved, the file creation date will be later than that shown in the save file, hence rogue believes that the game has been 'touched'. Chances of this happening are greater when the system is busy. Prevention: don't play rogue on a busy system. Cure: ask your system administrator to reset the system time-of-day to at least 1 minute previous to the file creation date, execute 'touch rogue.save', and reset the system time-of-day to the correct value.