ARP 1.3 and Amy 3000
5 messages in this thread
Lots of things are broken on the A3000. We've gone through three A3000s,
trying to get them to work reliably with motherboard expansion memory.
Some programs hang randomly. Don't blame ARP yet.
Sad to hear about your A3000 experience. Don't know whether to be sad
about the number of broken programs or encouraged about broken programs not
remaining so. Was sort of disappointed were it ARP per se, as I have been
most impressed with the coding so far as functionality goes. Would somehow
break my image of MicroSmiths for the code to have been goofy on 680×0's.
Does this mean that C-A has messed with the documented stable WB/OS
functions again? If so, …. Hope they will at least fix the existing
A3000's! Thanks for the reply! Doug Tittle
I've not had a problem using the Arp commands on my 3000, at least not on
the V1.3 side. Wish I could say the same thing about my bridgeboard…
– Dave
I look at it this way: They needed to ship the A3000. WB 2.0 had to go
with it. They couldn't ship with something called 'preliminary 2.0', so
they called it 'final 2.0.' It's not in ROM yet, on the A3000, it's loaded
from hard disk. So I wouldn't call it "documented stable" just yet,
especially considering the magnitude of the bugs we've seen so far in code
that wasn't documented as potentially dangerous under 2.0.
John:
I saw your note to Doug Tittle. I've had a question for a long time,
and you may be just the man who knows the answer: It's now all but
forgotten by most users, because they long ago gave up, but
Is the DoCollision() graphics routine finally fixed under WB 2.0?
Thanks and regards Tom