Sender: |
|
Date: |
Tue, 15 Sep 1998 10:44:43 -0800 |
Reply-To: |
|
Content-type: |
text/plain; charset=US-ASCII |
Subject: |
|
From: |
|
Content-transfer-encoding: |
7BIT |
In-Reply-To: |
|
Organization: |
General Magic |
MIME-Version: |
1.0 |
Parts/Attachments: |
|
|
On 14 Sep 98 at 19:00, Lance W. Kephart wrote:
> >Please describe your drive connections: >primary/secondary, master/slave/csel, specific
> >drive models and jumper settings on each
> >drive.
>
> The drive is a Western Digital Cavaiar 34300, jumper is set to
> single for right now.
> The BIOS was flashed, but I'm not sure if I gained anything. It
> originally showed the BIOS as V6.153PA2, but after flashing it
> (using FIC's instructions and BIOS update from their web site)
> it changed to V2.03C700. I haven't done much learning yet when
> it comes to BIOSes, but I thought this kinda strange.
I agree that this is strange; but manufacturers can use whatever
version numbers they like, so it doesn't necessarily mean anything.
[Their page shows the latest as 2.05C800.]
Hmmm... Several of the other PA-20xx boards show version numbers
in the 6.15 region. Any chance that your board is actually not a
-2000, but a -2005 or something like that?
> When I do the auto-detect feature, it reads the drive parameters
> correctly, but shows the drive size as 76MB. Even entering the
> data manually still shows the same results. I have the drive
> installed on a 486/DX2 66 with no problems recognizing it.
I think this is the critical piece.
Some BIOSes have trouble with drives larger than 2.1GB. This
trouble can appear in several ways -- some will show larger drives as
2.1GB, others will report the drive size MODULO 2.1GB. Adding 2.1
and 2.1 and .076, I get 4.276, so I expect that yours is one of the
latter. [This behaviour for a drive bigger than 4.2GB is sort of
reasonable, although I've never actually seen it before.]
David G
-----
**Need help with PCBUILD mailing list? Send an Email to:**
Bob Wright<[log in to unmask]> or Drew Dunn<[log in to unmask]>
|
|
|