This message is from the T13 list server.

Michael,

I believe the Phoenix BIOS that supports 48-bit LBA devices correctly reports the 
drive size in INT13 FN48.  I will double check this though.  I wll also look at what 
EDD3.0 specifies and give my feedback to either the reflector or Curtis directly.

> Gary Laatsch
> Principal Engineer
> Phoenix Technologies Ltd.
> 949-790-2107
> [EMAIL PROTECTED]
> 
> "If you are going through hell, keep going." 
>      - Sir Winston Churchill (1874-1965) 
> 
> 



-----Original Message-----
From: Curtis Stevens [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 09, 2002 3:29 PM
To: 'Eschmann, Michael K'; ATA (E-mail)
Subject: RE: [t13] Who owns EDD3? and related 48bit drive concerns


This message is from the T13 list server.


I am the EDD-3 owner.  There are several BIOS vendors that have provided
input to the EDD series.  T13 has been that forum in the past.  Usually, it
takes a customer request to get new things into the BIOS in a consistent
way...

-----------------------
Curtis E. Stevens
Pacific Digital Corp.
2052 Alton Parkway
Irvine, CA 92606

Phone (949) 477-5713
Fax (949) 252-9397

E-Mail: [EMAIL PROTECTED]
WEB: www.PacificDigital.com 

Remember, it is easier to get into something than to get out of it.

-----Original Message-----
From: Eschmann, Michael K [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 09, 2002 3:19 PM
To: ATA (E-mail)
Subject: [t13] Who owns EDD3? and related 48bit drive concerns


This message is from the T13 list server.


Since Curtis Stevens moseyed from Phoenix to PD, who officially owns editing
of the EDD3 spec?

To get down to brass tacks, I've been getting calls about support for 48-bit
LBA in OS's that require the Int13 Fn48 call to return back the correct size
for a drive larger than 128GB (0x0FFFFFFF sectors) in order to use the
entire disk, and I'd like to see something in the BIOS that can help these
folks who are having problems.

Since there is currently no way an end-user can do to determine if a BIOS
can handle these new large drives without buying one (then finding out you
either have to chase down a new BIOS or return the new drive), I'd say this
is not a very nice thing to do to an unsuspecting end-user.  Oh, yes, the
customer could track down the BIOS and find out first if the BIOS is
capable, but how many people are gonna do that when they are drooling over a
big drive at a store and they have their visa(tm) card in their hand?

So, what do we gotta do to get a flag in the BIOS to indicate it can handle
one of these large drives?

MKE.

 

Reply via email to