Reply 20 of 28, by wierd_w
Run memtest.
It can tell you which one.
Run memtest.
It can tell you which one.
wierd_w wrote on 2024-06-22, 19:10:If it were me, I would set the emm386 line like this: […]
If it were me, I would set the emm386 line like this:
Device=C:\windows\emm386.exe ram I=b000-b7ff I=c800-dfff p=e000 notr
AND i would replace the RAM.
The /testmem:off on himem.sys is to speed up boot on systems with known good ram. Not to skip the testing to halfass use bad ram.
😀
Emm386 uses xms memory, mapped into the adapter rom region, to do its thing. If that memory is faulty, you will get the behavior you are experiencing.
Tried adding the amended line to config.sys but get the following on screen then it comes up with insufficient memory. Same issues in DOS, a general protection error anytime I go to run software.
Got ahold of memtest. Will copy that over later today when I get a chance and see what it comes up with.
Hmm.. looks like it's either not worth turning on the monochrome display buffer region as UMB, or fancy stuff with load order needs to happen.
as for the emm error.. I must have been asleep at the wheel. Correct statement is frame=e000 not p=e000
So, see if this plays nicer.
Device=c:\windows\emm386.exe ram i=c800-dfff frame=e000 notr
The issue of windows crashing/hanging is probably related to the suspicious bad ram himem.sys is reporting.
wierd_w wrote on 2024-06-22, 21:12:Run memtest.
It can tell you which one.
Finally getting back to working on the PC. Ran Memtest86 via a boot floppy. It’s currently been running for close to 18 hours now which I don’t thing is right?
Overall I 128Mb which comprises of x2 32 Mb & x1 64Mb.
So far I’ve had 21 passes. (See screenshot) - but I couldn’t tell you which memory this relates to? Any advice would be greatly appreciated.
Col.
Interesting.
Memtest has a much more aggressive test regimen than himem does, so I wonder why himem is reporting bad ram?
wierd_w wrote on 2024-10-13, 10:06:Interesting.
Memtest has a much more aggressive test regimen than himem does, so I wonder why himem is reporting bad ram?
So should I keep running memtest just now?
If it's gone that many passes, the ram is likely fine.
It will run endlessly if you let it.
I subltly wonder about cache being bad now.
FWIW the current memtest86+ 7.00 works fine on 586-class CPUs like the K6 family. Download the binary files and write memtest32.bin directly (raw) to the floppy. If necessary, pad it with nulls to 1440KiB if the software insists on the image being exactly the size of the floppy.
It should detect the L2 cache size on the Aladdin V chipset and the SPD info on the SDRAM DIMMs.
76kb is reserved.
I'm pretty sure that means it's not tested by memtest.
Maybe the fault is there?
Assuming that is correct, and the memory isn't interleaved or anything, you might get faults in memtest by swapping the memory around.
You said you have 3 sticks.
Logically, it's most likely for the first stick to be the "lowest".
Leave the middle stick, and swap the other 2 and rerun.
I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11 auto-install iso template (for vmware)
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic