public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "Janos G. Komaromi" <jankom@aaahawk.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Problem with dosemu
Date: Tue, 15 Apr 2014 17:52:32 -0400	[thread overview]
Message-ID: <534DAA20.1000803@aaahawk.com> (raw)

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


             reply	other threads:[~2014-04-15 21:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 21:52 Janos G. Komaromi [this message]
2014-04-16  0:47 ` Problem with dosemu Ivan Baldo
2014-04-16 14:52   ` jankomEarthlink
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 19:52 jankomEarthlink
2014-04-15  3:02 jankomEarthlink
2014-03-26  2:32 jankomEarthlink
2014-03-30 18:49 ` Frantisek Hanzlik
2014-03-30 23:22   ` jankomEarthlink
2014-03-31  7:31     ` Frantisek Hanzlik
2014-04-14 15:26       ` jankomEarthlink
2014-04-14 22:22         ` Frantisek Hanzlik
2014-04-15  2:24           ` jankomEarthlink
2014-04-21 20:19             ` Frantisek Hanzlik
2014-04-22  2:31               ` jankomEarthlink
2014-04-22  3:08                 ` Jegunn
2014-04-23  3:25                   ` jankomEarthlink
2014-04-23 11:38                     ` Jegunn
2014-04-22 22:10                 ` Frantisek Hanzlik
     [not found]                   ` <5357347D.1010401@earthlink.net>
2014-04-23  7:06                     ` Frantisek Hanzlik
2014-04-23 19:08                       ` jankomEarthlink
2014-05-04 11:20                         ` Frantisek Hanzlik
2014-05-05  1:57                           ` jankomEarthlink
2014-05-05  8:46                             ` Frantisek Hanzlik
2014-03-25 22:51 jankomEarthlink
2014-03-25 23:35 ` Ivan Baldo
2014-03-25 23:38 ` Frank Cox
2003-08-29 14:06 Problem with DOSEMU scroowhar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=534DAA20.1000803@aaahawk.com \
    --to=jankom@aaahawk.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox