There is not enough disk space

you might wish to check for compression on the 5GB drive as well as the 28GB. You might want to check the newly formatted drive for errors with scandisk after running fdisk to see if there are other partitions. I had the problem before and it ended up that the new drive was bad, so i'm going about this with a different approach. Hope this at least gives you an idea of what you can do.

I am not an expert on NT4, but I have always been told that it can work with NTFS and FAT16 only. If you use FAT32 partitions, NT4 is not capable of reading them correctly. When you have a multiboot system, I was under the impression that FAT16 was your only option for total portability. Hope I helped.

that could be the limitation of fat32 system under win2k. Microsoft might have limited the filesize for fat32 in win2k. Try NTFS5 and see if the error still occurs.

Yes, this is a new feature designed to be more OS specific and less compatible.

sometimes you can get this error if you are managing your virtual memory pagefile yourself instead of letting windows do it.

NTFS and FAT32 handle things very differently. FAT32 has a larger block size than NTFS so what is 5 GB on a NTFS drive may take up 7 GB or more on a FAT drive. If you add compression to that then this file could be 20+ uncompressed. Unless you needto access the FAT32 drive from any other OS then W2K then I'd upgrade it to NTFS 5.0 This is only in a dual boot not another OS accessing it over a network, or share.

This question was closed by the author