#Disney Animator
20 messages in this thread
Crashes that are ALL TOO frequent. 'Nuff said?
2.0 won't run quite a bit of my software (which I can't really blame on C=,
but one thing I can blame on them is taking clipping out of 2.0). DP:TAS
doesn't work for **** now.
Tom Gandey Gold Disk, Inc. Technical Support
What version are you running? 36.143 is quite stable – I haven't had a 2.0
caused crash since going from .141 -> .143. What programs aren't working
for ya?
Commodore meanwhile has confirmed that the next rev of 2.0 will make copper
clipping optional, with the default disabling it, so DP:TAS will run
without a hitch under that rev.
-Mike e
Is this area protected so we can talk without violating our developer
agreements?
-Greg
What developer agreement? 2.0 is a public release now, right up to the
36.143 revision, so there isn't any problem in discussing it in open
forums. People have been talking about 2.0 problems (and good points!)
quite candidly in the open forums on Bix. You sound like you're still
using Beta 5 or something…..
-Mike
Of course if you're talking about anything after 36.143, then that's a
different story…..
-Mike
As far as I know, although I could be wrong, version 143 was the last
version shipped to developers, although i'm not certain how 'public' that
version is, officially… when in doubt, say 'nuttin.
143 is fully public – current 3000's are being shipped with it.
-Mike
What really ticks me off is that even though I'm a reg. 3000 owner, and
work for the biggest Amiga software publisher, I had to get 2.01 off of a
friend.
Tom Gandey, Gold Disk
C= automatically sent out KS 36.143 to all commercial developers. I can
only conclude that either yours got lost in the shuffle, or Gold Disk isn't
a commercial developer. I suspect that once a 'truly' final 2.0 is out
then upgrades will be sent out to all current 3000 owners i.e. when it goes
into ROM.
-Mike
You started talking about 'features in the next release', which by
defination, is not released. How does that sound like Beta 5, Mike?
Whenever something has been asked on Bix about CBM defining what can and
can't be taked about, there never has been a definitive response (its a
moving target).
>>>What developer agreement?
I assume you received one and signed it.
-Greg
This one particular item has been discussed publicly on Bix, in public
forums there. In addition, Manx has not received any copies of 2.0 beyond
release 36.143 (which is public).
Developer non-disclosure agreements cover items received by the developer.
Since Manx has not received any beta copies of 2.0 since the 36.143
release, I fail to see how our developer contract covers that.
With a product as important as DP:TAS, I felt that it was important to
convey the fact that Commodore is aware of the problem, and is moving to
correct it.
-Mike
With CBM representatives visiting this area, why do their work for them? If
they want to respond, let them. If they don't, then there is a reason why.
-Greg
Greg,
Mayhaps this ought to be moved over to S14/Developers in AmigaTech.
Victor A. Wagner, Jr.
I'm running 36.143 now, while its plenty better, I still get my share of
crashes running AZComm 1.1, Diskmaster, and CED 2.2 Pro.
Hopefully 2.02 will correct these problems…
One question for you… I seem to be getting LOTS of x.7fxxxxxx crashes
could this possibly be a bad ram chip?
These crashes are all under 1.3.2
Tom Gandey, Gold Disk
Yes, it could be bad RAM – tough to say though.
BTW, note also that some incompatabilities are due to speed & 32-bit memory
on the 3000 and have nothing to do with 2.0 (the NewTek dynamic ham viewer
falls into this category).
-Mike
Heh. Keep an eye on the SHAM front to resolve some of the 030-braindead
problems of DHAM..
Mike:
Can you explain why a disproportion of things fail on 2.0 as compared to
1.3.2?
Tom Gandey, Gold Disk
Please define 'disproportion' – that terms kinda vague to me. I have
personally run into very little software which was truly broken under 2.0
(several have minor cosmetic problems which don't bother me all that much).
What titles have you had problems with, and what were the problems?
-Mike
Tom, DiskMaster 1.3 *does* crash on 2.0. PP&S is up to version 1.4 on
DiskMaster, and it runs fine under 2.0. I just got the 1.4 version this
past weekend.