[comp.sys.amiga.hardware] a3000 bridgeboard

dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) (04/10/91)

  I know that people have used the Bridgeboard in a3000's by removing the
back plate. Is this true, and are there any other incompatibilities? How 
many IBM slots are left over? Is there room for an internal 5.25 drive?
Although I have an a3000, it is not within 400 miles, so I can't check it out.
I have been inside it before when installing ram, but never saw enough room
for the floppy drive.

-- 
    David Tiberio  SUNY Stony Brook 2-3481  AMIGA  DDD-MEN  Tomas Arce 
           Any students from SUNY Oswego? Please let me know! :)

                   Un ragazzo di Casalbordino, Italia.

drysdale@cbmvax.commodore.com (Scott Drysdale) (04/11/91)

In article <1991Apr10.002547.18565@sbcs.sunysb.edu> dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) writes:
>
>  I know that people have used the Bridgeboard in a3000's by removing the
>back plate. Is this true, and are there any other incompatibilities? How 
>many IBM slots are left over? Is there room for an internal 5.25 drive?
>Although I have an a3000, it is not within 400 miles, so I can't check it out.
>I have been inside it before when installing ram, but never saw enough room
>for the floppy drive.

"removing the back plate?"  that's the toaster, not the bridgeboard.

there's no space for a 5.25" drive that's externally accessible.  if you have
an unusually thin 5.25" hard drive, it's possible that you could fit it in
there by laying on top of the 3.5" drives.

the 3000 has only 2 bridgeboard slots.  if you use a 2286 bridgeboard (at),
and you want one free pc slot, you'll lose the amiga/video slot.  if you want
the video slot, you'll lose a pc/amiga slot.  the 2088 bridgeboard (xt) only
takes up one slot, so no magic.  you'll have one amiga/pc slot, one amiga
slot, and one amiga/video slot left over when you install the 2088.

once more, here's what you have to do if you run a bridgeboard under ks/wb
2.0 on a machine with a data cache (a 3000, for example):


the problem:
	on a system with a data cache (68030 and up) running ks/wb 2.x,
	the data cache is enabled by the operating system.  under 1.3, the
	data cache is never enabled, so no problem.
	the bridgeboard (and possibly some other cards) is a large chunk
	of shared memory.  if either the 80x86 or the 680x0 caches anything
	in bridgeboard address space, things won't work.

the solution:
	you must disable data caching of bridgeboard address space when
	running ks/wb 2.x on a 68030 or better system.

method 1:
	insert the line:
	CPU NODATACACHE
	before the binddrivers command in your startup-sequence.  this will
	disable *all* data caching, potentially slowing your system down
	slightly.  everyone with 2.x should have the CPU command.

method 2:
	insert the line:
	ENFORCER QUIET
	before the binddrivers command in your startup-sequence.  this will
	disable data caching only for bridgeboard address space.  other
	"normal" RAM in your system will be cached as usual.  not everyone
	has ENFORCER, and only recent (past few months) versions know
	bridgeboards.

>    David Tiberio  SUNY Stony Brook 2-3481  AMIGA  DDD-MEN  Tomas Arce 

  --Scotty
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Scott Drysdale           Software Engineer
Commodore Amiga Inc.     UUCP {allegra|burdvax|rutgers|ihnp4}!cbmvax!drysdale
		         PHONE - yes.
"Have you hugged your hog today?"
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=