Op 11-3-2012 17:21, Zbigniew schreef: >> but as I suggested in a off-list reply to a question >> that Eric Auer send me, the fact that sound output is effected as >> well, this seems kind of confirm my suspicion on how JEMM is handling >> IN/OUT statements when in protected mode, or something along those lines... > > Then indeed there's something in a need for a little improvement?
Please let us know if/when you're able to pinpoint a culprit. You might want to start with a MSDOS/Win9x bootdisk (www.bootdisk.com) to eliminate FreeDOS components as the culprit, and to have a proven reference platform. Once that works, try 4DOS but keep MSDOS's memory manager. Independently, also try JEMMEX (and/or XMGR and/or HIMEMX with/without JEMM386). Your game seems to be the most obvious situation to demonstrate something's not quite right. So things that can vary: [1] KERNEL (MSDOS versions, or various FreeDOS kernels) [2] SHELL (MS-COMMAND, FREECOM, 4DOS) [3] HMA/XMS driver (MS-HIMEM, HIMEMX, XMGR) [4] UMB/EMS driver (MS-EMM386, JEMM386) [5] Combo XMS/UMB driver (JEMMEX) A not so nice challenge is trying Quarterdeck's QEMM, that's one big nightmare :) ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
