A4000 Systems
On A4000/040 systems, the Enforcer program should not be necessary (see the
A3000 section), but you should verify proper
operation of the GG2 Bus+ yourself. Note that since the A4000/030 card
typically uses a Motorola 68EC030 (which does not have an MMU), you will
not be able to run Enforcer. This is a problem because of differences between
the '040 CPU card and the 'EC030 CPU card; the '040 card has a different idea
of how to maintain its cache and does not try to cache the portion of the
memory map that contains the GG2 Bus+ board, while the 'EC030 board does try
to cache that area. Normally, the solution would be to run Enforcer when
using a GG2 Bus+ board in an A4000/030, but Enforcer requires an MMU to do
its job. Because of these factors, the only viable solution is to disable
data cache entirely while using the GG2 Bus+ in an A4000/030. No information
is available at this time regarding 68060 accelerator cards.
On an A4000 system, depending on the speed of the PC card you are using,
you may be able to run the GG2 Bus+ with "zero wait state" operation
for a possible speed increase. The default is for one wait state to be
added to each bus cycle. To change this, you must turn off the wait states
using the SwitchControl program provided in the software package. If you
experience no data loss, system crashes, or other errors, you may consider
moving the wait state jumper on the GG2 Bus+ board from the "on" to the
"off" setting, in order to have the "wait states off" as the default mode
on power up and after software reboots.
Note: The wait state mode can be changed at any time through software
using the SwitchControl program.
HTML Conversion by AG2HTML.pl V2.950424, perl 5.000 & witbrock@cs.cmu.edu