home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: rec.games.hack
- Path: sparky!uunet!munnari.oz.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!augean.eleceng.adelaide.edu.AU!rhelbig
- From: rhelbig@augean.eleceng.adelaide.edu.AU (Roger Helbig)
- Subject: What happened???
- Message-ID: <1992Dec18.005054.2680@augean.eleceng.adelaide.edu.AU>
- Organization: Electrical & Electronic Eng., The University of Adelaide
- Date: Fri, 18 Dec 1992 00:50:54 GMT
- Lines: 29
-
- Yesterday I was attempting my first win with a valkyrie
- (having ascended with barbarian and priest). Having
- got as far as dlevel 24, I was cavorting around with a nurse.
- After she had teleported a few times, the nurse seemed to
- just freeze in one place, not moving, not hitting me :-(
- However, #chatting worked as normal.
-
- The problem occurred when I used the backslash key to id
- the nurse. Instead of printing "nurse", it printed several
- lines of characters, including a lot of non-ascii IBM
- graphics characters (this is an old 286), beeped and *froze*!
- I had to reset the machine.
-
- I back up save files in case of power failure/riot/meteorite
- strike, but this character hadn't been saved since level 12!
- Oh well.
-
- Has this happened to anyone else? This is the *second* time
- this has happened to me! Maybe my executable has been
- corrupted... or is there a bug associated with nurses? Looks
- like some character pointer that points to the place where the
- monster names are stored is getting clobbered (or the names
- themselves are). After the first time this happened, I thought
- maybe my pc had a problem or cosmic rays were following me
- around or something. Oh, I'm using the 3.0j executables from
- linc.cis.upenn.edu. Any theories?
-
- -=-
- Roger
-