At 12:41 2001/7/31, you wrote:
>To one and all,
>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.
Well, then, can you think of a system with only 32 MB of ram is still
running now, using Win 98 and running ICQ, Eudora 5, Opera 5 and FlashGet
all at the same time?
>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
Do you mean the Helix Cloaking?
>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 can't think of any device driver which can suck up so much RAM, but I
think there's alternative for your current device driver set. For memory
manager, keep with HIMEM.SYS, it provides the greatest compatiblity. Then,
you may use UMBPCI to provide UMB, which just make those original Shadow
RAM available for writing. Then, you may use smartdrv to provide caching,
ctmouse for mouse driver, SHSUCDX.EXE to replace MSCDEX. There's a
homepage, http://users.aol.com/axcel216/ , which provide just the
information above.
--
File Operator of
PersoNet (Virtual ISP in Hong Kong)
http://www.personet.net
============= 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
=====================================================
