From: Jason Green Newsgroups: comp.os.msdos.djgpp Subject: Re: 18-sector limit with biosdisk() Date: Wed, 14 Feb 2001 23:47:52 +0000 Organization: Customer of Energis Squared Lines: 19 Message-ID: References: <3a80a97c$0$96560$272ea4a1 AT news DOT execpc DOT com> <200102070231 DOT VAA23644 AT envy DOT delorie DOT com> <3a88965b$0$96557$272ea4a1 AT news DOT execpc DOT com> NNTP-Posting-Host: modem-177.vanadium.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news7.svr.pol.co.uk 982194463 31659 62.136.22.177 (14 Feb 2001 23:47:43 GMT) NNTP-Posting-Date: 14 Feb 2001 23:47:43 GMT X-Complaints-To: abuse AT theplanet DOT net X-Newsreader: Forte Agent 1.7/32.534 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com NoEmailAds AT execpc DOT com (Chris Giese) wrote: > I have experimenting with boot sectors lately, and I wonder if > it's REALLY the BIOS that makes oversized floppies fail. Maybe a > bootloader fails to patch the maximum sectors-per-track value in > the floppy parameter table (FPT). Or maybe it makes a bad guess > or assumption about the floppy geometry. > > Last time I checked, the built-in loader of Linux (bootsect.S) patches > the FPT, but does NOT support 21 sectors per track. I downloaded Tom's > boot/root disk, and it worked OK. His disk has 21 sectors per track, > 82 tracks, and boots with LILO. Precisely - LILO will load the kernel from an oversize floppy, but the kernel will not boot itself from the same media formatted in the exact same way. If the Linux source shows that oversized floppies are not handled properly then we can safely say that the BIOS is not the culprit.