On 6/18/07, Jan Willem Stumpel <[EMAIL PROTECTED]> wrote:
1) create a $HOME/.dosemurc file with a line in it $_hdimage = "$HOME/olddos" 2) go to $HOME/.dosemu/drives and do ln -nsf $HOME/olddos c 3) go to $HOME/.dosemu and do mv drive_c drive_c.orig ln -nsf $HOME/olddos drive_c (BTW which of these 3 methods would be the best?)
It doesn't really matter in the end. 2) is what "dosemu -install" does, since it avoids needing to edit the user's .dosemurc.
But what I do not understand is how the original C: drive (just after a fresh install), namely $HOME/.dosemu/drive_c, could work. It does not contain the .sys files that a DOS boot disk should have. Just AUTOEXEC and CONFIG. So how can it boot?
It's magic :) If dosemu can't find a kernel in C:\ it'll fall back on the kernel.sys that is installed in $DOSEMU_LIB_DIR/drive_z, loads it into DOS memory and executes it. Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
