Shoutbox

the 135 Gb is a limit that is there due to historical reasons, and other dodgy things that I won't explain now. The fact is that if you don't have (or didn't have) the drivers installed, your disk is a 135 Gb one, so scandisk detects that some indexes are wrong (ie: they're indexes that point to files phisically stored upper from the 135 Gb boundary). In this case, scandisk changes the indexes so they point inside the 135 Gb zone. This makes you see you have 50 Gb used instead of 150.

The files are (may be) still in the disk, i mean, phisically they're still there, however they're in an unknown place, because no index points to them. The only way to recover them is installing the maxor driver again, and using some program like norton undelete or similar (if such tools still exist for ntfs partitions). However I'm not very optimist. Once scandisk has touched your MFT (where indexes are) I don't think you'll be able to recover those files.

About what Kao said about SP1: That may or may not be a possible sollution. I'm not sure.

One thing more: Are you sure your BIOS supports 135+ Gb disks?

And the last thing: I strongly recommend making partitions on disks. The bigger the disk is, the better making partitions is. For example, with a 200 Gb disk, I'd do at least 4 partitions (very probably a couple more) of about 30 - 50 Gb. In that way, you help to reduce fragmentation, keep your files more organized and always have a place where place files before a format on the partition where Windows is installed is made.