Hi Eric, > On Feb 17, 2025, at 7:17 PM, Eric Auer via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > > Hi Jim, > >>> as several people reported SIGSEGV / page faults with MINIBOX, >>> for example MINIBOX PWD or MINIBOX CLEAR, I wondered whether >>> the crashes are just a symptom of the EMM386 issues discussed >>> earlier. Or rather: Some VMWARE problem causing problems FOR >>> EMM386. On which real or virtual hardware are you testing? >> You might have missed the note in my email where I said I even tried >> booting FreeDOS without anything loaded (no FDCONFIG or AUTOEXEC) and >> still got those errors: >>>> *And to test that nothing else was getting in the way, I booted my >>>> system without a FDCONFIG.SYS or AUTOEXEC, and still getting these >>>> errors. > > I have not missed that note. That is why I explicitly said: > "Some VMWARE problem causing problems FOR EMM386" and later > explained that everything somehow touching protected mode > can be affected by such issues.
My tests were under VirtualBox not VMware. VirtualBox does not exhibit the “out of memory” issue which occurs in VMware. I get that error using any of the 4 boot options in VirtualBox. (Note: Most other platforms (default configs) get 5 options. However, option 1 of the default config is not compatible with VirtualBox. Therefore, VirtualBox gets a different config that omits those settings.) I also ran MINIBOX from within its own directory. No change. Still get those errors. I had no issue running FreeDOOM, DILLO and LINKS under the default boot option for VirtualBox. Jerome
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
