At 04:00 PM 3/14/2012, Zbigniew wrote: >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.
Do you use 4DOS with any special parameters on startup? Ralf ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
