Message-ID: <011301c300df$fcf7a160$0101bfbf@f9c6f0>
From: "Matthew Smith" <matt AT the-good-stuff DOT freeserve DOT co DOT uk>
To: <djgpp AT delorie DOT com>
References: <b76ti5$fni$1 AT newsg4 DOT svr DOT pol DOT co DOT uk> <b77j3k$abn$1 AT news8 DOT svr DOT pol DOT co DOT uk> <8011-Sat12Apr2003123600+0300-eliz AT elta DOT co DOT il>
Subject: Re: Sector Editor?
Date: Sat, 12 Apr 2003 11:40:48 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

>
> If you can add this functionality to biosdisk without any harm to the
> old functions, please do submit a patch.  If the LBA and the old
> functions contradict, I think a new function is in order.

The biosdisk() API could be used up to the limit of INT_MAX sectors (1TB
drives).  The int 13h extensions can handle 64 bit sector numbers but I
think there are other limits at 1 or 2 TB such as the ATA spec.

The patch would be harmless but I think a new futureproof function is in
order. I'll try both when I've tested the code in the wild.  At current
rates, there will be ATA drives bigger than 1TB around the middle of next
year, and some RAID controllers might already be there.