gonzalez@bbn.com (Jim Gonzalez) (04/12/90)
I compiled and ran RED, early this morning, after struggling to get L2 together (the BDS documentation could use a few corrections, here). RED cleared the screen, positioned the prompt line in a bogus place, and then quit after printing: Error: not enough room for buffers This is on a 64K system. I had linked RED using L2, since CLINK had been complaining about not having enough memory. The BDS manual suggested that CLINK might do this, and L2 was included in the distribution as a solution. L2 had reported the following: Number of functions: 255 Code ends at: 0x984 Externals begin at 0xA400 Externals end at 0xB018 End of current TPA: 0xC700 Jump table bytes saved: 0xB97 It sure looks like RED doesn't have much room left for file. I must admit that I was apprehensive when I saw the link statistics, and not surprised when RED quit on me. At least it didn't walk all over CP/M. The bogus placement of the prompt line is my problem; I botched the control sequence when I ran RCONFIG. I doubt that this would affect buffer space. So. Any ideas on what might cause this? I used the supplied SUBMIT files, which copile RED1.C through RED14.C and then link it. L2 had to go to file mode, it ran out of memory after getting to RED4.C. This is on a Cromemco System Three running CDOS. -Jim.