Hi, On Tue, Aug 25, 2015 at 1:04 AM, Mateusz Viste <mate...@viste.fr> wrote: > Rugxulo, Ralph, > > Thank you both for your inputs! Here's the endgame :) > > I already tried to test the RAM on this machine using both "AleGr > MEMTEST 2.00" and "MEMTEST86+ 4.20" (from a boot floppy), but both fail > miserably - AleGr MEMTEST imemdiately freezes, while MEMTEST86+ > immediately reboots the PC.
I vaguely remember an older version (circa 2003) hacked by Eric, which I think is this one, so if super curious, you could try it: http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/memteste.zip > The BIOS test passes though, so even if RAM chips are bad, they are at > least seemingly behaving correctly. Well, it's probably not your RAM then. > Now, I tested two things: > > MS HIMEM v2.06 (from the XMS developer disk, with sources and all) - > works fine, mem detects all XMS memory, Wolf3D is happy, no wild > reboots, no freezes, everything works (yaay!). This is not a 'free' > solution, so it can't be considered viable, but still - WORKS (meaning > my 386 is not totally wasted). Also, MS HIMEM consumes 30K of > conventional memory, which is not cool. Yes, at least it works, so that's good. > HIMEMX v3.34 (as per Rugxulo's suggestion) - miracle, this one works > perfectly - mem sees all the RAM, Wolf3D is happy (as well as all other > applications I tested), no crash, no reboots, no freezes, no nothing. > Solution found! Again, it's probably the 386 "jmp $+2" cache flushing (or whatever, I'm no systems programmer). > I didn't test XMGR, since I don't really see the point, XMGR being a > dead end anyway. Well, slightly older is still on iBiblio with sources, for comparison. > About HIMEMX: > 1. The 'TESTMEM:ON' switch is not working - with my limited ASM > understanding, I think it checks for "TESTMEM:OFF" only, while the > default is OFF anyway. Dunno. > 2. What makes the v3.34 "unofficial"? Maybe might it be a good time to > advertise it as "official", so other people would avoid going through > hoops like I had to? There are no maintainers. I don't even know who (if anybody) would even have the interest to decide to even release a "new" version. Literally, the previous two versions were hacks done by random people, and even those are from years ago. So it just doesn't seem to show much activity. I actively use 3.34 with no problems, but that's far from exhaustive proof that no bugs or regressions remain. I agree that the 3.32 "bug" is bad for 386 owners, but it's unlikely that anybody cares (well, besides you and me and a very few others). In short, I don't know what to tell you. What do you want to do? Clean up the sources? Repackage it? Edit the Software List? Become maintainer yourself?? (Can't be any worse than /dev/null.) ------------------------------------------------------------------------------ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user