Superman9534
Senior member
I put a 45GB Maxtor drive in my PC today and when I went to install windows 2000 on it, it only says its 32GB. Any idea why this is? What can I do to fix it?
-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
45GB Drive only shows up as 32GB?
- Thread starter Superman9534
- Start date
Superman9534
Senior member
bump
didn't he said that he "went to install win2k on it" if i remember correctly win2k would convert/format it to NTFS by default
since i'm assuming he used NTFS..
the only problem is either the mobo/chipset doen't support it or the bios is outdated...
more info is required........
but you might try flashing your BIOS..
thanx for the reminder Mday
Superman9534
Senior member
I have an ECS K7S5A with what i think is the latest cheepoman BIOS. I'll check and make sure the BIOS sees the full capacity. And it says 32 GB of Unpartioned space (it was in a mac, now its not.)
WinkOsmosis
Banned
Why not just use NTFS??
also, maxtor has several different jumper settings.
I had a similar problem my 46 gig, formatted NTFS, was showing up as a 32.
This guide shows the possible maxtor jumper settings. If you use the settings on the bottom row, it is in "cylider limitation" setting. and it won't dected you whole hard drive. Make sure you have it set in on of the top positions from that page.
I had a similar problem my 46 gig, formatted NTFS, was showing up as a 32.
This guide shows the possible maxtor jumper settings. If you use the settings on the bottom row, it is in "cylider limitation" setting. and it won't dected you whole hard drive. Make sure you have it set in on of the top positions from that page.
AnAndAustin
Platinum Member
😱 I believe there is a faint chance without checking the manu date or chipset of your mobo that it simply can't handle disks bigger than 32GB. IIRC the size limitations were approximately 8GB, 32GB and the next one is 130GB (resolved by ATA133 and most of the newest BIOS'). I don't recall a prog to overcome this but it was probably DOS based anyway (autoexec.bat style), anybody rem these?
😉 Anyway that said it is most likely M$'s hatred for the very compatible (not just older M$ but also alternative OS') FAT32 file system it would like to destroy. I believe Win2000 can format and handle FAT32 partns bigger than 32GB while WinXP has probs esp upon installing WinXP. In any case this is best overcome IMHO by either using NTFS (much better suited to large HDs) or by using multiple partns, a FAT32 partn bigger than 32GB is quite clunky and VERY wasteful due to the insanely large cluster size, best avoided. FAT32 is simply a fudged solution because the original FAT file system couldn't cope with partns bigger than 2GB and even at 2GB it was VERY wasteful.
😉 Anyway that said it is most likely M$'s hatred for the very compatible (not just older M$ but also alternative OS') FAT32 file system it would like to destroy. I believe Win2000 can format and handle FAT32 partns bigger than 32GB while WinXP has probs esp upon installing WinXP. In any case this is best overcome IMHO by either using NTFS (much better suited to large HDs) or by using multiple partns, a FAT32 partn bigger than 32GB is quite clunky and VERY wasteful due to the insanely large cluster size, best avoided. FAT32 is simply a fudged solution because the original FAT file system couldn't cope with partns bigger than 2GB and even at 2GB it was VERY wasteful.
CrazySaint
Platinum Member
Agreed about the jumper limitations. Most HDs have a jumper setting which limits the HD capacity to 32GB because older motherboards can't see any HDs larger than 32GB. I had this problem while trying to install an 80GB HD on my old PII-350 motherboard, the BIOS simply would not recognize the HD until I limited the capacity to 32GB.
CrazySaint
Platinum Member
Right, I meant to say that he needs to check to make sure that his HD has the proper jumper setting (ie, that it isn't set to 32GB mode), not that his motherboard wouldn't support anything over 32GB. Sorry about the confusion 🙂
AnAndAustin
Platinum Member
😉 Yeah cool, I simply wasn't familiar with how modern the ECS K7S5A was off the top of my head and I get sick of having to look up the chipset it uses every time someone neglects to mention this VERY important aspect of their mobo ... not getting on any one in particular here, most people only quote manu and model number .. sigh.
😀 So checking the HD for a limiting jumper is a good start while the next logical step would be to check your OS isn't fluffing you around. I'd still avoid a FAT32 partn bigger than 32GB and either use NTFS or multiple partns, but to each their own I guess.
😀 So checking the HD for a limiting jumper is a good start while the next logical step would be to check your OS isn't fluffing you around. I'd still avoid a FAT32 partn bigger than 32GB and either use NTFS or multiple partns, but to each their own I guess.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
