tschak909 Posted April 25, 2020 Share Posted April 25, 2020 Hey guys, I'm digging into the DOS 2 memory map, but I thought I'd ask here too, I have a prototype CIO handler which works well under CLI DOSes like SpartaDOS and OS/A+, but when I load in DOS 2, and use DUP, it obliterates my handler, and since i'm trying to USE my device in the DUP, it can't just be paged back in via MEM.SAV. I am going to move my handler up past DUP, but I thought I'd ask for a saner approach? I ask this, with the understanding that this is just a prototype, and that there will be a new handler written in assembler... -Thom Quote Link to comment Share on other sites More sharing options...
Rybags Posted April 25, 2020 Share Posted April 25, 2020 Just for during dev? Under the OS or under Basic. High in memory like under the screen if you're just doing text only. Or top of memory then re-open E: Page 6 should have plenty of space for the stubs of code to do stuff like PORTB changing or moving blocks of memory around. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted April 25, 2020 Author Share Posted April 25, 2020 Yeah, I've moved it to $8000 for now. Which allows me to test certain bits under DOS 2. Video coming. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted April 26, 2020 Author Share Posted April 26, 2020 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.