Is 100 gb too much space?

[jray]

Has anyone experienced data corruption using a large drive formatted with no partitions? It has happened twice that I have seen and probably more on a Western Digital 100gb drive. Last time I was told it had an error writing to drive C:, now Windows not boot, scandisk finds a bunch of data and of coarse I end up with files0000.chk. A thorough drive diags checks out fine (twice), I'm wondering if it could be either the cache on the drive, or is that just too much space for Windows to handle? Just wondering if anyone else has had the same sort of problem...

jray

[otheos]

What OS?

[jray]

Originally XP, now 98se.

[Strat]

Any version of Windows below 2K can only recognise a HDD/ HDD partition of less than 136GB. Therefore, this aint your problem.


If you installed XP first onto the hard drive then the filesystem is probably not FAT32.

This means Win98 cannot run. Win98/SE needs a FAT32 filesystem to work.





I personally have a 120GB Maxtor HDD. Never had any problems with it. It has no OS installed on it, it is purely there to store stuff. My 10GB HDD has the OS (Win2K) installed on it.


No problems with either, ever. And the 10GB one is a fair few years old and its only a lil ATA66 ! awwwwwwww

[jray]

Obviously the drive has been fdisk'ed / formatted after XP was on it. Either way, it has problems. The major specs are:

Athlon XP1900
ASUS A7V266-E mobo
(3) 256mb Crucial DDR 266 (768)
Western Digital WD1000 (100gb)

I am also wondering if the CPU may be the issue (oem, not boxed).

[Strat]

My XP was OEM, not boxed. It's fine.


It doesn't sound like a CPU problem to me, but I suppose you could whip it out check it for bent pins & cracks in the core etc, and resit it in the socket........

[Grentarc]

Ahhh... I build computers for a side enterprise... and in my last year i have sent back 6 Western Digital Caviar HDD under warranty... I have sent back 0 Seagate or IBM drives I have installed. I have started replacing the WD's with Seagates as i now trust them WAY more than WD's.... All the WD drives were reporting bad clusters, then corrupted FATs then they were not recognised by the BIOS anymore... they died goodly and properly.... some couldn't even park their heads, so they would knock alot.... anyways.. only one drive i havnt sent back of all the ones i installed... my parents HDD.. but it had bad clusters at one stage too... Anyway, i'll get off my soap box now...

[Kurylo]

Why do you have such problems? HDD has some cache (0.5, 2 or 8 MB). This cache is used to store temporal data. If your PC is being shut down wrong, during your HDD was saving something on it, then this data don't save to HDD, and you have corrupted files.

[Grentarc]

actually with my parents HDD, they never just turned it off, always shut down properly.... the drives i think are just low quality.. or it's just the ones we get in australia :D

[jray]

The cause of the corruption has not been determined, but I'm sure in this case it wasn't due to improper shutdown.


Anyway, I set it up with XP pro on a 4 gig fat32 partition, formatted the rest of the drive NTFS and put the program files over there, so windows doesn't get crowded on C; We'll see how that works....

jray