VOGONS


First post, by auron

User metadata
Rank Oldbie
Rank
Oldbie

when i go to run memtest86+ on a pentium, using a boot floppy created as per the instructions, the tool instantly crashes with an out of range message on the monitor. my first thought was that it's trying to use 686 instructions, but on the site it says that it should run on pentium and up. can anybody confirm that memtest86+ does run on pentiums? memtest86 does run fine, forgot which version of that i have but should be the newest.

assuming that memtest86+ is supposed to run fine, that would put my floppy at fault, which i didn't create really all that long ago. it's one of those very late verbatim ones bought new sometime in the 2010s and i'm unclear as far as their reliability goes. is there a tool out there that can verify a floppy against a .bin image?

Reply 2 of 2, by jtchip

User metadata
Rank Member
Rank
Member

There are screenshots of various users running memtest86+ >=6.0 on i586-class CPUs (an AMD K6-2, SiS 550, Intel Pentium and Pentium MMX), and even an Am486DX4, so it definitely works on Pentiums.
I have used memtest86+ 6.20 on a Pentium MMX and a K6-2+ (both only support the i586 instruction set), the former running memtest86.bin via GRUB4DOS on MS-DOS 7.10 (Win98SE without the GUI) and the latter via PXE from the boot rom of a 3Com 3C905C, with the TFTP server serving pxelinux from syslinux 6.04.
I have just tried the latter again with the latest 7.00 release and it still works. I avoid using floppies if possible because they're a hassle.
When you say you say "using a boot floppy created as per the instructions", which instructions are those? The only mention of floppies on the main page is "If you need a floppy image, use the "make iso" command to generate a 'floppy.img' file" but the binary files, specifically memtest32.bin from the binaries, should just work written directly to a floppy. On Linux this would just be:

dd if=memtest32.bin of=/dev/fd0 oflag=direct status=progress

There is a floppy.img make target but that justs writes memtest32.bin into floppy.img and pads that with 0s to 1440KiB.
The fact that your monitor went out-of-sync suggests something wrong with the binary that was written to the floppy as memtest86+ only uses text mode.