The DVI-DOS loads from 0xE000 -> 0xF700. It also taps into the command processor for BASIC to add in the extra DVI commands. If REXMGR or anything else writes over those locations with its own jumps etc then the DVI commands will not be found (FC error). It would appear that is what is happening. As mentioned yesterday there might be some tools that can save and restore the DVI commands allowing some co-existence?
On 20/2/19, 9:28 AM, "M100 on behalf of Greg Swallow" <[email protected] on behalf of [email protected]> wrote: >Yep, DVI-DOS gets dumped. > >1) Cold Start to clear MT >2) Turn on DVI >3) Insert boot disk at prompt >4) Hit reset on MT >5) Verify DVI-DOS loaded with LFILES >6) In BASIC and CALL 63012 >7) REXMGR in Menu, go to BASIC and DVI-DOS not working; LFILES gives a FC >error. > > >God Bless, > >GregS <>< > >----- Original Message ----- >From: "Josh Malone" <[email protected]> >To: [email protected] >Sent: Wednesday, February 20, 2019 9:55:01 AM >Subject: Re: [M100] Rex vs DVI > >I don't think you're missing anything. I just don't think DVI-DOS and >REXMGR can coexist. It didn't occur to me when Stephen posted his method >that REXMGR was also a problem, not just TS-DOS. Once you load DVI-DOS, is >it possible to re-load REXMGR or does that Smurf up the loaded DVI-DOS? >
