Arch Linux

darut

Member

Registered: 2004-04-17

Posts: 69

dosemu and dosbox start problem

Does anybody have problem starting dosemu or dosbox?
My dosemu was working well but after archlinux update it cannot start.
Message is about not found command.com file.

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: dosemu and dosbox start problem

I get

LOWRAM mmap: Invalid argument
Segmentation fault

from dosemu, but dosbox is working fine.

I've got dosemu installed and command.com is present:

[karol@black ~]$ locate command.com
/usr/share/dosemu/drive_z/command.com
/usr/share/dosemu/drive_z/bin/command.com

Last edited by karol (2012-01-15 12:18:53)

darut

Member

Registered: 2004-04-17

Posts: 69

Re: dosemu and dosbox start problem

I get this:

C: HD1, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
D: HD2, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
UMB's unavailable!
dosemu XMS 3.0 driver installed.
dosemu EMS 4.0 driver installed.
CONFIG.SYS error in line 10
>>>devicehigh=d:\dosemu\cdrom.sys
             ^
Kernel: allocated 41 Diskbuffers = 21812 Bytes in HMA
CONFIG.SYS error in line 1

Bad or missing Command Interpreter: z:\command.com /e:1024 /p
Enter the full shell command line:

Last edited by darut (2012-01-15 12:38:21)

sarbash

Member

From: Russia, Naberezhnye Chelny

Registered: 2011-03-15

Posts: 32

Re: dosemu and dosbox start problem

The same problem here:

GNU General Public License as published by the Free Software Foundation;
either version 2, or (at your option) any later version.
C: HD1, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
D: HD2, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
UMB's unavailable!
dosemu XMS 3.0 driver installed.
dosemu EMS 4.0 driver installed.
CONFIG.SYS error in line 10
>>>devicehigh=d:\dosemu\cdrom.sys
             ^
Kernel: allocated 41 Diskbuffers = 21812 Bytes in HMA
CONFIG.SYS error in line 14
>>>
 
 
                                                  ^
Bad or missing Command Interpreter: z:\command.com /e:1024 /p
 Enter the full shell command line: ^@^@^@^@                                   

Has anyone the solution?

ole

Member

Registered: 2012-08-08

Posts: 1

Re: dosemu and dosbox start problem

Got the same surprise after moving to arch x86_64. Let us compare output of

dosemu -D +d

on my current system and my fallback system by means of

diff <debug_output_arch> <debug_output_fallback>

Here is the key fragment:

< MFS: dos_fs: build_ufs_path result is '/home/ole/.dosemu/drives/d/doseu/lredrr.ccom'
---
> MFS: dos_fs: build_ufs_path result is '/home/ole/.dosemu/drives/d/dosemu/lredir.com'

Looks like the arch package has been compiled with a buggy library (glibc?).

Solution #1: build from source (skipped cause of ...)
Solution #2: get the binary from another distro and substitute it for the buggy one.

That`s what I did (step-by-step):

Step 1. Add a line to /etc/dosemu/dosemu.users:

default_lib_dir= /usr/share/dosemu

Step 2. Get a stable 64-bit package of dosemu: Tip 1 Tip 2

Step 3. Unpack .deb (or whatever you`ve got in its own way):

ar -xv <package_file_name>.deb data.tar.gz   
tar -xzvf data.tar.gz

REM: find `ar` in `binutils` package if not present on the system
       
Step 4. Replace /usr/bin/dosemu.bin. Dosemu launches now but DPMI apps make it crush.

Step 5. Replace six libs /usr/lib/dosemu/libplugin_*.so

That`s it. At this point my dosemu came back to life and since then working flawlessly (with Foxpro 2.6 in particular).

Good luck.

sarbash

Member

From: Russia, Naberezhnye Chelny

Registered: 2011-03-15

Posts: 32

Re: dosemu and dosbox start problem

Thank you for the reply. I've bugreported this problem.
But it isn't important for me now because dosbox community has helped me with my app to run it.
Nevertheless, this is a bug.

Rallemikken

Member

Registered: 2013-03-28

Posts: 1

Re: dosemu and dosbox start problem

Can confirm bug on fresh install as of march 2013. Quick (and dirty) fix, worked for me (on 32-bit):

- Download the http://ftp.us.debian.org/debian/pool/co … 2_i386.deb from squeeze
- Open in archieve program, unpack the data.tar.gz
- Open data.tar.gz in archieve program as root, and unpack in / (top-level)

Personally, I have an old /etc/dosemu folder, which I have reused over the years, so I only unpacked the content of /usr. Aletrnativly, you can unpack all, and replace debian's /etc/dosemu with your own afterwards. Maybe the problem can be solved by only replacing the /usr/bin/dosemu script and /usr/bin/dosemu.bin binary?

New to arch, and new on forum. Hope this is within whats permitted    Dosemu is vital to me.

clauslack

Member

Registered: 2013-05-02

Posts: 1

Re: dosemu and dosbox start problem

for mmap segmentation fault

Try

echo 0 > /proc/sys/vm/mmap_min_addr

Check http://kernel.xc.net/html/linux-2.6.31/ … P_MIN_ADDR

Regards