Insider for A1000?
5 messages in this thread
Dean, a question for you: did you ever put together a schematic/et. al. for
Ralph? He said you designed the Insider completely out of your head (wrong
turn of phrase there 8) and never put anything on paper; was that in fact the
case?
Rick
Rick,
Yah, I was out of my head, alright! ;^)
There is no schematic as such, but there is documentation as to how the
board is wired. In fact, in a form that I find easier to use to debug with.
It is true that for a few months there was no paper documentation for the
board, and on occasion, I still repair some boards over the phone while working
from memory.
I know its a bad habit not to document my designs, but I am doing better
these days. I have to, since I went to a CAD design system. I do find it a lot
easier to edit the design while its stored in the grey matter. 8)
-Dean
Dean, have noticed I get a disconnected message on your Novi BBs. Is the
system no longer on?
A while ago I raised the question of why autoboot will not work properly with
the 1.3 ROMs I have replaced in my KwikStart. (I have the older one with 4
ROMs). Have you had any insight into why this happens and how one might get
around it?
Steve
PS. Everything has been working like a charm! Insider, Kwikstart, Cltd
stuff!! Love it.
Steven,
Yes, the Novi Download has been disconnected due to an almost total lack
of use. It had gotten to the point that the usage wasn't worth the cost of the
phone line and the space that it took up.
As for autoboot not working with the 1.3 ROMs on a KwikStart board, I
really don't recall any mention of a problem. (could be me though!) If you
could refresh my memory as to what isn't working properly, I'll try to find out
what's happening. What is it that you're trying to autoboot? If it's RAD, try
not addmeming the 256K of KS mem in.
-Dean
Dean, too summarize. I have tried the following:
1. Booting normally using addmem (the one supplied on Insider disk)
Mounting RAD: and putting the required startup files on RAD:
Remove disk from df0: and warm boot.
The machine automatically defaults to request to insert WB disk.
2. Same procedure as above, but no addmem. Same results as before.
3. Same procedures as above two, but omit using FastMemFirst. Also
same results as before.
4. Same procedures but cold boot with KS 1.3 on disk instead of using
ROM, autoboot from RAD: works as it's supposed.
That's basically what I have experienced, Dean. I had relayed this before
on the Novi board and the response was that you all had NOT tested this with
the ROMs and no one else had reported the problem. It's not really a big deal,
but if it worked that would be nice. I normally move quickly to the hard drive
for the completion of my startup, so I don't do much from the floppy. Again I
am using the older KwikStart with the 4 ROMs and an Insider and Cltd Amega
outboard memory and Cltd Host/Controller.
The addmem does not seem to be contributing to the problem, because the
autoboot fails immediately. That is once you warm boot the RAD: device has
completely disappeared. In a word, it doesn't hang around on warm boots
whether addmem has been used or not. This is true even if you don't try
autobooting. The problem is that the RAD: device doesn't remain in memory at
the moment you warm boot.