Hi.

Am running dosemu 1.1.99.2, and I think I've finally got the basics of
a good startup all figured out - except...

In /etc/dosemu.conf, I have $_hdimage = "/dosc/dos", where /dosc is
my usual DOS/Windows partition mounted under linux, and /dosc/dos has
autoexec.bat, config.sys, command.com, and the various DOS commands
distributed with DOSEMU.  I have yet another directory under this,
/dosc/dos/command, for "external" commands for DOS (attrib, etc).

Then, in both /dosc and /dosc/dos, I have identical copies (for overkill)
of both autoexec.bat and config.sys.  In config.sys, I have two commands:

device=c:\ems.sys
SHELL=C:\DOS\COMMAND.COM C:\DOS /E:4096 /P

and in autoexec.bat:

SET PATH=C:\;C:\DOS;C:\DOS\COMMAND;...
lredir c: linux\fs\dosc

I know that autoexec is being run, because the redirection of c to the
/dosc directory (up one level from where it starts) is happening.  But
I absolutely can get no action out of this config.sys.  The EMS driver
isn't being loaded, and the SHELL setting isn't happening, as evidenced
by its lack of appearance when I do

SET

after bootup.  Side note:  Two things that I don't define ARE there -
the PROMPT and the COMSPEC env variables.  Where are these being
defined?

What I would like to achieve, in the end, is to have the boot sequence
be using this directory one level below the DOS root, and as well have
all the DOSEMU stuff in this same area one level below.  This way I can
keep this stuff out of the area that Windows considers to be the main
drive root area.  But by the same token, I want to start off my DOS session
in the root area, since that's where everything else starts from.

Any ideas?  And how could I examine stuff to see what's not happening - are
there any useful debug options for this?

thx,
jbh
-
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

Reply via email to