First, is there already a version of the MG Explorer for the Geneve out there? We haven't been able to find one yet. Is there any interest?
Years ago Mike Dodd wanted to modify it to work on the Geneve. He spent some time recoding and returned a disk with his initial work. I have nothing after that and I don't know Mike's whereabouts/status today.
So, if there is interest and if someone would like to take up the task I would be happy to post what I have. I haven't taken an in-depth look at the changes and I probably won't be able to engage too much on this project given time constraints. If you've good with coding, have good knowledge of the Geneve, have the time and want to take this on let me know. Here is a synopsis of the notes page that Mike sentat the time:
NOTES ON GENEVE VERSION OF MG EXPLORER
Modified for the MYARC Geneve 9640 Computer by Mike Dodd
Nature of this release of Explorer:
This version will probably work on a 99/4A, but
slllowwwllllyyyy, due to all CRU keyscans being removed.. It would be much
better to use Bytemaster's version of EXP for the /4A - this version was
meant for the Geneve..
There are two versions on the disk: EXP and EXP1.. EXP loads at
>B9C4 and is designed for operation from the Editor/Assembler
environment.. EXP1 loads at >A000 and is designed for the Extended BASIC
environment.. It can be loaded with the LEXP utility provided on the
Bytemaster release disk.. Both versions are >462C bytes long..
 EXP used CRU keyscan to check for CTRL 2-5 when in continuous
execution mode.. Changed to use normal keyscan link..
 EXP used CRU keyscan in memory editor to check for FCTN-SHIFT
cursor movement.. Removed..
 EXP used CRU keyscan to scan for SHIFT when in continuous
execution mode, for purpose of placing in Turbo mode.. Removed..
 EXP had many "Anti-Piracy" checks, to prevent changing the load
interrupt vectors, and looking at/altering EXP's memory.. These have been
 All auto-repeat code has been removed - they were too fast on
the Geneve's higher speed, and the Geneve's IBM keyboard has auto-repeat
 If the PC reaches >02B2, indicating a keyscan, the Geneve will
execute the keyscan at high speed and return to *R11.. This was changed as
the Geneve's keyscan involves memory paging, and would page EXP out of
memory, resulting in a lockup.. Unfortunately, this still does not work
perfectly, and I'm not sure how to fix it.. The problem is this: when you
STEP an instruction, either in single step mode or continous mode, EXP
scans the keyboard, using the standard link (see  above).. This keyscan
almost always grabs a new key first, before the AP program gets a chance
to read the keyboard.. Thus, when the AP program scans the keyboard, the
keyscan returns a status of >00, since, as far as it's concerned, that
key was already pressed.. Which is true.. Then, of course, the AP program
scans the status byte and sees that nothing has been pressed, and scans
again.. This can continue on forever.. I honestly don't knoww what the
solution to this is.. I am welcome to any ideas..
 EXP destroyed all memory when CTRL = was pressed to exit.. This
has been removed, so that on CTRL =, EXP executes a BLWP @>0000..
 colors changed to suit my perverted tastes (I have a monochrome
monitor).. You don't like them? Tough - wait for the final release of
this.. I'll try to have easily changable colors in it..
 Would like to modify EXP to have option to execute DSR calls at
full speed, so that programs may call the DSR and still work on the EXP..
This shouldn't be too difficult..
 Would like to modify EXP to reside in different memory pages
than AP program, so that the AP program could take up as much memory as
it wanted.. However, this may be next to impossible to do.. I'll have to do
a detailed study of EXP's usage of AP memory.. If the only users of it are
STEP and DASSEM, it might not be too difficult.. Otherwise........ could be an
incredibly neat trick.. Sure would be nice though - would make EXP the
Keep in mind that unless change 
above is accomplished, memory is very tight.. For that reason, such large
features as, for instance, disk catalogs, printer dump, help screens,
etc.. will not be considered, _unless_ I can get the above change made..
Even then, I will want to keep it to 32K maximum (it's about 17..5K now,
so there would definately be room for expansion), counting code and
buffers.. BUT, I would not bet great amounts of money on the success of
changing the EXP to reside in different memory banks, so keep it
Edited by FALCOR4, Mon May 28, 2018 4:05 PM.