Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!orion.oac.uci.edu!eaeu079
From: eaeu079@orion.oac.uci.edu (Jason Goldberg)
Newsgroups: comp.sys.amiga
Subject: Re: Turbo and the 2630
Message-ID: <25F7DA71.9670@orion.oac.uci.edu>
Date: 9 Mar 90 16:31:44 GMT
References: <9003090636.AA11199@gaudi.CSUFresno.EDU>
Reply-To: eaeu079@orion.oac.uci.edu (Jason Goldberg)
Organization: University of California, Irvine
Lines: 40

In article <9003090636.AA11199@gaudi.CSUFresno.EDU> erick@GAUDI.CSUFRESNO.EDU (Eric Keisler) writes:
>[-----------------------------------------------------------------------]
>Well, I've been using Turbo Silver 3.0 *and* SA4D on my GVP3001 equipped
>A2000 without a hitch for months.  Must be a problem with the 2630 or
>the 2091...
>

The problem is specific to Turbo Silver and the combination of the A2091
and the A2630.  Either of these compenenets will work fine by themselves.
Impulse is VERY rude if you mention this problem to them.  They will deny
any responsibility for the problem and blame CBM.  IMHO, they are full of
s#?!, why are they the only software program on the market that has this
problem?  Anyway, the first time I called, they denied the problem, the
second time they said it was CBM's fault but they are working on it, the
third time they said that if I buy their SV upgrade it will fix the problem,
when I bought there SV upgrade it acted exactly the same, I called a 4th 
time and they said that SV will probably only work if run from the CLI,
when I asked they told me the non SV version also would have woked from
the CLI.  Great way to do buisness guys!  Next, they told me to just not
do any ray-tracing and wait for their next great upgrade, yea right...

I would completly boycott thier product, but it can render some effects I
can't get out of Sculpt and Byte by Byte has their own set of problems as
a company.  Although Sculpt 4D seems very stable on my A2091 and A2630.  

BTW, I have herd completely unconfirmed rumors that the problem is a simple
as something in the A2091 code writing to Mem Location 0.  I don't know if
this is the problem but after booting up I did run a test program and
sure enough Mem location 0 was nonzero.  

-Jason-




-- 

---------
Jason Goldberg                     INTERNET: eaeu079@ORION.OAC.UCI.EDU
                                     BITNET: eaeu079@UCI.BITNET