glee
Sun Jun 01 08:26:06 PDT 2008
Some Award BIOS v.4.51 and older had the issue....usually a BIOS update will fix it.
The fix was added to updates after May 1999. I've got the updated BIOS file for my
machine with the issue, but have never installed it because the largest drive I have
for it is 30GB.
32GB 63 Sector Limit
http://www.allensmith.net/Storage/HDDlimit/63Sector.htm
http://support.ontrack.com/cgi-bin/ontrack.cfg/php/enduser/std_adp.php?p_faqid=77
http://www.pcreview.co.uk/forums/thread-1940681.php
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm
"Brian A." <gonefish'n@afarawaylake> wrote in message
news:OTMDea$wIHA.1936@TK2MSFTNGP04.phx.gbl...
> I sit corrected, the 32 GB limit was for Win95/98 and the fix wasn't FDISK, it
> was for the protected mode IDE driver Esdi_ 506. I'll agree that much older
> boards that didn't support LBA would be subject to the limit, although a board
> from '98 I would think should. The Matsonic mobo I have had an Award BIOS circa
> '94 which has been updated to '99 and supports LBA.
>
> --
>
>
> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> Conflicts start where information lacks.
>
http://basconotw.mvps.org/
>
> Suggested posting do's/don'ts:
http://dts-l.com/goodpost.htm
> How to ask a question:
http://support.microsoft.com/kb/555375
>
>
> "glee" <glee29@spamindspring.com> wrote in message
> news:%23gz%23I6%23wIHA.516@TK2MSFTNGP04.phx.gbl...
>> How do you figure? If it's an older system, it could very well have a 32GB limit
>> imposed by the BIOS....that has nothing to do with FDISK. I have a system here
>> from 1998 that has a 32GB limit....it was an Award BIOS bug.
>>
>> There was no FDISK update for a 32GB limit in FDISK, that I recall. There was an
>> update for a ~64GB limit of the program. Please provide a link to a 32GB limit
>> in FDISK. You must be thinking of XP, which has a 32GB limit for formatting with
>> FAT32.
>> --
>> Glen Ventura, MS MVP Shell/User, A+
>>
http://dts-l.net/
>>
http://dts-l.net/goodpost.htm
>>
>> "Brian A." <gonefish'n@afarawaylake> wrote in message
>> news:ONmQip8wIHA.1504@TK2MSFTNGP05.phx.gbl...
>>> IIRC the mobo wouldn't be the limit problem, the version of FDISK would be,
>>> however if EZ-BIOS was installed, also IIRC it's not easy to get rid of. MS
>>> put out an updated FDISK that dealt with the 32 GB limit and 64 GB limit. I
>>> have an old board from 1994 where I installed the 64 GB FDISK and haven't had
>>> any issue. Had I not installed it I would have had to install the drive overlay
>>> EZ-BIOS.
>>>
>>> --
>>>
>>>
>>> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
>>> Conflicts start where information lacks.
>>>
http://basconotw.mvps.org/
>>>
>>> Suggested posting do's/don'ts:
http://dts-l.com/goodpost.htm
>>> How to ask a question:
http://support.microsoft.com/kb/555375
>>>
>>>
>>> "MEB" <meb@not here@hotmail.com> wrote in message
>>> news:OJ6YqK8wIHA.4376@TK2MSFTNGP06.phx.gbl...
>>>> Uhm, better find out what motherboard/make/model motherboard/computer first
>>>> [old board].... If Ez-Bios [old drive overlay program] was installed there
>>>> MAY be an actual BIOS limitation...
>>>> Seagate called it Disk Wizard, Quantum called it Disk Go, Maxtor called it
>>>> MaxBlast, etc....all are basically the same thing, check for BIOS
>>>> limitation, installs drive overlay.
>>>>
>>>> Poster might try first scandisking in DOS to check the drive/partitions for
>>>> errors.
>>>>
>>>> Check the EZ-Bios utility to see if it has tools to check the drive with
>>>> [don't remember].
>>>>
>>>> --
>>>> MEB
http://peoplescounsel.orgfree.com
>>>> --
>>>> _________
>>>>
>>>> "Brian A." <gonefish'n@afarawaylake> wrote in message
>>>> news:uB$pK87wIHA.5832@TK2MSFTNGP02.phx.gbl...
>>>> | You don't have to be using EZ-BIOS, updating FDISK would take care of
>>>> the
>>>> | drive limit.
>>>> | Fdisk Does Not Recognize Full Size of Hard Disks Larger than 64 GB
>>>> |
http://support.microsoft.com/default.aspx?scid=kb;en-us;263044
>>>> |
>>>> | Also, you may want to try running defrag in Safe Mode. Safe Mode loads
>>>> the
>>>> | minimum drivers/software needed to run Windows.
>>>> |
>>>> |
>>>> | --
>>>> |
>>>> |
>>>> | Brian A. Sesko { MS MVP_Windows Desktop User Experience }
>>>> | Conflicts start where information lacks.
>>>> |
http://basconotw.mvps.org/
>>>> |
>>>> | Suggested posting do's/don'ts:
http://dts-l.com/goodpost.htm
>>>> | How to ask a question:
http://support.microsoft.com/kb/555375
>>>> |
>>>> |
>>>> | "SomeOne" <SomeOne@Example.Com> wrote in message
>>>> | news:TGs0k.120$js1.95@newsfe24.lga...
>>>> | > Please excuse. I am not sure if I am in the proper newsgroup. I am
>>>> | > shotgunning this to every Win98 newsgroup that I am coming across.
>>>> | >
>>>> | > I have tried looking this up on the new, but the only thing that it
>>>> relates
>>>> | > to is WinME
>>>> | >
>>>> | > I have an old system that I uses for subscription mail.
>>>> | >
>>>> | > I had about 100MB mem w/Win98SE
>>>> | >
>>>> | > Due to the age of the mother board, I have to use something called EZ
>>>> Bios
>>>> | > as I am running a hard drive that is greater than 32 gig.
>>>> | >
>>>> | > I have two hard drives. Drive C, E, and F are logical drive and Drive D
>>>> is
>>>> | > a single 4 Gig hard driv. Problem is this. I keep getting messages from
>>>> | > Norton stating that Drive C is heavily fragmented (over 82%) and needs
>>>> to
>>>> | > have defrag run on it. When I try and run any of the following
>>>> software;
>>>> | > Norton Disk Doctor, Optimization Wizard, Speed Disk, Win98 Scan Disk or
>>>> | > Win98 Disk Defrag, I get the following message "Unable to operate on
>>>> Drive C
>>>> | > because it is in use by unknown disk utility. Please close unknown disk
>>>> | > utility to operate on Drive C".
>>>> | >
>>>> | > Now I use Drive C as my system drive and I put nothing on the drive
>>>> | > directly. When I try and install, I try and have everything go to Drive
>>>> E;
>>>> | > however, sometimes software does not give me that option.
>>>> | >
>>>> | > I have turned off everything that I can find. Have to be careful if I
>>>> boot
>>>> | > in DOS and try this as I am not sure of the EZ Bios would be working and
>>>> I
>>>> | > do not want to screw up Drive C (Defrag might not see complete Drive C,
>>>> etc)
>>>> | >
>>>> | > I would appreciate any and all help. One thing, I really would prefer
>>>> not
>>>> | > to have to reformat Drive C. Drive C is 7.3 Gig with 5.6 Gig free.
>>>> | >
>>>> | > Thanks in advance
>>>> | >
>>>> | > SomeOne
>>>> | >
>>>> | >
>>>> | >
>>>> |
>>>>
>>>>
>>>
>>
>>
>