Hi Bernd, > Jack's driver only accepts certain values. This might be intentional due > to specific caching algorythms. > Using XMSSIZE I'd still have to use a lot of errorlevel stuff: > if not errorlevel 5 , then use /B /N1 /N3 > if not errorlevel 10, then use /S5 > if not errorlevel .. etc. > if errorlevel 80, then use /S%errorlevel% (limited to 255 as that's > errorlevel maximum).
You can use a factor or simply add a zero, to get 10 to 2550 MB cache. As you say, smaller caches (5, 15, 25, 40, 50 MB) would still need an extra check, but you need not cover ALL steps. A few "not enough RAM for 80 MB cache" choices will be enough, e.g. 15 MB and 40 MB. > All above is based on 'how much XMS is currently available' but also > ignores the 'how much should I leave available for programs I'd like to > run' (8MB system using 5MB cache means trouble for games and Windows). Again, I think a few steps for low memory systems would be enough and for big system percentages are exact enough imho. Also there are tools like my 503 byte "add" for further calculations, or use calc387 on newer computers, both in factorial-calc387-add.zip :-) Eric PS: calc387 is free open source software by Craig Hessel, 1024 bytes. ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
