It is easy to de install rex to see. Just go into rex manager and hit f7 I think. That removes the rex manager software.
On Wednesday, December 3, 2025, Mike Hyde <[email protected]> wrote: > Went digging through the archives for the mailing list, and found this: > > Some notes: > * PLEASE keep your RAM backed up in REX just in case of bugs. I'm not > aware of any but there could be one or two or several lurking in there. > * works with version-3 z-code files only (this covers *most* Infocom games) > * you will probably need at least 24K RAM installed in your machine > * save files can only be written to/read from the RAM file system > * it doesn't support non-ASCII characters yet > * if a game fails to start, or if saving a game fails, you probably don't > have enough free RAM > * As-built it works with REX v4.8, and the packaging program z100pkg.exe is > a Windows executable. See build.txt for instructions to build it on > Windows; modify if your needs are different. > > Could the changes in REX from 4.8 to 4.9 be the cause? > > > On Dec 3, 2025, at 10:30 AM, Joshua O'Keefe <[email protected]> > wrote: > > > >> On Dec 3, 2025, at 7:07 AM, Mike Hyde <[email protected]> wrote: > >> > >> I downloaded Zork, used z100pkg on it, and it created the bx files. I > then loaded it on a 102 with rex# 4.9, but when I try running it it crashes > with error #1f58. > > > > Hi, Mike. I see the same error in virtualt-1.8+ . At a cursory glance > it looks like that's an error in "setupimage:" which is described in the > assembly comments as: > > > > ;init code to be called when game > > ; starting, to set up reading from > > ; game image - need to call this > > ; before using zgeta, zputa > > ;DESTROYS ALL REGS > > > > setupimage: > > ;the block currently selected is > > ; first (contains interpreter) > > > > Now, my 8080 is so rusty as to effectively not exist any more but it > looks like if we're at 0x1f58 to throw the error it's because cblkp failed. > Why, I couldn't say in the couple of minutes I had to look. Also I know > nothing about the REX API and it's definitely digging around in the REX > filesystem here. > >
