will not download because there is not enough disk space....

[rednblue_pen]

how come it comes up with this when im saving it to my 200GB hard drive...

how do i fix it?

[Firon]

1) Are you sure you have enough space?

2) Is it FAT32? If it is, dump that outdated crap and convert to NTFS already. You'll not be able to create files larger than 4GB if you don't.

It's probably the latter causing your problem.

[yournotunique]

I'm having this same problem. And yes, the drive I'm saving my file to is FAT32. My boot partition is NTFS, but the file I'm dl'ing is 35GB and I only have 30GB free on that drive.

Anyway, my question is really why can't it (or I) create files larger than 4GB? I can (obviously) save files larger than that on it....

And yes, I'm not necessarily an expert, so go slow. Thanks.

--

Edit

--

I had already fixed it by the time I finished writing the post. At this point I'm wondering why on a slightly more detailed note.

[SledgeDG]

2) Is it FAT32? If it is, dump that outdated crap and convert to NTFS already.

Are you absolutely SURE you really know what you're talking about, buddy?

Or are you just hummin' M$'s marketing rubbish??

Can you back up your statement? (I mean with REAL facts?)

-DG

@yournotunique:

Microsofts implementation of the FAT 32 file system doesn't allow file sizes over 4GB

so just create/convert one Partition to NTFS and you should be all set

[Animorc]

FAT32 doesn't support files that are greater than 4GB, that could be the reason why the "not enough diskspace"-message appears.

Reading tips for the ones who want to compare the two tables:

http://www.ntfs.com/ntfs_vs_fat.htm

http://www.anandtech.com/guides/viewfaq.html?i=63

[chaosblade]

SledgeDG: Are you SURE you are not just another Anti-MS bullshit fanboy? :]

Also notice FAT32 has no 'unicode' filenames per-se. Perheps those torrents DO have unicode characters in them that dont match in your system's codepage and its causing some trouble.

[SledgeDG]

*LOL* listen to you, chaosblade what are you trying to accomplish here?

Are you trying to convince me of MS superiority??? no chance in hell...to much crap for that I have to deal with on a daily base

You play around with your WinXP Home Edition....I play around with 15 servers and close to 200 workstations

I don't try to make up anyone's mind...I just want to know what justifies calling FAT32 crap

And no..I don't have unicode trouble of any kind

-DG

[Firon]

What the hell servers do you use? Absolutely NO Linux server would use FAT32, and modern Windows servers use NTFS. In fact, pretty much all NT OSes used NTFS. 9x systems were never really used as servers or workstations (but pre-NT5 was, mostly as workstations).

FAT32 has UTF-16 support, but it's limited. And by the way, Microsoft made FAT32. And long filename support on FAT.

Let's see...

32KB cluster size for any modern partition size for starters. 4GB (- 1 byte) filesize limit. Absolutely no security. No journaling (nothing like having to scandisk on every hard shutdown). The fact that the FAT is just not that reliable (NTFS's MFT is way more robust). Long filenames are little more than a hack on FAT (fake directory entries). Limited filename length (26 characters). No extents. No sparse files. No native support for alternate data streams, metadata. NTFS has a backup of its partition table at the end of the drive. FAT32 does not. No mount points, various administrative features, hard/symbolic links (yes, NTFS actually supports this)

I could go on and on.

FAT32 is crap for any modern harddisk.

[chaosblade]

Point, Game, Match.