IMHO ==== --------------------------- Memory use -------------------------------- The program requires an initial chunk of memory, plus the size of the resource file, plus some memory for the data files it loads. It requires more memory when a message packet has been opened, and various functions within the open packet screens will require even more memory (which is dynamically allocated and freed). Memory needed for initialisation -------------------------------- At version 1.06, IMHO needs 134K + 10K to load IMHO.RSC = 144K Memory needed for loading IMHO.USR :- Size of file + 16 x No. of Users in file Memory needed for loading IMHO.SIG :- Size of file + 4 x No. lines in file Memory needed for loading IMHO.TAG :- Size of file + 4 x No. of Taglines in file Memory needed for opening a message packet ------------------------------------------ The archiver is invoked to unpack the messages, so you must have enough memory available to run it. After the archiver has finished the messages are loaded into memory. Memory needed for loading messages :- Size of the decompressed file MESSAGES.DAT + 2 x No. of messages + 2 x No. of (personal + All) messages + 2 x No. of personal messages Memory needed for Reading Messages ---------------------------------- Needs :- Size of largest message + Maximum( 8000 or 8 x No. of lines in largest message ) Gets freed on return to "Open packet screen" Memory needed for View Replies ------------------------------ Needs :- 128 x No. of replies Memory needed for Load Replies ------------------------------ Needs the maximum of the following :- Size of decompressed reply file Memory needed to run archiver (probably the most) Memory needed for Make Reply Packet ----------------------------------- Needs the maximum of the following :- Size of largest reply file + 138 Size of compressed reply packet Memory needed to run archiver (probably the most) If the Close Packet option is selected, followed by clicking YES to make a reply packet, then the memory needed for loading the messages is released BEFORE invoking the archiver. You may need to do this if you're short on memory or have a very large message packet to process. Additional memory ----------------- Some options, such as where a file selector is shown, will require an extra 32000 bytes (for a screen save area) just for the duration of that option. In order to reply to a message you need to have enough memory to run the editor. You also need a little (20-30K ?) memory to allow the operating system to function. Complications ------------- The memory allocation routines work in a granular manner; that is, they grab chunks, or heaps, of memory which are then broken up for use by further allocation requests. The default size for a heap is 64K, so even if you are loading very small data files, it will still grab 64K extra. If a chunk of memory larger than the heap size is requested - usually for loading the messages, then a heap equal to that size is grabbed. This means it's not quite so easy to predict the exact amount of memory needed to process a packet. You can change the heap size by using the "Heap Block Size" keyword in the configuration file, IMHO.CFG, in order to reduce the memory required. Generally, making it smaller is better, though if you reduce it too far (say less than 2000) you may hit problems, as it can only allocate 16 heaps at once. Try making the heap size a little larger than the size of the sum of the IMHO.TAG, IMHO.SIG, and IMHO.USR file sizes, if you're really pushed for memory. Otherwise 20-30K will probably do, or leave it at 64K if you have plenty of memory spare. Rough guide to memory used by ZIPJR ----------------------------------- I've noticed that when programs are run from within the OLR they seem to use 50K more than being run from the desktop. The following figures include the extra 50K. When decompressing, ZIPJR seems to use about 290K. When compressing, ZIPJR seems to use about 310K. Ramdisk size, for people using one for the Work directory --------------------------------------------------------- The ramdisk needs to be big enough for the decompressed message packet, plus 7K for directories, plus space for your reply text files plus (optionally) space for compressed QWK packets, plus space for compressed reply packets (and probably plus the space for the editor and archiver if you want to speed things up).