jimomura@lsuc.uucp (Jim Omura) (06/10/88)
I've been writing a program for a while now and I've run
up against "limit" in the OS-9 Level II window system on the
CoCo3. At about 32K user RAM (object module around 24K and
main dataspace of 24K), PutBlk() seems to be crashing. Now,
if this is a real limit of the system and it's not really
fixable, I might as well give up on this current project.
On the otherhand, if it's just a bug in PutBlk() or another
routine I'm working with, and it's patchable, I may just
finish it. That's a bit hard to say. I want to sell this
program and I can't see much point trying to sell it if
it means I have to teach everybody how to patch a system
module. Anyway, if it's fixable, it might be that Microware
and the Shack will get together and sell an update.
I really need more like 40K for this project and
restructuring isn't practical, because there was going to
be another part to this project later that would wipe out
almost all the rest of the RAM in a 512K machine (I'm actually
taking about 128K in total RAM usage on this program already).
Anybody know what's up?
Cheers! -- Jim O.
--
Jim Omura, 2A King George's Drive, Toronto, (416) 652-3880
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomurapete@wlbr.EATON.COM (Pete Lyall) (06/12/88)
As far as 'teaching everyone to patch a system module' goes, why not
write a function that effects the patch from within your code (if in
fact there is/will be a patch). The F$link, and F$CRC are ideal for
this.
Pete
--
Pete Lyall (OS9 Users Group VP)| DELPHI: OS9UGVP | Eaton Corp.(818)-706-5693
Compuserve: 76703,4230 (OS9 Sysop) OS9 (home): (805)-985-0632 (24hr./1200 baud)
Internet: pete@wlbr.eaton.com UUCP: {ihnp4,scgvax,jplgodo,voder}!wlbr!pete