Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Help with GVP A500-hd+ and new drive

0 views
Skip to first unread message

Mitchell W. Wing

unread,
Feb 14, 1996, 3:00:00 AM2/14/96
to
I have a problem with a new HardDrive, or should I say my system does.
I am running an A500 with a Mega Midget Racer 030 with 8meg 32bit ram,
a GVP impact series II A500-HD+ with 4meg of 16bit ram and a Quantum
LPS240S HardDrive using SCSI ID 0. The 500 has a 1.3 rom, but I am
softkicking 2.05. The system has worked fine in this configuration for
over one year.

I just bought a used Conner 170mb HardDrive through the net. When I
first connected it to my system it tried to boot off of it, but the
new drive had been reformatted before it was sent and had no system
files on it. I then booted from my gvp FaaastPrep disk, the system
booted up until loadwb and then it said I had a read error on drive b,
I have no drive named b. The new drive showed up as empty, but my old
drives three partions did not appear. I tried running FaaastPrep, but
it locked up as soon as I selected Manual installation.

The next thing I did was go to a friends who has a A3000. We set up
the same drive in the same case and fired it up. It came up fine on
his 3000. We used HDToolBox to look at it, It was bootable so we turned
that off because the boot priority was higher than my old drive. It used
SCSI ID 1 and it was formatted with FFS. We than copied some files to
and from the drive. Everything worked fine using his 3000. BTW this
was the third drive for the 3000.

I then brought it home and tried again and got similliar results. So
I started expermenting. I found out I could boot from either drive
but only one at a time. If both are hooked up the system will not
boot. I have had a Sysquest 88 hooked to this system once in the past
and had no problems then.

All help will be appreciated
?
The version of my GVPscsi.device is 4.5.

Chris "Big-Kahuna" Rampson

unread,
Feb 19, 1996, 3:00:00 AM2/19/96
to Mitchell W. Wing

It may be a termination problem. It may be a RDB problem (lastdisk set
on ID=0?).
It may be a cable problem.

--
Owner and wielder of Occam's razor! (Committed to regula philosophandi)

_/_/_/ _/ _/ Chris "Big Kahuna"
Rampson M.S.
_/ _/_/_/ _/ _/_/ _/_/_/ cram...@ford.com
_/ _/ _/ _/_/ _/ _/_/ NO cutdowns, flames or
insults
_/ _/ _/ _/ _/ _/_/ NO such thing as a stupid
question!
_/_/_/ _/ _/ _/ _/ _/_/_/ "NOT an OFFICIAL FORD
spokesperson"

0 new messages