From: Arkady V.B. <ar...@be...> - 2005-04-29 08:23:08
|
Hi! 28-=E1=D0=D2-2005 19:13 _Fr...@de... (Michael Devore)= wrote to fre...@li...: MD> With the /X2MAX32 option of HIMEM, full XMS memory is still available= for MD> both XMS 2.0 and 3.0 functions, and is fully reported on XMS 3.0 func= tions, MD> eliminating the previous need to literally reduce all available memor= y to MD> <32M via HIMEM's MAX option get Aladdin to run. MD> complain if /? is present. Use of /? will henceforth be known as the MD> Arkady gambit. :) MD> Since the EMS and VCPI allocators are now decoupled, I reduced maximu= m MD> available EMS to "industry-standard" 32M. Mostly this was done becau= se MD> silly EMS-using programs became confused if more than 32M was MD> available. Pumping it back up to 512M would be a small change, but MD> probably unnecessary for anyone. Isn't it possible to _increase_ available EMS memory through options (or, as with x2max32, make available all memory notwithstanding reported value)? MD> There is a fix to INT 15h, function 87 in EMM386, but I have forgotte= n the MD> details. Eric Auer can supply them in exhaustive detail, should one = wish. This fix was allows to work FD-EMM386 over MS-HIMEM. |