gonzalez@bbn.com (Jim Gonzalez) (04/12/90)
My thanks to Frank Wancho for pointing out the discrepancy in the link statistics. The trick was to adjust the location of the start of the externals area to free up more memory. It bothers me that I had to recompile each C file to adjust this figure. It took me close to an hour. The editor now runs, sort of. It clears the display, sets up the prompt line and version message, and then sits there. I get no response from the keyboard, not even from ^C. I have to reset the machine to recover. Oh yeah, and it doesn't display the expected "end-of-file" marker or help instructions. If I invoke it with a file specification, it does the same display set-up, then loads the specified file, displays the first page, and then sits there. So, it looks like the keyboard input code may be the problem. I've seen warnings in the BDS C manual about BIOS differences between real CP/M and look-alikes, my CDOS being one of the latter. The calling conventions are the same, however, as are almost all of the call codes. The fact that it manages to do display set-up and file I/O seems to rule out BIOS differences, but I can't be sure. Can anyone tell me? -Jim.