Page 1 of 1
DosEmu: how to specify proper path for command.com?
Posted: Thu 03 Mar 2011, 23:30
by Mysp
I have downloaded and installed DosEmu (using universal binary from dosemu.org) that is just unTAR two provided bin.tgz files. It seems that DosEmu start properly, but cannot find
command.com. I get completely confused, what is proper syntax and path to specify for it (on enclosed picture there are just two examples - I tried many others.
The config.sys is default from installation:
Code: Select all
rem config.sys for DOSEMU + FreeDOS
rem note that the initial "D:" is set to "Z:" at the end
SWITCHES=/F
DOS=UMB,HIGH
dosdata=umb
lastdrive=Z
files=40
stacks=0
buffers=10
devicehigh=d:\dosemu\ems.sys
devicehigh=d:\dosemu\cdrom.sys
install=d:\dosemu\lredir.com z: linux\fs\${DOSEMU_LIB_DIR}/drive_z ro
shellhigh=d:\command.com /e:1024 /p
Picture
DosBoxErr.png is a screen capture.
The
complete filelist of installation is in enclosed in filelist.txt file (to avoid clutter of forum).
Thank you very much in advance for your help.
Re: DosEmu: how to specify proper path for command.com?
Posted: Mon 21 Mar 2011, 19:59
by RetroTechGuy
Mysp wrote:I have downloaded and installed DosEmu (using universal binary from dosemu.org) that is just unTAR two provided bin.tgz files. It seems that DosEmu start properly, but cannot find command.com. I get completely confused, what is proper syntax and path to specify for it (on enclosed picture there are just two examples - I tried many others. [...snip]
Thank you very much in advance for your help.
I just tried the latest Debian version as discussed here, and it worked fine:
http://www.murga-linux.com/puppy/viewto ... 133#420133
That is, I downloaded and installed these 2 Debian packages (unless you already have the dependencies from second one from another install).
http://http.us.debian.org/debian/pool/c ... 2_i386.deb
http://http.us.debian.org/debian/pool/m ... 0_i386.deb
Open rxvt, and type "dosemu".
To exit dosemu: "exitemu".
Mine showed no errors or missing dependencies. Works fine.
Dosemu :<failure
Posted: Sat 28 May 2011, 06:09
by iw2evk
Hi,
i've rtetried to install dosemu on puppy 4.3.1 , but same problem (see picture).
Wher i can modify for found command.com and change config.sys autoexec.bat?
Thanks
iw2evk roberto
Milan
Re: Dosemu :<failure
Posted: Sat 28 May 2011, 15:07
by Moose On The Loose
iw2evk wrote:Hi,
i've rtetried to install dosemu on puppy 4.3.1 , but same problem (see picture).
Wher i can modify for found command.com and change config.sys autoexec.bat?
Thanks
iw2evk roberto
Milan
Go find the dosemurc or dosemu.config file
look in it for a line like this:
$_hdimage = "/root/something"
Read the comments right above this line. It tells you about where directories are that look like your disks. The version you have is assuming that there is a thing made into the Z:. The C: will be the
first thing on this list of directories. Look there for the config.sys and autoexec.bat
Re: Dosemu :<failure
Posted: Sun 29 May 2011, 01:45
by RetroTechGuy
iw2evk wrote:Hi,
i've rtetried to install dosemu on puppy 4.3.1 , but same problem (see picture).
Wher i can modify for found command.com and change config.sys autoexec.bat?
Thanks
iw2evk roberto
Milan
By what method did you install it? Which Dosemu? (there are the files which I posted above, but there is also a .pet out there, which appears to produce an incomplete install).
Posted: Sun 29 May 2011, 18:06
by Bruce B
After looking at one screen shot, I wonder if your install path is too long or deep or incorrect. And sorry I don't have DOSemu installed to check against.
~
/root/mydos/dosemu/freedos/ I think is correct
And the automatically installed directory /root/.docemu or /root/.dosemurc
~
Posted: Mon 30 May 2011, 03:51
by RetroTechGuy
Bruce B wrote:After looking at one screen shot, I wonder if your install path is too long or deep or incorrect. And sorry I don't have DOSemu installed to check against.
~
/root/mydos/dosemu/freedos/ I think is correct
And the automatically installed directory /root/.docemu or /root/.dosemurc
~
I think that I saw a similar error when I installed from an older .pet. When I installed using the 2 .debs, it worked fine. I think that the last time someone reported this problem, it was a missing config file.