I would like to advise you to heed the VMSIZE warnings LISTSERV is sending, not only because I get a copy after every reboot and it can become particularly hectic when I send out a new release and 200 servers reboot the same day ;-), but also because LISTSERV is going to need more and more virtual storage in the future, even though performance will improve and paging will not necessarily increase. For 1.7c, I have mostly converted EXECLOAD'ed supervisor routines to PASCAL with a ratio of a bit less than 1:1 (much to my surprise - in fact, 1.7c would be smaller than 1.7b if I hadn't added LISTFAQ MEMO), so the amount of virtual storage needed is roughly the same. I also removed quite a lot of code from LSVDIST2, which is EXECLOAD'ed. However, when I convert a non-EXECLOADed routine, I am increasing the size of the big MODULE which LISTSERV loads at startup without decreasing the amount of EXECLOADed data, and more virtual memory will be needed. It is not possible to make separate MODULE's because of shared static data areas and because it would lead to horrendous performance anyway, with some 120k of library code which would have to be reloaded every time. So the bottom line is that if you decide today that 2.3M is close enough to 2.5M that you don't need to worry, you will end up having to increase sooner or later anyway as each release contains more and more resident data. 1.7c increased the size of LSWPLIB by 92k. Eric