Here is a beta of Minidash v0.1 for PC0 platform, so you can play with canonic assembler samples a bit...
http://minilgos.perso.sfr.fr/pc0/pc0_beta.zipThe return value of your boot code affects the global behaviour of Minidash:
0 : Download boot code again and execute it immediately
(This value makes minidash execute your boot code in a loop. The advantage of this is that you don't even need to reboot the PC0 machine to try a new version of code. Just update boot file and see result. Reboot only if bad crash occurs. Note that all cpu and fpu exceptions should be trapped nicely, so crashes will be avoided and explanation messages will appear. However, current version doesn't manage well to resume execution after a cpu or fpu trapped exception, so you will have to reboot. If a debug mode is active in the text area where problem occurs, you will get the line number)
1 : Minidash will quit
(On consoles, that will make you return to system/dashboard menu. Not implemented yet)
2 : Power off machine
(Not implemented yet)
Error value (0xee??????) : Displays explanations messages, then displays "Press enter when you are finished editing boot file", then waits for 'enter' key.
(Happens when an exception is trapped, a user or engine error is triggered or a syntax error is detected)
Native code address (any value >2 and different from 0xee??????) : Move code and jump to it
(Not implemented yet. If your boot file is just a native code boot loader, after allocating a memory buffer and filling it with your native code program, you will compel Minidash to jump to it. On pc0, since we are still in real mode, code will be copied to 0070:0000 and CPU will jump to that address. That means your code must be address independant. Developpers willing to port XBMC may start trying to have reactos nt kernel clone boot on PC0 that way and init a ram file system...)
This post has been edited by openxdkman: Mar 28 2009, 10:44 PM
openxdkman Minidash Mar 25 2007, 08:26 PM
Minidash
Mar 25 2007, 08:26 PM
