1.3.2 builds but doesnt run

1.3.2 builds but doesnt run

[Hufnus]

Compiled dosemu many times in past.

compiletime-settings are identical to the 1.3.1 ones;
compiler same 2.95.3;
libc same 2.3.2

it builds fine but when I run dosemu, it just exits with no
error log...  The config files are the same as for 1.3.1,
the new global.conf was copied to var/lib/dosemu.

If I switch the dosemu.bin from 1.3.1 back into /usr/bin, all
works fine again.

TonyB


--
  __      __  _     I N C.               http://www.sysdev.org
/ __|\\// __||  \  __   __          /         tonyb@sysdev.org
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers

Re: 1.3.2 builds but doesnt run

[Stas Sergeev]

Hello.

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.
If it is really missing, try running
dosemu -D9+a -o /tmp/log
and maybe then it will create the /tmp/log.

Re: 1.3.2 builds but doesnt run

[Hufnus]

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

Re: 1.3.2 builds but doesnt run

[Stas Sergeev]

Hello.

Hufnus wrote:
> $_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
Ah, sure. Newer dosemu may refuse
to run with the wrong configuration,
whilst the older ones could just
ignore an error. In most cases
you don't need to touch the config
at all - the defaults are mostly
sane.
$_vnet accepts the string, so (off)
is definitely wrong.

> and no output to boot.log either.
Not for me. You have to investigate
further what have you done wrong
to make this to happen. Played with
the build options?
There are rather many things you
did wrong, for example you are
expected to run dosemu/xdosemu
and not dosemu.bin. And you are
not expected to do anything at
all with the global.conf (other
than probably to just delete it
since it is of no use).
What more have you done?
But in all cases, dosemu should
at least print a reasonable diagnostic,
otherwise it is a bug.
If I set $_vnet=(off), I get this:

$ dosemu.bin -X
ERROR: Unknown vnet mode "0"
$