hard drive is 160 gig, but it only finds 33gig!

  • Thread starter Thread starter shackrock
  • Start date Start date
S

shackrock

New member
Any ideas?


It's a samsung: sp01604n.

XPhome recognized it...but there is no letter assigned. I can't find out how to make an FDISK bootable disk either.

under administrative ooptions - computer management, it shows the drive - but says it is 33 GIG, not 160! that's a huge bad thing...haha

what can i do!?!?!?
 
my guess is it wasn't partitioned correctly. are you saying you used FDISK to format your drive? I think when using that it creates one primary partition on the disk. you probably somehow told it to use only 33GB of it. i think the only way to correct it would be to reformat the drive and tell it you want to use the entire thing as one drive.
 
Fdisk asks the question "Do you want to enable large disk management?" or something like that. If you don't answer yes, it won't behave.
 
Check the documentation for the drive in regard to the jumper settings.
If this a multi-drive setup ... be certain that the jumpers are set properly (both at cable select or one at master and one at slave ... if they are on the same IDE channel). Or ... set them both at master and have them each on their own IDE channel.
Some drives offer jumper settings to limit the size of the drive in cases where the BIOS and\or OS don't support large drives.
Operating systems and system BIOS's have separate limitations that are related to specific hard drive capacities that effect how your hard drive will be supported. Verify that your system BIOS supports your new drive.
Some OS's struggle with the 137.4 GB barrier, and cannot recognize capacities greater than that. XP "should" be able to recognize the full capacity provided you have the current Service Packs from Microsoft. In the event that the full capacity is not recognized, you may be able to utilize the full drive be making use of partitions under 137 GB.
Seeing as how you only show 33GB ... Some BIOS's released before June 1999 stall with drives larger than 32 GB and require a BIOS upgrade from the manufacture. If your BIOS recognizes the full capacity, go to Windows Update and look for any patches or service packs.

Hope this helps

-Ken

One other note:
FDISK doesn't recognize drives with the NTFS file structure.
 
you are good crankz...

jumpers were wrong.

turns out I need TWO jumpers, and in different places. and it found it all A-OK. I set it to slave, and my other one (on the same IDE channel) is set to CS still. it seems to work fine. and it's formatted to one huge drive, about 150 gig.

thanks

although, my system seems to be going a BIT slower than usuall...new HD why? also got a new 512 of ram, as well as a video card....
 
Thats a hard call shack...
Systems can slow down for any number of reasons.
Things I would look into ....
Set that primary drive to Master instead of Cable Select
Ensure that DMA is still enabled on that IDE channel
If you are using the NTFS file structure ... turn off indexing
That new memory ... is it additional 512 or all new? If it's additional ... is it matched with what was in there already?
Can't think of much on the new video card that would do anything, yet I ain't really that smart in all areas of computers.
I'm sure you've been around here for a while and know of a lot of the tweaks for DAW purposes, but I'll list a few links for you and\or others that can help in the computing experience.

MusicXP
TweakXP
Black Viper on XP services
 
how can i make sure DMA is enabled?

I turned off indexing, but it seems like that would make it faster...no??

i also changed the other drive to master.

seems to be running significantly faster already, but i'd still like to make sure DMA is enabled.


and yeah, i got most of those tweaks already done for my music stuff, haha.

thanks you all rule. ha.
 
Quote from Black Viper ......
Indexing Service
This service always has been a major resource hog. I NEVER recommend having this service enabled. Remove the function via the "Add / Remove Programs" icon in the control panel (Windows Setup Programs). It uses about 500 K to 2 MB in an idle state, not to mention the amount of memory and CPU resources it takes to INDEX the drives. I have had people (and witnessed it on other people's computers) report to me that the Indexing Service sometimes starts up EVEN while the system is NOT idle... as in the middle of a game. You may feel, as I do, that this is unacceptable. If your computer suddenly seems "sluggish," Indexing Service is usually the cause of it.
................................

DMA ....
Navigate to control panel/system/hardware/device manager .... click the + sign to expand the list for IDE/ATAPI controllers ... double click Primary IDE Channel ... click advanced settings .... in the scroll box for transfer mode, select DMA if available ... under that it will show the current transfer mode. So long as it doesn't say PIO ... all is good.
Do the same for the secondary IDE channel.

-Ken
 
You must log in or register to reply here.
Back
Top