knudsen@ihwpt.UUCP (mike knudsen) (04/22/86)
Why would OS9 (on Coco) boot up and silently throw away almost 4K of RAM at the top? I use two different boots (made by os9gen). Both are pretty well stripped down. The "CCIO" boot uses RS' CCIO screen driver. The other "Wordpak" boot uses Wordpak's driver instead. An MFREE on the Wordpak boot gives 169+1 pages free, which allows some good-sized C compiles; MDIR itself loads at $B300. But the CCIO boot shows only 150+1 pages, and MDIR loads at $A300, or a full 4K lower. Both boots begin with SDISK at $BE00 (I think). Some invisible object is holding on to 4K of RAM below the booted modules! Now, MDIR E shows that CCIO is two pages bigger than Wordpak, plus I know CCIO eats up two pages for the text screen (we're not talking graphics just now). That accounts for 4 of the 19 pages. Where did the other 15 pages go? Both boots have the same startup file (just "setime < /term"). I'd use Worpak all the time, except that my application is graphic. I can't compile nontrivial C code without rebooting Worpak, and can't test it without rebooting CCIO, etc. Please help me find those 15 pages of RAM.. thanks, mike k PS: after throwing out Pipes and Printer stuff, I get 153+1 pages in CCIO boot. The addresses given above are actually from that boot.
jimomura@lsuc (04/25/86)
This is just a wild guess, but it could be a set of buffers, such
as type-ahead buffers, Shell buffers, possibly even shadow buffers for
screen data.
Talking about WordPak. Does anybody know what the RAM chip upgrade
for the WordPak II is to get 8K video RAM? I've got the WordPakII and
the 2K chip seems to be 8347, SY2128-3. It's sitting in a 28 pin (oversize)
socket.
Cheers! -- Jim O.
--
James Omura, Barrister & Solicitor, Toronto
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomura
(416) 652-3880