Hi Jim,
I'm bringing back to the list an item we talked about on the video call today: the issue with JEMMEX on VMWare and some hardware configs.
One solution is to not include some memory areas, such as when the installer detects VMWare (that's an easy fix).
It should not be the job of the installer to know about certain, not even real, hardware, what is broken in it. Instead, it would be nice if we could select JEMMEX options which are humble enough in UMB selection. I remember we had similar problems before, when the default config sys boot option was some setting which tried to allocate as much UMB as possible, leading to problem reports and people finding out that another, also pre-installed boot option with more cautious UMB detection was stable for them. They did not have to "manually know" that their specific hardware or VM model X needed a manual exclude of region Y. They could use the easier method of just selecting the more careful JEMM style :-) Not sure if I remember this correctly, but you get the idea. Also, detecting known-broken VMs to adapt JEMM actions to not fall into the holes of the broken VM sounds like something which could be built into JEMM itself ;-) Regards, Eric _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
