If I mount the drives in the preinit before, then booting happens properly, BUT, empwake does not bind to the hijack menu.

On the serial port, there is no error from empwake either. Just the single line saying was process ID it received when starting.

And, again, WITHOUT mounting the drives, I get errno2 (Can't readconfig.ini)

I'll ask again in case you missed it (and b/c I'm curious) - how does Hijack find and read the config file?

Next of course is why on earth we'd be getting different behaviour with basically the same hardware setup. Discounting drive startup times of course - maybe you can build a version with that delay to test for this...

On second thought, I just remembered that I aldo dont' get the program to bind when running it from the shell prompt myself. Argh. Very odd. Any more debug output you care to test with? Or some other sample program for testing puposes only?

Bruno