Op 30-7-2011 17:05, JPT schreef: > Was 3x128 + 1x256 = 640, but recognized only 384 MB. This might indicate > a problem. Removed all but 1x128 MB. Memtest runs fast now, > 20 mins for 2 passes. Everything ok. > I will reinsert and check some of the other memory modules later. > (I did memtest before without error, but who knows...)
Not all memory modules are created equally indeed, layout and chip density matters a lot. > > - disk, ontrack is running, 2h. > No error. > I have my rescue floppies and CDRWs always at hand, but the labels > aren't matching the content any more, for most of them :) Typical hehe. What's this Ontrack thing you're running? Hope it's not that crappy 'disk drive overlay' software that was used ages ago to have system BIOS work together with harddisks that had a relatively huge capacity. > - CPU clock rate too high for a lot of old dos software? > Do you think clocking down to below 500 Mhz might help? > Bart says so for his network boot floppy. No idea. Shouldn't matter much unless running into some Pascal programs that haven't been fixed yet, or in programs speeding up whenever the CPU is more powerful. > - A20 stuff... > especially the XMS/EMS driver loading seems to fail often. > I have in mind that A20 has to do something with EMS oder XMS. (or UMB?) > And, A20 is some hack using the keyboard controller. > Since I attached an USB keyboard to a USB switch, for easily switching > between computers... could this be a problem, eg in the BIOS USB > Keyboard code? A20 was keyboard hardware related but typically it's used whenever providing extended memory, while also unlocking 64 kilobytes of HMA, often best used by DOS=HIGH in config.sys. As I've experienced issues earlier with that, you could try DOS=LOW. Other options might be performing a clean boot, and either skip loading memory driver, or load it from commandline: DEVLOAD XMGR.SYS or JEMMEX.EXE LOAD > btw, the fdisk program contained on the floppy sucks. > created a bad partition layout. have to move partitions now... > what about xfdisk instead? If you really have a Disk Overlay program running (Ontrack, Compaq stuff etc) then that might explain a lot. There's always some Linux bootCDs like Parted Magic for example. Maybe UltimateBootCD (UBCD) is of help as well. > - Install debian... for having less trouble with partitioning in the > future, and to verify the hardware. Good step. I wonder if a Win98 bootdisk gives you the same issues as the FreeDOS one does (provided it contains FDISK in the first place) > - install Freedos 1.1T3 > Ran through in almost no time, wow! It's a small disk still. Glad it works mostly for you. > I got the same error message from Jemm, but pressing ESC continued > booting the installer. > So where do you suggest to continue? Should I jump to the 1.0 installer? > or should I install manually? Could you point me to a tutorial for > manual install, or is it just "unpack anywhere", as we are used from old > dos? Do what you think it's best. It's rather complicated to explain stuff from this point on as the FD1.0 installer might ruin FD1.1 settings and files, and lacks a lot of flexibility that I've added recently. You'll have to find the INSTALL.EXE in D:\FREEDOS\SETUP\INSTALL\ and find out it's options. Could swear I had a batchfile somewhere for that, but oh well. ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
