Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!ncar!ico!nbires!maa
From: maa@nbires.nbi.com (Mark Armbrust)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Minor bug in nethack 2.3e
Message-ID: <403@nbires.nbi.com>
Date: 31 May 89 13:32:05 GMT
References: <401@nbires.nbi.com> <2415@infocenter.UUCP>
Reply-To: maa@nbires.UUCP (Mark Armbrust)
Organization: NBI Inc, Boulder CO
Lines: 37

In article <2415@infocenter.UUCP> mhoffman@infocenter.UUCP (Mike Hoffman) writes:
>in article <401@nbires.nbi.com>, maa@nbires.nbi.com (Mark Armbrust) says:
>> 
>> at offset 5487Eh (346,238 dec) in NETHACK.EXE, change 74h to EBh. 
>              ^
>
>Mark goes on to say:
>> -e 70f8:497e     [note:  70f8 is DS + 5000]
>> 70F8:497E  74.eb
>        ^
>
>Well, is it 5487E, or 5497E?

The OFFSET in the file is 5487Eh.  This is the number that you need if you are
using a binary file editor like BPE to do the patch.

When you load a file into memory using the DEBUG command, the file is loaded
starting at DS:100h; therefore, you need to add 100h to the file offset to get
the memory address to patch.

Since the offset is greater than FEFFh, you also need too compute the segment
address as noted above.

if you compare the posted/patched files using "FC /B", the miscompare will be
at the correct file offset.

Hope this clear things up.


Mark Armbrust
maa@nbires.nbi.com
maa@nbires.UUCP
-- 

Mark Armbrust
maa@nbires.nbi.com
maa@nbires.UUCP