) I fixed a bug that looked like this.
failed_to_start.png [ 5.53 KiB | Viewed 255 times ]
The logic in kernel.asm is as follows:
- If rd_load_from_hd = 1, skip initialization of /rd;
- If rd_load_from_hd = 1, load it and initialize /rd.
For historical reasons access to rd_load_from_hd variable was sometimes done as rd_load_from_hd+0x10000, which pointed to some kernel code.
If you are lucky enough, [rd_load_from_hd+0x10000] is actually 1 but there is no ramdisk image on hdd.
Therefore ramdisk is not initialized and launcher app cannot be started.