2012/3/13, Ralf A. Quint <free...@gmx.net>: > So far, this rather looks like a problem with 4DOS, not with JEMM as > I initially suspected... :?
Yes, you were right: I'm terribly sorry, but my former reports were somewhat misleading. Just finished another couple of tests, and indeed: it's 4DOS who is the culprit. No idea, how could it happen; maybe too many things done at the same time, maybe a bit of auto-suggestion (or both) - or maybe too many lines in my fdconfig/autoexec files - but just found out, that neither JEMMEX nor any other memory manager (JEMM386, HIMEMX) should be blamed for described problem. Be it FreeDOS or MS-DOS - contrary to my yesterday's report. Sorry. :( Then there is some strange issue just with 4DOS as command shell. -- regards, Zbigniew ------------------------------------------------------------------------------ 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
