hey jcc,
re: "Now if I could just figure out what it means..."
lol! i hear you. <g3> some of it makes sense to me. what particularly caught my eye is the 'high memory' category, and how empty it is. is it the same on your system?
now let me refer you to a recent post of mine...
#reply-11565620 that references a fred langa piece called 'by the bootstraps'. btw, the article contains an interesting fact about how we came to call starting our computers booting.
fred points us towards reclaiming what he calls a chunk of commonly wasted memory space (i.e. high memory). he goes on to state,
"What the above does is to tell your system to use to two "memory managers" (himem and emm386) to access to all your PC's memory including a normally wasted area of "high" or "upper" DOS memory; to allow certain types of device drivers to reside in that otherwise-wasted space; and to load the core elements of DOS itself and any DOS apps in your Autoexec file "high" and out of the way of other programs."
there is, of course, the requisite disclaimer... "the standard cautions apply: None of this stuff is very dangerous, but it always, always, always makes sense to make a backup before you twiddle any system settings".
and another remark,
"if you don't like the results, just re-edit the files with Sysedit to put things back the way they were before, and reboot. Simple!"
________________________________
i have not tried these adjustments yet myself. i've made several changes to memory recently. so far they are working out nicely. i don't want to tweak too many things all at once. i'm in an observation phase at the moment. but i fully intend to give the article's "cut-and-paste commands" a test drive very soon.
and when i do, perhaps more of what i see when typing MEM in the start/run box will make sense. <g3>
any comments always welcomed!
:)
mark |
