Re: Problem with dosemu

Frantisek Hanzlik
2014-03-31T07:31:00Z

jankomEarthlink wrote:
> Hi Frantisek,
>
> Thanks for your help.
>
> (1) I'm almost there. Your rpm 1.2.2-1 did install, and it did go through
> initial steps, got to a black screen, but no prompt and the CPU is system
> loaded 100%. I had to kill xterm to stop it. But this may be due to
> lingering dosemu installations from my compiled 1.4 version, so I'll do
> some cleanup later.
>
> (2) Do I understand correctly that you say compiled 1.4 on i386 (or for
> that matter i586, i.e. any 32 bit PC processors) does not work? It did not
> work for me, as indicated in the original posting: compile OK, but dosemu
> command starts nothing. At least I could stop it with Ctr-C.
>
> One step at the time...
>
> Janos

1) I tried 1.2.2 under both, X and console, and it seems working well,
without any significant CPU load (perhaps only case when I saw 100% CPU
load with dosemu was screensaver from some DOS program. In other cases
CPU load was always less thas ~ 10-20% per core).

2) I was able compile and build dosemu-1.4.0.1 (well, as there was wery
little official dosemu releases, I maybe made our own numbering ;) and
this version work for me at Fedora 3, both in X and console.
There is difference betveen dosemu 1.2.x and 1.4.x: 1.2 had disk C: etc.
in ~/dosemu/, while 1.4 has all in ~/.dosemu/ (and disk C: is in
~/.dosemu/drive_c/ subdir). 1.4 further maps (via lredir) DOS binaries
and dosemu commands to drive Z: (which is /usr/share/dosemu/drive_z/ ).
Due to this difference, it is perhaps best start with deleted/renamed
~/.dosemu/ and ~/dosemu/ dirs, or with new user account.
If you want to use my 1.4.0.1 version, You maybe have to install svgalib
package - it can be downloaded from my web too.

This dosemu-1.4.0.1 is from Fedora 11 era, thus it is cca 4 years old.
And although there was not any official releases since this, dosemu
was significantly evolved by Bart, Stas and others - but as I wrote,
I was not able compile this actual development version (market as
1.4.0.8+, IMO) at Fedora 3 (although at Fedora 19 it compile fine
- perhaps it is because too different gcc versions - 3.4/FC3
vs. 4.8/FC19).

> On 03/30/2014 02:49 PM, Frantisek Hanzlik wrote:
>> jankomEarthlink wrote:
>>> Thank you both for your interest in helping me.
>>>
>>> This is an old Fedora-3 installation that I have mangled up and use it as
>>> a sandbox to learn the inner workings of linux. I have managed to compile
>>> the programs I need and while doing so I learned a lot. Now the specifics:
>>>
>>> 2.6.20 kernel on i686, AMD machine with nvidia graphics.
>>>
>>> When I did ./configure it went OK, no warnings or errors. Compiled also
>>> without problem. It is a challange for me to figure out, with some help,
>>> why it is not booting up into the virtual dos window.
>>>
>>> By the way, "dos" is also and old thing, but I still have some favorite
>>> applications (not games) that I would like to use from within my linux.
>>>
>>> I do have a modern installation as well, xubuntu 12.04, kept current.
>>> There I use dosbox installed the easy way, directly from distro.
>>>
>>> This is my story...
>> Hello Janos, I tried (after years :) run again my FC3/i386 distro and
>> found there dosemu-1.2.2 RPM package, which I build at that time.
>> You can download if at:
>> http://www.hanzlici.cz/packages/fedora/dosemu/fc3/dosemu-1.2.2-1.i386.rpm
>>
>> Unfortunately I have no dosemu-1.2.2 source RPM.
>>
>> I further tried to build under FC3 some newer dosemu version, and
>> successfuly compile dosemu-1.3.2 (from ~ Fedora 5 times) and
>> dosemu-1.4.0.1 (from ~ Fedora 11 times). Compiling newer versions
>> fails on dosemu commands (in i86 assembler) build, and as I'm bad
>> programmer, no know how solve this.
>> Both these versions You can download from my web at
>> http://www.hanzlici.cz/packages/fedora/dosemu/fc3/
>> (along with their source RPMs)
>>
>> HTH, Franta Hanzl√≠k

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html