Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!apple!voder!nsc!amdahl!rtech!cpsc6a!crs
From: crs@cpsc6a.att.com (Chris "I'm Outta Here!" Seaman)
Newsgroups: comp.sys.amiga
Subject: 2091/Turbo Silver problems
Message-ID: <2424@cpsc6a.att.com>
Date: 19 Mar 90 21:01:16 GMT
Organization: AT&T (CPSC), Oakland, CA
Lines: 22



After discovering the incompatibility between Turbo and the 2091 controller
software, and reading some of the discussion on the net, I tried a little
experiment this weekend.  I wrote a small, brute force program to display
and/or set address 0.  Sure enough, after booting, the value of address 0
WAS non-zero, so I tried clearing it.  Turbo loaded with no trouble, and
everything else appeared to be working properly (I was able to build some
simple objects, trace them, and save to the hard disk).

My questions:

Does anyone (preferably someone who worked on the 2091 driver) know why
the driver writes to address 0?  What are the potential consequences of
clearing the value? (I perceived no difference when I did this).  Has anyone
else tried this, and, if so, what has your experience been?

-- 
Chris (Insert phrase here) Seaman |  /o  -- -- --
crs@cpsc6a.att.com <or>           |||    -- -- -        I'm Outta Here!
...!att!cpsc6a!crs                |vvvv/  -- -- -
The Home of the Killer Smiley     |___/  -- -- --