What I want:
1. A step-by-step tutorial with screen shots on
a) obtaining the compiler
b) obtaining the source
c) configuring MC or TC source and any make files/processes
d) executing a compile and having a new bzImage or kernel etc. that can be tested by plugging it into the files I have on the drive
Then an example of adding / embedding / changing this with another file - i.e. similar to the method Svolli used to create the version that can be installed on a W2K NTFS system.
2. Once done this way - "hard coded" if you will, completing the same steps without embedding a change in the kernel, and walking through a tutorial - with screen shots - of linking a module or TCZ at run time so that a specific module or library loads at that time.
Example: Let's assume a call to the a wifi tool or other port would take place at boot and rather than relying on a backup, the device/PC it was on only had one task: connecting to the internet and becoming an access point with virtually no user interface. There is a routine.
Example: A device that in fact had no screen or keyboard IO. A similar "Kernel" was used to drive a PC that controlled a car stereo with buttons on the steering wheel. That kernel is likely to have far different drivers than another.
In short, modifying the MC kernel for specific tasks whether an NTFS mount, an access point or a stereo console, would either require the kernel to be changed or a different set of files to be linked to it.