-
Notifications
You must be signed in to change notification settings - Fork 1
XEP ROM
Xep128 implements an EXOS ROM, which is "installed" within the memory map without any external ROM image source or any option for it to do so (in fact this is the only "fixed" ROM content inside Xep128, even EXOS is loaded externally from a file - the reason of XEP ROM is done this way is the fact that it interacts with the emulator itself, so version mismatches between Xep128 and its ROM could be fatal). Its purpose is mainly to provide an in-Enterprise solution to query/set emulation parameters. As for a normal EXOS ROM, you can see its existence with the :HELP
command as well. The ROM implements the "XEP" commands. They can be used like any other EXOS commands, that is:
- From IS-BASIC, you need to put ':' before 'XEP', so for example
:XEP EMU
to get the 'EMU' command of XEP - From EXDOS window, as with other things too, ':' is not needed at the beginning (but still, I prefer using :XEP commands rather than XEP commands, do not let to be confused because of this)
What does XEP ROM do?
- It's the "hook" point of :XEP commands to be "patched" for the emulator, and giving the feedback (output of command)
- It hooks on EXOS ROM calls currently it does:
- Sets the EXOS date/time on boot
Most important :XEP commands are:
-
:XEP HELP
(or even:HELP XEP
works in this only case): Xep128 compile-time information and list of :XEP commands available -
:XEP HELP command
only displays help on the given :XEP command -
:XEP EMU
displays run-time information on Xep128 (paths - even preference directory -, and such)
Xep128, the minimalistic Enteprise-128 emulator with main focus on exotic hardware