Re: "EMS driver version mismatch: got 3, expected 5, disabling"
Stas Sergeev <[email protected]>
| Newsgroups | org.kernel.vger.linux-msdos |
|---|---|
| Message-ID | <[email protected]> |
30.08.2016 20:59, Mouse пишет:
> Okay, I was hoping to see a bit of list traffic before sending, but,
> for whatever reason, I'm not seeing anything. I hope it's not some
> kind of filtering spazz - though I did get the list welcome mail, so
> that seems unlikely.
>
> Teal deer: I'm getting the message in the Subject:, but can't figure
> out where to get an appropriate ems.sys.
>
> In more detail....
>
> I'm trying to use dosemu on Linux (kernel 3.13.0-48-generic, on
> x86_64). The binary distribution had some X issues - but I know a bit
> about X, so I cloned the git tree and started to fix them. I think I
> have succeeded in fixing the immediate problem there, but now I'm
> having other trouble.
>
> The binary distribution claims to be 1.4.0.1 (in that when I run
> dosemu.bin --version, the first line printed is "dosemu-1.4.0.1"); as a
> disambiguator, dosemu.bin's MD5 hash is
> 60bf29180c9270018f6ba8f246e57a41. But when I base my stuff on commit
> 77c5e739bf5f128802ef55763909568008eac6f0 ("Tagging 1.4.0.1", the only
> child of commit 74b00d8d5b46d20ce384ab64544ea41a389afe70, "DOSEMU
> 1.4.0.1"), all I ever get is segfaults on startup after a complaint
> about how LOWMEM mmap is failing. The binary distribution's dosemu.bin
> does print
>
> EXPERIMENTAL: using non-zero memory base address 0x110000.
>
> and strace leads me to think this is relevant (in that it's printed
> immediately after the same mmaps fail, but then two more mmaps are done
> with addr=0x110000). However, I can't find that anywhere in the
> 1.4.0.1 tree.
>
> So I moved my work over to the apparent development tip, basing it at
> commit 18f6f5cdf1beceae8c7532718bfaf423e4a44f6a instead. It still
> crashed, but now I could find hints in the source that turning on
> EXPERIMENTAL would help. It did; I then got something that would start
> (and, yes, the X issue was fixed) and complain about missing DOS. So I
> fetched dosemu-freedos-1.0-bin, through the chain of redirections (the
> first one coming from either http://www.dosemu.org/stable/ or
> http://www.dosemu.org/bleeding/):
>
> http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
> http://downloads.sourceforge.net/project/dosemu/dosemu-freedos/1.0/dosemu-freedos-1.0-bin.tgz?download=
> http://superb-sea2.dl.sourceforge.net/project/dosemu/dosemu-freedos/1.0/dosemu-freedos-1.0-bin.tgz
>
> which last finally gave me the gzipped tarball. I did a make install
> with this in place as dosemu-freedos-bin.tgz and then it was willing to
> start, but told me
>
> | DOSEMU 1.4.0.8-762-g400b188 (2016-08-30), configured: 2016-08-30 12:32:33 -0400
> | Please test against a recent version before reporting bugs and problems.
> | Submit Bugs & Patches to [email protected] or via http://dosemu.org.
> | FreeDOS kernel build 2036 cvs [version Aug 18 2006 compiled Aug 18 2006]
> | Kernel compatibility 7.10 - WATCOMC - 80386 CPU required - FAT32 support
> |
> | (C) Copyright 1995-2006 Pasquale J. Villani and The FreeDOS Project.
> | All Rights Reserved. This is free software and comes with ABSOLUTELY NO
> | WARRANTY; you can redistribute it and/or modify it under the terms of the
> | GNU General Public License as published by the Free Software Foundation;
> | either version 2, or (at your option) any later version.
> | C: HD1, Pri[ 1], CHS= 0-1-1, start= 0 MB, size= 2000 MB
> | D: HD2, Pri[ 1], CHS= 0-1-1, start= 0 MB, size= 2000 MB
> |
> | EMS driver version mismatch, disabling.
> | Please update your ems.sys from the latest dosemu package.
> |
> | Press any key!
>
> and I've been unable to find an ems.sys that works any better,
> including the one generated from ems.S during the build.
Remove your ~/.dosemu/* (ems.sys is there)