Re: available memory

[cld@xxxxxxxx]

-------------- Original message ----------------------
From: flash 
> Not being familiar
> with Xy4, I wasn't sure whether this is normal behavior or peculiar to
> my constellation. It seemed peculiar to me that Xy4 had a quarter of the
> available memory left compared to Xy3. I guess it's normal.

It's normal. Ignore the X, ignore available memory numbers; they're not errors, they're correct,
just nothing to fret about. Xy4's memory management is light years ahead of Xy3's. (To take one of
many possible examples, try working with, say, a 1 Meg DeFined block in Xy3. No can do.)

> I will try to unload some of the features I don't need, if possible. The
> Xy3 memory window has a load/unload function to kill processes and
> components singly, which I didn't find in the Xy4 memory window. Can
> processes be "no load"-ed in the Xy4 startup.int file? If not, perhaps
> you can give me command-line kill-syntax from within Xy4 and I'll
> experiment with the various processes to see what I live without.

Try if you like -- the syntax is BX UNLOAD -xyzQ2 , where x, y and z are components listed in the
memory management menu -- but I think you'll find it's not worth the effort. Xy4 often reloads
unloaded components; you may not think it needs them, but Editor knows it does. As I say, none of
this is a problem.

The only memory component worth paying attention to is programming memory a/k/a Save/Gets, value (in kilobytes) returned by . Good to keep this down in the 5-6 range, if possible. There's a U2 routine, KILLMEM, that will do it for you if the number gets too high. Generally speaking, if it's below 10 or 12, you're OK. Really, you only need to pay attention to it if Xy gets flaky. If it happens, you'll know it.

--
Carl Distefano
cld@xxxxxxxx