From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: 1.3.2 builds but doesnt run Date: Tue, 24 May 2005 07:44:37 +0400 Message-ID: <4292A325.1000908@aknet.ru> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org 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" $