Windows 10: Copying Compressed Files

Greetings,


I would like to use the compact command on my laptop, and then copy the file to an external hard drive. However, the external drive doesn't support NTFS. Will this cause any problems?


I'm using the external drive as a backup, so I wouldn't try to uncompress it on the drive. I think the external drive is using the EXT4 file system. I want to make sure that I can copy a compressed file back to a NTFS drive and uncompress it, if need be.


Thanks,

Shane.

:)

 

Java.nio.file - Copying files

You can't copy a folder, thats why it generates an exception (you are trying to copy a folder using a copy file function).
You probably need to list all the files inside that folder and copy one by one

 

Java.nio.file - Copying files

Issue was the above, so thanks temp02.

 

NTFS Compression of copied files

I'm experiencing an odd issue in Windows 10 that involves copying files that are compressed using the NTFS filesystem to another folder that has the compression flag set (so that when the file is
copied, not moved, it is compressed in the destination folder).

The issue is that when the file is copied to the folder, the filesystem is not releasing the uncompressed copy of the file (as it should) after compressing. Thus, the disk is recognizing that
double the space is needed to store the file (e.g. if the file was 500MB, the remaining capacity for the disk will be 1000MB less). In Windows 7, this behavior is not being seen (i.e. after the file is compressed, the uncompressed file is released,
showing the correct amount of space used.)

I've experienced this on several (actually all) Windows 10 installs, so I'm wondering if anybody else has seen this.

Of course, restarting the computer seems to correct the reported free disk space remaining, but while in a session, I've had to decompress a file manually, then recompress it to have the filesystem report the correct size. The system believes that much more
disk space is being consumed that what is really there, and it is leading to insufficient disk space errors (in testing out the problem, I made a dummy partition and copied the compressed file to it).

I would write this off as a corrupted installation, but I've seen it on good installs also. I've also reported the problem in the Windows feedback community, in case it is an actual bug.

Thanks for any help.