kalash@ucbcad.UUCP (07/09/84)
> Hence the grossly large saved games. This method also results in another > rogue sickness: one must continue saved games on the same terminal type as > they were started on. I hate to ruin your day, but you do NOT need to continue games from the same terminal. Rogue explicitly resets itself for the new terminal, before continuing. Joe Kalash kalash@berkeley ucbvax!kalash
davidk@dartvax.UUCP (David C. Kovar) (07/22/84)
As hacking binaries with adb is not my idea of fun, I decided to
try a different tactic: call my own routines from a routine in
the mach_dep.c file. For those who have not seen the rogue
distribution, it comes in two parts: one large binary file and one
small C file that has machine dependent stuff in it. I happily
wrote code to dump and modify statistics and set off to use it.
It turns out that unless I install the hacked rogue as the systems
offical rogue, something I can't do, my version is useless. Why?
Apparently rogue includes it's *own* size in the saved file. Rogue
binaries of different lengths can't read each other's files. At least
that is what it looks like at this point. Pity.
--
David C. Kovar
USNET: {linus|decvax|cornell|astrovax}!dartvax!davidk
ARPA: davidk%dartmouth@csnet-relay
CSNET: davidk@dartmouth
"The difficult we did yesterday, the impossible we are doing now."brian@uwvax.ARPA (07/24/84)
Actually, rogue (5.3) doesn't really put its size in the save file. When
you save a game, rogue just writes its entire data segment on the save file.
Hence the grossly large saved games. This method also results in another
rogue sickness: one must continue saved games on the same terminal type as
they were started on.
--
Brian Pinkerton @ wisconsin
...!{allegra,heurikon,ihnp4,seismo,sfwin,ucbvax,uwm-evax}!uwvax!brian
brian@wisc-rsch.arpakevin@amdcad.UUCP (Kevin OwWing) (07/25/84)
> Actually, rogue (5.3) doesn't really put its size in the save file. When > you save a game, rogue just writes its entire data segment on the save file. > Hence the grossly large saved games. This method also results in another > rogue sickness: one must continue saved games on the same terminal type as > they were started on. Gee, is this really true? It seems that I've been able to play games starting on a vt125, then continue on an adds regent 25, and then still more on a homemade computer that currently emulates a Beehive microbee (its easy to emulate, for what I use it for, ok). Does this mean I really didn't play the same game? :-) Kevin Ow-Wing @ AMDCAD (408) 749-2354 UUCPnet: {ihnp4,amd,gatech,resonex}!amdcad!kevin US MAIL: 901 Thompson Pl. Sunnyvale, CA 94086 Mail Stop 144
davidk@dartvax.UUCP (David C. Kovar) (07/26/84)
Ok, someone claims that rogue does not write the binary file size
in with the saved file and then check it when it restores. I will
go along with that. But how the hell (sorry Mom) does it tell the
difference between a save file created with a different binary. We
have two versions of rogue running here, one normal and one that
promises one party/treasure/monster room per level. The only difference
between the two is that one has 4 or so instructions NOP'd. They
are still exactly the same size. But a saved game created by one
version will not run under the other version. Anyone know why??
--
David C. Kovar
USNET: {linus|decvax|cornell|astrovax}!dartvax!davidk
ARPA: davidk%dartmouth@csnet-relay
CSNET: davidk@dartmouth
"The difficult we did yesterday, the impossible we are doing now."