levrin: Thank you for this information. I was curious about this myself but so far have been too lazy to actually do the research.
Anyway, what was driving me crazy about the boot was that there seemed to be an unnecessary step when grub4dos was loading its built-in default menu for about 1 second before redirecting to the linux partition. I just didn't like to see it there every time.
So, I eventually figured out a way to get rid of it completely by patching grub.exe and effectively inserting my own menu.lst in it which by the way eliminates the need of an external menu.lst file.
Yes, the default menu is built into the binary itself but can be replaced by other plain text boot entries without any problem.
This is a script I wrote for the task (it will probably work only with grub4dos version 0.4.4 since the absolute offsets may be different in other versions):
Code:
#!/bin/bash
g=grub.exe # grub
og=grub.exe.bak # grub backup
mn=menu.lst # menu file to embed
mv $g $og
dd if=$og ibs=1 count=230018 > $g
cat $mn >> $g
dd if=$og ibs=1 skip=230567 >> $g
Now it looks nice!
gcorreai: I'm sorry, I wish I could help but the problem is that no one actually understands how Splashtop boots so far. I can't even test it in virtual environment, it just won't work, so the chances I can crack this are very slim...
However, earlier in this thread there are links to the phoronix forum where they're hacking Splashtop and some of the darkstar2000's posts about kexec booting look promising.
It wouldn't be the cleanest solution since you would be loading your distro from an already running Splashtop but it is possible according to him. It's just that there is no simple step-by-step howto so you'll have to study more on the subject if you want to understand it.
Bookmarks