From: Stas Sergeev <stsp@list.ru>
To: Tom <tommy.forty@gmail.com>, linux-msdos@vger.kernel.org
Subject: Re: dosemu and ubuntu 14
Date: Tue, 10 Jun 2014 16:43:50 +0400 [thread overview]
Message-ID: <5396FD86.9020705@list.ru> (raw)
In-Reply-To: <CAD+xYi5rh4UgfD2S_4dQq38UVVu8bLNGMRX5qZtX0wigSjzEzg@mail.gmail.com>
10.06.2014 16:24, Tom пишет:
> Excuse for my english
>
> With the first installation of Ubuntu 14.04, dosemu work fine (foxpro under
> dosemu work fine!)
> Linux 3.13.0-27-generic #50-Ubuntu
>
> But now, 10 june 2014, after I've update the system
> Linux 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> foxpro under dosemu don't work with this error:
> "
> Phar Lap err 35: The 386 chip is currently executing
> in virtual 8086 mode under the control of another program. You must turn
> off this other program in order to use 386|DOS-Extender to run in
> protected mode
> "
>
> What's the problem?
3.14 linux kernel has dropped the DPMI support for x86_64.
Yours is 3.13.0-29 - my guess is that it had backported
that behaviour from 3.14.
Your previous 3.13.0-27 was likely i686 (32bit), where the
DPMI support is still possible. Or it didn't have the aforementioned
backport.
So, to run foxpro, you either need old kernel or 32bit system.
Kernel developers seem to no longer consider dosemu users
as their target audience.
3.15 kernel will probably have a work-around to that problem
because wine was also affected (wine users are regarded much
better, it seems :)
--
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
next prev parent reply other threads:[~2014-06-10 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 12:24 dosemu and ubuntu 14 Tom
2014-06-10 12:43 ` Stas Sergeev [this message]
2014-06-10 13:56 ` Andrew Bird
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=5396FD86.9020705@list.ru \
--to=stsp@list.ru \
--cc=linux-msdos@vger.kernel.org \
--cc=tommy.forty@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.