U211344@HNYKUN11.BITNET (Olaf 'Rhialto' Seibert) (01/31/89)
I played a little with Xoper recently, and looking at the library
overview I noticed that the expansion.library and romboot.library
both had an OpenCount of 1. So obviously someone is keeping those
libraries open for no apparent reason (at least the reason is not
apparent to me). Since there is nothing to expand after the boot,
and nothing more to boot either, I would think those libraries
would not need to be open any longer. They just waste some of my
precious memory (of which I now only have 512K) with their
library bases.
So I tried to close them forcibly (still with Xoper), and then
expunge them, but they would not go. They were completely 'stuck'
into memory.
I also saw that the ramlib.library had an OpenCount of 1. So I still
wonder what that ramlib.library is for.
So, who keeps those libraries open and why?
Freely_Distributable=Greetings(Not_For_Any_Commercial_Purpose)->
Olaf.Seibert;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Q: How many lines does it take to screw in a disclaimer? A: Only two.
--- Olaf Rhialto Seibert the Marvellous --- U211344@hnykun11.bitnet ---
Study safely - stop deets 7167 BYTES FREE Too painful to do right
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*bryce@cbmvax.UUCP (Bryce Nesbitt) (02/01/89)
In article <@jade.berkeley.edu> (Olaf 'Rhialto' Seibert) writes: | |I noticed that the expansion.library and romboot.library |both had an OpenCount of 1. So obviously someone is keeping those |libraries open for no apparent reason... The reason is so expansion.library can hold on to it's lists of configured boards. |So I tried to close them forcibly (still with Xoper), and then |expunge them, but they would not go... The expansion.library cannot be expunged under V33/V34 Kickstarts. Sorry! More things will be expungable in the future. Don't depend on "romboot.library", it may disappear in the future. Ignore "ramlib.library", it is an internal construct only.