To one and all, I have found what seems to be an increasing problem with increasing ram in my system. The problem originally showed itself with some older Dos apps that were made originally in the pre-64Meg boundary days - the days when no one thought that any system would have more than 64Megs of ram. Well, fortunately or un, systems these days can and do commonly, including mine. The problems that were originally affected had done some weird calcs that used that border to tell how much ram was found in the system. Unfortunately, when you had more, it ended up thinking you had negative ram and would not work. That problem was not so really big and important BUT last nights is. I had, previous to last night, 256 Megs of ram in my system. And no problem loading some dos devices and related from my config.sys and autoexec.bat file, such as when I booted directly into Dos (running Win98SE). However, yesterday I installed another 256 Megs of ram in my system, and now several items that used to load do not seem to at all. The package was original from Helix software, and was consisted of a main device driver that would get loaded into XMS/EMS ram from config.sys, and then several other programs that would load also into similar mem, with just a small amount loaded in conventional/high ram - these included a mouse driver, CD driver, and cache. UNFORTUNATELY, after adding the additional ram, for some reason, the main device driver will no longer load in XMS/EMS memory - get a weird message related to memory. And the mouse and CD drivers will end up getting loading totally in conventional memory, and the cache part will not get loaded at all. After this whole message, where I used to get around 600K of conventional memory after all was loaded, I ended up with only around 550K of memory, with the result that some dos programs I need to run in a native dos environment will not run now, due to low memory problems. Other than removing the new ram unit, I am not totally sure what to do at this point. Is there some kind of device driver or similar that I can load when Dos is booting up, that will use up most of the ram and the ram will not be seen by other stuff after it??? This would be some kind of driver similar to the old ramdisk device driver that has come with Dos, but was limited to only taking up 64Megs of ram. I know, in this day of less and less dos to be found and used, this might seem strange. BUT, some of these older dos programs have proved to be VERY useful yet in this day and age. So can anyone think of any device drivers that can be used to do this operation for me in native dos mode??? Ralph ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
