Re: New NMI handler / .commands
david_ps wrote:Luzie wrote:
great to hear from you!
I'm looking forward to any news regarding your navigator.
btw. Maybe you can have a look here at my question: http://board.esxdos.org/viewtopic.php?id=1033 "TRDBOOT.BIN - How does it work?"
Luzie, the only thing I know about TRDBOOT.BIN is that if the "Autoload from vdisk" system call fails, TR-DOS Navigator (TRDBOOT.BIN) is automatically loaded. It is done internally by esxDOS, I dont't have more info.
So I can renamed any Autobooting-.TRD-Image to TRDBOOT.BIN and this will be loaded? Or is this TRDBOOT.BIN specially prepared for use/starting under your NMI handler?
TRDBOOT.BIN is TR-DOS Navigator executable, binary code, it isn't a TRD Image.
When the appropriate system call is called, BETADISK.SYS loads TRDOS54T.KO (esxDOS TR-DOS Emulator) using configuration stored in CONFIG/TRDOS.CFG. Emulator automatically loads TRDBOOT.BIN if Boot is present (there is an option to change it to load always). In esxDOS v0.8.9, TRDBOOT.BIN is loaded at address $6000 with SP pointing to $FF32, then controll is passed to address $6000. TR-DOS Navigator start running.