#GVP PhonePak
11 messages in this thread
Oops – wanted to make clear. PhonePak works in A2000 or A4000 without anything
else, and requires the 16 bit memory mentioned only in the A3000.
Thanks for the clarification regarding PhonePak. I was a little concerned
when you started talking about the extra memory. Thanks for the
information.
– Joe
Paul, are all A2000 (Zorro II?) memory cards 16 bit? I may be able to get an
ooooold memory card from an A2000 cheap, real cheap.
-Jerry
Yes, all A2000 (Zorro II) memory cards are necessarily 16 bit because Zorro II
is 16 bit. Zorro III is 32 bit. If it's an ANCIENT memory card you might be
able to get, make sure it works properly with other cards in a machine. Some
early cards weren't real friendly.
We recommend (of course) either a GVP RAM/8 or a GVP Series II HardCard 8
populated with 2MB for use with PhonePak in an A3000. You actually only need
about 512K for PhonePak to work.
Paul.
Paul, I have a Series II SCSI+ RAM controller and have lost my
documentation. Could you upload a quick jumper config for memory?
-Jonathan
I have a GVP series II ram board with 2megs onboard and another 2 in SIMMs
… and I wouldn't sell it to my worst enemy! So far I've had nothing but
problems because it declares itself as a ram board and a SCSI controller
with 64k ROM although it's only a ram board. That leaves one controller in
the configuration area which doesn't exist in reality!
The problems don't arise until you start using other boards or software
which is resident and tries to change or use the autoconfig lists which
are setup during a bootstrap. I tried asking DTM (GVP's destributors in
Germany) about a solution… but guess what they said… "normally it
shouldn't act up… it only happens with 0.000001% of software… WE HAVE
TESTED IT HERE AND IT WORKS…!" This probably means that eather I got a
dud or they got something that they don't sell with the board. I've tested
the board on an a2000a/b/c so that there's no doubt that it's not the
computer!
I hope that that helps someone out there who might be thinking of buying
one!
Sean
Hi Sean. I'm sorry you're not happy with your Series II, but I really am
unclear as to what the problem is. You say: "because it declares itself as a
ram board and a SCSI controller with 64k ROM although it's only a ram board."
I don't understand this last part since it IS a SCSI controller AND a RAM
board. Perhaps you could explain why this is a problem.
You go on to say "That leaves one controller in the configuration area which
doesn't exist in reality!" But it does exist. What am I missing here?
You say "the problems don't arise until you start using other boards or
software which is resident and tries to change or use the autoconfig lists
which
are setup during a bootstrap." Pray tell, what software needs to worry about
the autoconfig lists at all, and (shudder) changes it? I don't see why this
should ever be a problem.
I really need you to explain what you're trying to do, and then hopefully I can
help. So far, I guess I don't see that the board is performing improperly.
Paul,
Well what I have isn't the SCSI+RAM series II board it's just the RAM
series II board… "NO SCSI!" Which means that it should only declare
itself as such and not as something else aswell.
Just for any experts out there:
Model: A2000-RAM8
MFG CODE 0391
SERIAL *D000909*
RAM INSTALLED = 2MB
So what I'm talking abaout seems to be slightly (not much) different to
what you're talking abaout just that my board thinks that it's a SCSI
board with RAM. Nobody told it that the SCSI was amputated! It's like a
fly without wings… every time it gets to a high spot it jumps off in the
hope of flying………. Shall I say more?
Hmm you're wondering what kind off software patches the autoconfig list.
Well the autoconfig list is patched by any programm which loads the
kickstart into ram to then boot from it (zkick, kickit, skick, etc). There
is also other software which gurus out because of the board.. but I don't
have it anymore as I find it rather anoying removing the board everytime
something doesn't run! Other than that the board is a gift from God! It's
just that I can't use ROM images if I want to run 1.3 or any old ROMs I
have lying around… I can't run a lot of resident modules… My turbo
board has difficulties with it (sometimes) depending on what mode it's
in… and it can't be switched off! As I said … It's really a gift from
the skies :-).
Here's what the SCSI part looks like after a NORMAL boot with just it and
a REAL Masoboshi SCSI controller in my a2000c(68010):
Flags = CDF_CONFIGME
Board Address = e90000
Board Size = 65536
Slot Address = 233
Slot Size = 1
Driver Code at 0
er_Type = d1
er_Product = b
er_Flags = 0
er_Reserved03 = 0
er_Manufacturer = 7e1
er_SerialNumber = eeeeeeee
er_InitDiagVec = 8000
er_Reserved0c = 0
er_Reserved0d = 0
er_Reserved0e = 0
er_Reserved0f = 0
(taken with the EXPANSION tool from C=)
Say "on ara!"
Sean.
Will forward your info to someone at GVP and see if they can figure out a
solution. Sorry for the confusion and your troubles.
Paul, thanks for your help. I got a great deal on a CBM 2052 memory card with
2 meg on it (kind of a gift from a friend). Both the memory card and a GVP
PhonePAK are working fine in my A3000.
Thanks again.
-Jerry Thompson