mg@notecnirp.Princeton.EDU (Michael Golan) (02/23/89)
I have a 386 machine with the "neat" chips set. IT seems that the only way to use the "reserved" (384K) of memory above the 640K (out of 1M ram) is as bios shadow and/or as ram in locations C800:000 to F000:0000 (160K). I know that many people have "ram holes" unused in these locations. The only use for it I could find in simtel20 is a program called ADJREM which creates a ram disk from this memory. I think it should be easy to make dos believe it has memory up to F000:0, then "allocate" it all up to C800:0 and then load tsrs, and free the memory upto 640K. Does anyone have a program to do that? can it really be done? Email or post, I will summarize results (if any! my last request was on the paradize vga plus 16 card was completely ignored ...). Thanks for your time Michael Golan mg@princeton.edu
asgard@cpro.uucp (J.R. Stoner) (02/25/89)
From article <15128@princeton.Princeton.EDU>, by mg@notecnirp.Princeton.EDU (Michael Golan): > I have a 386 machine with the "neat" chips set. IT seems that the only way > to use the "reserved" (384K) of memory above the 640K (out of 1M ram) is > as bios shadow and/or as ram in locations C800:000 to F000:0000 (160K). Please don't do that. It has been said to me (the source could be wrong) that Compaq 386/25 with Flexcache has some kind of interaction with that region of memory, specifically 0x00d0000. I can't test this myself as I do not have a Compaq machine. I do know that Novell/SMC and CompuPro network adapters use this memory for packet buffers. If you want to also get the purported benefits of IBM SAA they also use this region of memory as the cluster adapter IPC buffer. > I know that many people have "ram holes" unused in these locations. The only > use for it I could find in simtel20 is a program called ADJREM which creates > a ram disk from this memory. SIMTEL20 is not the universe, you know. Real programmers working for real companies are writing code that make use of this memory according to real published specifications. In the case of a program making unknown use of the network buffer memory, if it works more power to you, but be cautious from now on about attributing bugs to program authors where they more properly reside with the system integrator. > Thanks for your time > Michael Golan > mg@princeton.edu -- "To prevent having to tell fools to RTFM don't let on you WTFM in the first place." - J.R. (May the Source be With You) Stoner asgard@cpro.uucp asgard@wotan.uucp asgard@well.uucp ...decwrl!pacbell!cpro!asgard