From mboxrd@z Thu Jan 1 00:00:00 1970 From: Enrique Baraibar Subject: Re: dosemu and paradox 4.5 Date: Mon, 6 Feb 2006 23:05:50 -0300 Message-ID: <20060206230550.01a3c168.enribar@hotpop.com> References: <43E5A9D3.2090104@aknet.ru> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <43E5A9D3.2090104@aknet.ru> Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="iso-8859-1" To: linux-msdos@vger.kernel.org Cc: Stas Sergeev On Sun, 05 Feb 2006 10:31:31 +0300 Stas Sergeev wrote: > Hello. >=20 > Enrique Baraibar wrote: > > Paradox memory problems and not > > DOSemu's. Try paradox -extk 8000. > In this case you may want to increase one of the > $_xms, $_ems or $_dpmi values in your dosemu.conf, > if the default ones are not enough for paradox. > "-extk" suggests that it should be $_xms. > If you find the value that suits, we may consider changing > the defaults, so that paradox can work without any extra options > with the future dosemu releases. Actually, the current defaults > look very small indeed. >=20 Stas, I don't know why, but Paradox "sees" more than 16MB extended memo= ry when running over DOSemu. And that is why it crashes with a GP 0000 err= or. Using -extk 8000 (or anything equal or lesser than 16000) forces it to = use only the amount specified. IIRC this happens no matter which settings you choose in dosemu.conf, s= o you must always use -extk xxxx. =46or what is worth, though, Paradox shines with 8MB extended memory. More is better, of course, but not that much better. And 16MB is the absolute max. > > Paradox 4.02 has run fine for me on DOSemu 1.2.1. since it appeare= d. > 1.2.1 is too old and is usually problematic to run on the modern > systems like FC3. Well, I am eagerly waiting for 1.4.0 :o). (I am not at all fluent with linux and keep myself confined to binary versions :o( ) --=20 Enrique Bar=E1ibar - 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