🚀 go-pugleaf

In article <637@jc3b21.UUCP> crash@jc3b21.UUCP (Frank J. Edwards) writes:
>From article <13417@watdragon.waterloo.edu>, by kgschlueter@violet.waterloo.edu (Kevin Schlueter):
>> Myself and a friend are having trouble getting our LUCAS boards to work
>> with expansion memory.  He owns a starboard, I own a "rambo 2" (an
>> autoconfig, external, 2 meg memory box made by a company no longer in
>> business).
>
>The 500 has 1.5MB in an external box (I don't know the manufacturer's
>name) and the same thing happened at boot-up, although the 500 got
>a little bit further:  the WorkBench screen would come up, but when
>we attempted to execute anything, the machine would bomb.  Obviously
>it passed the auto-config stage (this is 1.3), AND was able to read/execute
>the programs in the startup-sequence ... why would it wait until WB
>time to hang-up??

Your two problems are not the same.  Kevin's is probably, as he points out,
happening at auto-config time, or thereabouts.  Actually, it's probably
dying when it tries to do something like enable the cache or check for
the '881 ( I remember reading that this happens right before the workbench
screen comes up ) ...

Your problem is something more like I had.  It is basically one of flakiness.
I built the bus terminator and it bacame quite solid.  As you say, mine
was dying: when I tried to loadwb, when it got a requestor, etc.
Anything that was CHIP-MEM related ( it seemed ).  And always with an
f-line instruction.

Now, it just hangs when I put my Supra on and try to "supramount".  If
I just let the Supra sit (no mount) it will die eventually, with very
wierd errors.

Sigh.

Blair
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Blair MacIntyre, bmacintyre@watsol.{waterloo.edu, UWaterloo.ca}             =
= "Don't be mean ... remember, no matter where you go, there you are." BBanzai=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=