Hello!
Interesting. But will it solve the problem of starting kernel from arbitrary directory on arbitrary drive without the need to specify it on commandline? Let's say I want to launch /d/dist/osmd/kernel.prg (which is of course mint.prg), but do not want to use modules from /c/mint/(1-16-*) because I have my own in /d/dist/osmd/, which could easily become /e/osmd/, /g/betatest/osmd/, /a/ or whatever.
You simply only need a small program that determine sysdir and then load kernel with this argument. This are 10 lines in C. I don't like to add error-prone sysdir detecting code just for the very rare case that someone install FreeMiNT. My experience is that it's very confusing if the kernel search in several dirs for it's configuration or load it's modules from several dirs. This was a point of misconfiguration and problems in the past.
Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------------------- http://www.cs.uni-magdeburg.de/~fnaumann/ e-Mail: fnaumann@freemint.de