> On Feb 2, 2025, at 10:23 AM, Bernd Böckmann via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > Hi Jerome, > > hope you are feeling better! > > Am 02.02.2025 um 16:06 schrieb Jerome Shidel via Freedos-devel: > > >> Do all boot options result in the “out of memory” error? > No, it works when booted with JEMM386 and HIMEMX. > >> Also, JEMM was updated to 5.85 for RC2. I doubt it will make any >> difference. But, you may want to test the previous version of JEMM with >> FreeCOM 0.86. Since I have not had the opportunity to update the packages on >> the update/download repository, you could just use FDNPKG to remove then >> install JEMM386. That would fetch 5.84 from the repo and install it. Easy to >> do with networking under VMware. However, I do not think it likely to fix >> the issue. > I tested with JEMMEX 5.84 from RC1. Same problem. However, when I boot with > FreeCOM 0.85a and then launch FreeCOM 0.86 after the system is booted, it > works. > >> This could be related to the “out of memory” issues Paul Dufresne was >> experiencing on real hardware with RC1, FreeCOM 0.85a and JEMM 5.84. That >> seemed to occur while FreeCOM was initializing. I think he was able to >> mitigate the error by changing what was loaded prior to FreeCOM. However, I >> do not think the actual problem was found or fixed. > Seems indeed to be the same problem. Question would be which component > actually causes this: FreeCOM, JEMMEX or KERNEL? Tricky to debug if it only > occurs sporadically. > Greetings, Bernd > >
Unfortunately, the newest version of VMware I have is 11.5.3 running on an older Intel Mac. But after installation of RC2 into a fresh VM on that machine, it gets an “out of memory” error using option 1 or 2 of the 5 that are available. When selecting either of those first two options, JemmEx displays a message “System memory found at dc00-e7ff, region might be in use” After that FreeCOM tries to load and gives the generic “out of memory” error and attempts to terminate. Which puts us in the cannot terminate permanent instance loop. :-( For fun, here is a neat little trick with LOGGER for the VMware config files…. First edit the FDCONFIG.SYS file by uncommenting the entry for LOGGER. After that line, add two more lines: 123?INSTALL=C:\FreeDOS\BIN\MEM.EXE /DEBUG 123?INSTALL=C:\FreeDOS\BIN\LOGGER.COM This will cause FreeDOS’s MEM command to provide “debug” output which is automatically captured by LOGGER. Then FreeDOS will run LOGGER in "view log" mode before FreeCOM is loaded. Please note, viewing the log turns off logging. If additional logging is desired, you will need to add another line to tell LOGGER to re-enable logging. Future versions of LOGGER will probably get a “save to file” option instead of always requiring I/O redirection. That could be extremely useful in situations like this. But for now, if someone really needs that feature, they will need to make it themselves. LOGGER does have a fairly easy API and even includes a demo program to “print” the current log to STDOUT. Not hard to modify that demo program to dump the log to a file instead. Like adding RLE to its storage in memory, a “save to file” feature is planned for future versions if LOGGER’s general usage grows. :-) Jerome > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
