public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: jankomEarthlink <janosk@earthlink.net>
To: Frantisek Hanzlik <franta@hanzlici.cz>, linux-msdos@vger.kernel.org
Subject: Re: Problem with dosemu
Date: Mon, 14 Apr 2014 22:24:14 -0400	[thread overview]
Message-ID: <534C984E.7070808@earthlink.net> (raw)
In-Reply-To: <534C5FA3.2000407@hanzlici.cz>

Hi Franta,

Thanks for the quick reply.

See below my answers and comments:

On 04/14/2014 06:22 PM, Frantisek Hanzlik wrote:
> Hi Janos, dosemu has log in user home directory, '~/.dosemu/boot.log' 
> - is there anything? 
Thanks, this section may show something
...
CONF: reserving 64Kb at 0xE0000 for 'E' (EMS page frame)
ERROR: cpu exception in dosemu code outside of VM86()!
trapno: 0x0e  errorcode: 0x00000004  cr2: 0x0419eab7
eip: 0x001135a0  esp: 0xbfdb8db4  eflags: 0x00210282
cs: 0x0073  ds: 0x007b  es: 0x007b  ss: 0x007b
ERROR: Fault handler re-entered! signal=11 _trapno=0xE
leavedos(1|0x1) called - shutting down
leavedos() called from within a signal context!
ERROR: leavedos called recursively, forgetting the graceful exit!

I seem to remember that a few years back, the time when FC-3 was the new 
thing, I installed dosemu and it never worked. But I could be wrong.

>  You are trying run dosemu under console, right? I not sure when is 
> possible run dosemu in background, as You indicate above. At least 
> first dosemu start should be run in foreground, because dosemu shell 
> script (wrapper around 'dosemu.bin', emulator binary) will ask You 
> about several things (freedos installation etc.). You have completed 
> this dialog? Can You try run xdosemu under X Window? It should run 
> fine too.
Actually, I did the install while in X environment, from xterm. Indeed, 
it ran through the initial install steps (creating directory, agreeing 
to license terms, etc. This happened both if I started dosemu from root 
or from my home directory. By the way, xdosemu is just a symlink to 
dosemu in my installation. I also tried it from console (Ctr_Alt_f1), 
but same thing happened, and I could even not get out of it, I had to 
open another tty to reboot. As far as foreground or background are 
concerned I initially ran it in foreground and did the dosemu & only to 
show you what was on my screen.

> You write that you did clean install - did You remove stuff in user 
> home directory as well ('~/.dosemu/*' and eventually '~/dosemu/*', 
> including ~/.dosemu and ~/dosemu directories itself)?
Yes, absolutely clean, even the man files were deleted. I first ran rpm 
-e ...., but it left some lingering files, empty directories. So I did a 
find (using kfind) to make sure nothing was left behind.

> You mean to tell that no one dosemu version (1.2.2 nor 1.4.0.1) works, 
> and both have same behavior, as You described above?
Actually, the behavior is a little different. rpm 1.2 install does lead 
me through the install steps, and opens up the black screen, but I had 
to kill the process. Compiled 1.4 does not go through the script, it 
presents me with a blank xterm screen, and I can simply get back to 
command prompt with  Ctr-c.

> What is your terminal screen resolution? You are using Linux Kernel 
> Mode Setting (KMS) to set display mode? What is 'stty -a' output?
[apu@Andraslinux ~]$ stty -a
speed 38400 baud; rows 30; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon 
-ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 
vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

> Did You install dosemu package with command 'rpm -U dosemu-x.y-z.rpm' 
> or 'rpm -i dosemu-x.y-z.rpm'? Produce this command some error output? 
> And did You install it as root? 
I used rpm -ivh command, but after your answer I cleaned it up again 
(rpm -e) and did the rpm -U. Installation was always quick and flawless. 
Yes, I did it from my home directory, xterm, but after issuing su 
command. So the installation was with root privileges.

I'll do now another clean up, the compile 1.2 source, see if it makes a 
difference, i.e. 1.2 from source instead of 1.4 from source.

We'll get to the bottom of this, I'm sure.

Janos


  reply	other threads:[~2014-04-15  2:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  2:32 Problem with dosemu 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 19:52 jankomEarthlink
2014-04-15 21:52 Janos G. Komaromi
2014-04-16  0:47 ` Ivan Baldo
2014-04-16 14:52   ` jankomEarthlink
2014-04-15  3:02 jankomEarthlink
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=534C984E.7070808@earthlink.net \
    --to=janosk@earthlink.net \
    --cc=franta@hanzlici.cz \
    --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