Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!LL.ARPA!SAGE From: SAGE@LL.ARPA Newsgroups: comp.os.cpm Subject: Determining TPA Requirements of Programs Message-ID: Date: 29 Apr 88 20:11:29 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 11 Richard Secrist asked about determining the amount of TPA that a program needs. There is no way in principle to do this. Well written programs test to make sure they have enough room and abort with a suitable message if they don't. On the other hand, there probably are not very many well written programs (I certainly have not written too many of them!). An experimental approach would involve zeroing out the TPA memory (for example, with DDT), then running the program, and finally examining memory to see what data got written where. Under Z System it is easy to examine memory without using any (with the RCP peek command), but there is undoubtedly some way to do this under CP/M as well.