From: Hufnus <tonyb@thekrnl.sysdev.org>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.3.2 builds but doesnt run
Date: Mon, 23 May 2005 15:02:09 -0800 [thread overview]
Message-ID: <20050523150209.090ba127.tonyb@sysdev.org> (raw)
In-Reply-To: <429203DA.6070207@aknet.ru>
On Mon, 23 May 2005 20:24:58 +0400
Stas Sergeev <stsp@aknet.ru> wrote:
> Hufnus wrote:
> > it builds fine but when I run dosemu, it just exits with no
> > error log...
> The log is usually in ~/.dosemu/boot.log.
> Please double-check that it is not there.
Made a clean new make for the 4th time:
Had made (2) 2.95.3 builds (with and without strip) on one host
and made (1) 3.3.4 build on another host, they all FAILED to start
on configurations that had been running with 1.3.1.
Well made one more try w/2.95.3 and guess what, it now runs !!! ???
I think the problem was with /etc/dosemu.conf, in the past it had a
line:
$_vnet = (off)
which was tolerated in previous versions < 1.3.2, with a msg:
ERROR: Unknown vnet mode "0"
But dosemu.bin would run!
Enable that line and dosemu.bin (1.3.2) does not run and no output to
boot.log either.
One NOTE: I run Ziff Communications config.ctl to allow me
to edit config.sys at start-up and my hdimage is an msdos 5.0 image:
if I use the /usr/bin/dosemu from 1.2.0 then the <F1> <F2> and
<arrows> work fine, for config.sys editing.
if I use the new /usr/bin/dosemu from 1.3.2 they do not work at all.
"sdras vouitye"
Sorry no Cyrlilic
Tony
--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities
|___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
next prev parent reply other threads:[~2005-05-23 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 16:24 1.3.2 builds but doesnt run Stas Sergeev
2005-05-23 23:02 ` Hufnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 3:44 Stas Sergeev
2005-05-23 5:36 Hufnus
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=20050523150209.090ba127.tonyb@sysdev.org \
--to=tonyb@thekrnl.sysdev.org \
--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