Steve,
Yes it looks difficult when just looking at a raw disassembly and for the past
week I've been thinking it was going to be really difficult. But I'm pleased to
hear that NewDos can be changed just with an org change.
Ken,
I'm looking to use the main program code that is currently between 3535h and
535f on the TS-DOS 4 ROM. I don't think it would be possible to use the cold
start recovery routine at the end of the ROM the way I plan to put the two
together.
I'll look at the 36 bytes of overlap. It may be easier to move that code.
Kurt
On Wednesday, April 8, 2015 10:22 AM, Ken Pettit <[email protected]>
wrote:
Since they overlap by only 36 bytes, one option is to simply figure out what
is in that overlapping region and relocate just that code, then patch any
references to addresses in that range.
Ken
On Wed, Apr 8, 2015 at 10:10 AM, 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
