jimomura@lsuc.uucp (Jim Omura) (06/02/88)
I think to a point the Shack's general policy of "you get
only as much as you bought" is sort of justified. You buy cheap
programs for the CoCos and so the cost of upgrades isn't factored
into it. *Some* bugs can be acceptable. I never felt that the
Shack "owed me" a new copy of Color Scripsit due to the one or
two relatively rare bugs it had. It worked within spec reasonably.
In the case of the current OS-9 Level II for the CoCo3, I think
they've crossed the border. I think reasonable cost for an
upgrade may be justified, but whatever, an upgrade is *necessary*.
The bugs I seem to running into are too big to be overlooked.
I'm writing a pair of rather large applications. One is
a fair distance to being completed. Memory usage is like this:
Main program 16K (will probably be about 25K when done)
basic dataspace 5K (will be about 10K)
Get/Put Buffers declared 40K (will be about 96K)
Space over overlay windows 16K
The Get/Put buffer handling seems to be the culprit for
most of my problems. I've had crashing. I've had system
memory trashed on exit. I'm not happy about the fact that
often things don't occur in the order I program them too.
Possibly this is a part of the crashing.
I'm writing this under the Window system without Multi-Vue
specifically so this will work with or without Multi-Vue.
As such, there's a chance that some things may be fixed with
WindInt that are not working right under GrfInt. No matter.
If GrfInt is buggy, it should not be sold in its current
condition and furthermore, an upgrade should be made available
as soon as possible.
Guys, "this is not the way to run a railroad."
Cheers! -- Jim O.
--
Jim Omura, 2A King George's Drive, Toronto, (416) 652-3880
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomura