Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!waikato.ac.nz!comp.vuw.ac.nz!matai.vuw.ac.nz!st1.vuw.ac.nz!panther
Newsgroups: comp.sys.amiga.hardware
Subject: Re: 68030+68040 on A3000: is it possible?
Message-ID: <1991May6.151030.1@st1.vuw.ac.nz>
From: panther@st1.vuw.ac.nz
Date: 6 May 91 15:10:30 +1200
References: <24561@well.sf.ca.us> <15543@life.ai.mit.edu>
Distribution: comp,vuw
Organization: Victoria University of Wellington,  NZ
Nntp-Posting-Host: st3.vuw.ac.nz
Lines: 28

In article <15543@life.ai.mit.edu>, psteffn@pogo.gnu.ai.mit.edu (Paul Steffen) writes:
> "Tweaking" the system software is quite an understatment if you
> were modifying the operating system to run on 2 cpu's.  The closest
> you could probrably get to utilizing two cpu's is to have AmigaDOS
> loaded on both and use some kind of hardware interface [perhaps dual ported
> RAM like Bridgeboard uses] and a PIPE: type device.  It would be running
> like two separate Amigas connected via something like ParNet/SerNet.

Well, how about this as a varient.  Since we now have our famous 'workbench
in a window', it _may_ be possible to patch the DOS 2.0 to kick up two 
workbench windows, one attached to each processor and a segment of memory.
This would be an interesting option.

The other would be to create a 'virtual network' within the machine similar
to the one suggested above, and use a technique that is used on DECnetted
VAXes, and has been used on Acorn BBCs to meld the processing power.

Either way, you have to do a LOT of work-either write a (probably fairly
extensive) OS patch, or a fairly complex hunk of network simulation 
software...

Hmmmm...
Much Luck

Rodger Donaldson			panther@st3.vuw.ac.nz
Run Disclaimer
[CLI SHell2]
Ahh...forget it....