Hi, sorry to disturb the peace of EMM386 happiness, but I found two problems, one with EMM386 and one with HIMEM...
First problem: EMM386 EMM=1416 causes a crash while letting the AuGoS computer Go game play against itself. EMM=1408 works, and EMM=1416 reports exactly 1536k of EMS (according to MEM). Bigger EMM=... values cause crashes, too: either a hang, an illegal instruction and MCB corruption (MCB at dfdf:0 overwritten, last MCB on my system), or a reboot (in particular for EMM=... values of e.g. 4 MB and higher). Something with EMM=value versus some 1.5 MB alloc chunk structure in EMM386 seems to be going wrong here. Plus EMM=... has an offset, there are always roughly 100k (maybe UMB-size?) more than the EMM=? value of actual "total EMS". On the other hand, maybe this is meant to be like that (as the UMBs are defined as "EMS allocated for the system handle", so EMM=... could be interpreted as correct method to tell "... kB of EMS should be FREE initially"). Whatever. EMM386 EMM=??? which causes more than 1.5 MB of TOTAL EMS to be prepared causes a crash while playing AuGoS DOS against itself. Second problem: HIMEM /LOG option does not work. When I try to activate it, the XMS handle table gets all messed up but no log file is created. Strange. Tested with newest (2.03) EMM386 and newest HIMEM. Eric PS: No problem happens in "pool sharing mode", only EMM=... going wrong. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel