Problem with dosemu

Here is another update - compiled again 1.4:

System was clean, no traces of dosemu. configure and make, make install was OK.

NOTE:
(1) .dosemu directory is empty on my home or root
(2) No dosemu directory is created, therefore there is no log file

Running dosemu command after make install either from root or from home user nothing happens except cpu usage shows "user" usage, and Ctr-C stops it, I'm back at command prompt. No initial conversation about setting up home directory or accepting freedos license terms.

[apu@Andraslinux dosemu-1.4.0]$ su -c "make install > dosemu_install.txt" Password:
[apu@Andraslinux dosemu-1.4.0]$ su -c dosemu
Password:
[apu@Andraslinux dosemu-1.4.0]$ dosemu

[apu@Andraslinux dosemu-1.4.0]$

This all is from within X environment, running from xterm. I created the dosemu_install.txt log file just to preserve what was happening during make install.

It seems to me that dosemu program does not even get to trying to open a window, a dos terminal. It is stuck before opening the dos terminal or "booting into" dos. When I tested your rpm installation of 1.2 it did open up a dos terminal, the black window, but then it got stuck and I could not kill it with Ctr-C.

It looks like freedos is installed on /user/local/share/dosemu/drive_z.

Is there a path issue here?

Janos

Hello.
Use the latest CVS version, is better and more stable than the
latest release.
If it doesn't work in the same way, then look in .dosemu/boot.log
or maybe try an strace dosemu.
Good luck!!!

El 15/04/14 18:52, Janos G. Komaromi escribió:

Ivan Baldo - [email protected] - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: [email protected] - http://go.to/ibaldo

--
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

Hi Ivan,

Thanks for the suggestion. Here is what I did (on a clean system, no traces of previous attempts of dosemu rpm or comiled installations):

[apu@Andraslinux dosemu]$ git clone git://git.code.sf.net/p/dosemu/code dosemu
<I then copied the cloned directory into my compiled work directory>
[apu@Andraslinux dosemu]$ ./configure
[apu@Andraslinux dosemu]$ make
<both commands were OK, although I saw some "fatal" words during
compiling>
<Then I copied freedos binaries tgz file into this compile work
directory>
[apu@Andraslinux dosemu]$ su -c "make install"
<During installation of man I got this: "fatal: unrecognized
argument: --format=%cd" - probably not significant, but probably related to "fatal" word during make> [root@Andraslinux dosemu]# dosemu
Segmentation fault
[apu@Andraslinux dosemu]$
<Same thing happened if I ran dosemu from root.>

I do have a ./dosemu directory installed in my home structure, and it does have a boot.log file. Same thing is true for /root directory.

Output of diff for the two boot.log files, first is from root:
< CONF: running exclusively as ROOT: uid=0 (cached 0) gid=0 (cached 0)
---

49c49
< PKT: Cannot open raw sockets: No such device
---

It looks like everything is going well till the last minute. Here is the tail end of the user boot.log file:
...
device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C:
device: /etc/dosemu/drives/d type 4 h: -1 s: -1 t: -1 drive D:
CONF: cdrom MSCD0001 on /dev/cdrom
CONF: config variable c_system unset
Linux kernel 2.6.20; CPU speed is 1795357000 Hz
CPU-EMU speed is 1795 MHz
CONF: mostly running as USER: uid=500 (cached 500) gid=100 (cached 100)
DBG_FD already set
DOSEMU-1.4.0.8-180-g35054ba is coming up on Linux version 2.6.20_apu032214 #1 Mon Mar 24 12:36:54 EDT 2014 i686 Compiled with GCC version 4.2.1 -m32
CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K))
CONF: reserving 48Kb at 0xF4000 for 'r' (Dosemu reserved area)
CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory)
PKT: Cannot open raw sockets: Permission denied

Apparently the segmentation fault is the result of no raw sockets that root discovered and user has no permission to it.

Will this help in finding out what my problem is?

Thank you for your attention,

Janos