wangqi Posted October 9, 2019 Share Posted October 9, 2019 Got an issue when trying to download large files with BitComet v1.58. When opening a torrent file and choosing destination directory is says: "The file to be download is larger than 4GB, please modify your destination location to NTFS!". The file system that I am using is MAFS (Microsoft Azure File System) which definitely support files that are larger than 4GB. Since 4GB limitation only exist in legacy file systems such as FAT and FAT32, it would be great if in such case BitComet could check with a "blacklist" and only block FAT and FAT32. For other cloud-base file systems, just let them go. Regards, Qi Link to comment Share on other sites More sharing options...
Rhubarb Posted October 10, 2019 Share Posted October 10, 2019 Azure file system is a cloud based system - NOT a hard drive system. You need to set up your drives to handle NTFS and only uxse Azure for any cloud storage https://docs.microsoft.com/en-us/azure/storage/files/storage-files-faq Link to comment Share on other sites More sharing options...
wangqi Posted October 12, 2019 Author Share Posted October 12, 2019 Hi Rhubarb Thanks for your response. Azure File can be mounted on local windows machine as a hard drive. It works fine when I use BitComet to download files that are less than 4GB to this hard drive. Meanwhile I can copy files larger than 4GB to this hard drive. So it would be great if BitComet can download 4GB files directly to this hard drive:-) Regards, Qi Link to comment Share on other sites More sharing options...
Rhubarb Posted October 12, 2019 Share Posted October 12, 2019 Please try to understand - Azure is NOT designed for local storage - it's for cloud storage. If you feel that it should be able to handle larger files, please take this up with Microsoft. File size limitations are a product of the hard drive file system - not the applications Link to comment Share on other sites More sharing options...
meanie Posted December 28, 2019 Share Posted December 28, 2019 I posted in another thread, but I have the similar issue with a network drive. I agree with OP that Bitcomet should just try to download large files to any drive that's not FAT or FAT32 instead of checking to make sure the location is NTFS. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now