Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!lll-winken!uunet!pdn!boake2!jc3b21!crash
From: crash@jc3b21.UUCP (Frank J. Edwards)
Newsgroups: comp.sys.amiga.tech
Subject: Re: LUCAS Problems with expansion memory
Message-ID: <637@jc3b21.UUCP>
Date: 23 Apr 89 14:29:32 GMT
References: <13417@watdragon.waterloo.edu>
Distribution: comp
Organization: St. Petersburg Jr. College, FL
Lines: 24

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).

Interesting.  The LUCAS board is designed for a 1000, but when a friend
of mine came visiting from Orlando he brought his board and we tried
to install it in a 500 (the 500's cover had to remain off).

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??

I realize this doesn't help your problem at all, but perhaps it'll
lead someone to the cause...

----
Frank "Crash" Edwards
I don't have a cute .signature