Correct, for any OptROM that hasn't been disassembled into an re-assemblable file. But NewDOS has, so it is very easy to relocate it wherever you want. So it just depends on which code you are trying to relocate.
Ken On Wed, Apr 8, 2015 at 10:18 AM, Stephen Adolph <[email protected]> wrote: > pretty hard to relocate option rom code. you need to have an accurate > disassembly, and then process it to adjust addresses on jumps and calls, > etc. > > ..Steve > > > On Wed, Apr 8, 2015 at 1:10 PM, Kurt McCullum <[email protected]> > wrote: > >> Thanks for the update Ken, >> >> One question about the ROM versions of NewDos. I noticed on the versions >> you have in your memfiles area that the code has been relocated to a lower >> portion of the ROM. How difficult is it to relocate optrom code to a new >> location? The original versions started at 3535h. >> >> I ask because I have been working on merging TWord/Sardine with TS-DOS as >> one ROM image (Excluding the internal dictionary). I've found the location >> of the F7 call from the TWord main menu (1C28) and was planning to call >> TS-DOS from there but 3535h is about 36 bytes too low to work. >> >> Kurt >> >> >> >> On Wednesday, April 8, 2015 9:54 AM, Ken Pettit <[email protected]> >> wrote: >> >> >> Almost. >> >> Bob Pigford did some work on getting the NEWDOS assembly code ported over >> with T200 System ROM addresses and got it about 90-95% there I would >> guess. But additional work is still needed to get it to a working state. >> >> Ken >> >> On Wed, Apr 8, 2015 at 9:39 AM, Kurt McCullum <[email protected]> >> wrote: >> >> Does NewDOS exist for the 200? >> >> Kurt >> >> >> >> >> >
