CompuServe Messages

#WShell RESIdent Problem?

    05-Oct-88 01:50:22
Sb: #14625-#WShell RESIdent Problem?
Fm: KEITH YOUNG 73170,307
To: Mark Olbert 73557,1512
Why does it make a call that frees up mem? Well, there's only so much memory in the machine… and if you need a large chunk of it (contigenous) but there is a (theoretacle) 1 byte long library in the middle of it (not currently being used) then you can't get the one big chunk. I'm not an expert on this type of thing, but each library and/or font loads into 'some' space in memory, which eventually 'fragments' the large sections of memory available into smaller chunks (running programs also allocate various small chunks, worsening the situation) so that ( in this case ) when I need to re-size/move one window (requires mem) and open another (more mem) I need a little breathing room. Allocating 16 megs (trying to) will do just that <grin>. This was just the only way I knew of to do it (and had seen examples of). Unfortunately, it effects things like Facc II (I think), resident commands and alias commands, most of which were not around 2 yrs ago. I now know of a way of removing unused fonts (that were loaded within Access!) from memory… I think it's a 1.2 command, so I can change that part of the code. – Keith