I think those are binary instructions. Not actual addresses. You could try disassembling here [0] but a quick cut & paste gave an instruction sequence that is non-obvious to me. If Contra is a debugger/mod, then that makes a little more sense. The full message might also help clear things up. Also, noting what memory managers, drivers, and other software versions are running also helps.
[0] https://defuse.ca/online-x86-assembler.htm#disassembly2 On Thu, Mar 4, 2021 at 12:37 PM Michał Dec <[email protected]> wrote: > Hello, > > I've run some software on Pentium 3 Tualatin S on FreeDOS and it's > getting an invalid opcode error. The error precisely says "Invalid > opcode at ..." where ... is a bunch of 16 bit variables. Saying "at" is > really misleading and doesn't make any sense, since such a high address > like let's say 628a 0000 3002 206f 2b43 202b 202d 6f43 7970 6972 6867 > 2074 3931 is well within the realm of ZFS storage, not protected mode > address space :D > > If anyone's wondering, the offending software is Contra and Quake 1.08 > (software renderer). For what it's worth, the above hex string is > exactly what Quake blurted out. > > Where do I even begin with understanding this message? Is this a series > of opcodes the CPU failed to run, or is this an address, or is it > something else? I could recompile Quake, but Contra will probably > require me to patch the binary with the help of reverse engineering tools. > > Best regards, > > Michał > > > > _______________________________________________ > Freedos-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-user >
_______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
