You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
In Mac OS X Yosemite I could read and write to NTFS partitions starting the following settings:
1. OSXFuse
2. NTFS-3G
3. Fuse-Wait.
After upgrading to the El Capitan I'm not able to write to NTFS. Is there any solution? Because I tried to reinstall the software and NTFS-3G does not install properly.
MacBook Pro with Retina display, OS X El Capitan (10.11)
André Hottër wrote:
I can not understand Apple such a simple function nowadays is to store data in an HD generates so much head and cost of pain for us users!
There is no other puglin free to install?
Apple has its own file system format. Use that and there isn't any pain. If you need to use the drive on a Windows machine, then you have to deal with the cost and pain.
up to possibly corrupting your OS X installation.
Or losing everything on your NTFS drive by trying to use the Terminal hack in OS X to enable write operations.
"...losing everything on your NTFS drive..."
That as well. It was assumed most folks should be aware of that but, definitely a wrong assumption.
From numerous years of being subjected to the inefficiencies of MS products (lost projects due to unexpected app errors, failure to meet deadlines due to errors -- OS/app freezes, crashes and the list goes on with over 25 years of grievances) I'd probably be more concerned about that, "losing everything on" an NTFS drive due to alleged shortcuts, while in a hurry and failing to back that data up.
Your response lacks any objectivity, the issue at hand is that most computers in the world run a flavor of windows and sometimes you just need to share files between them. OSX being the one with less systems should at least allow for that, as simple as that. Also, in my personal requirement, I need to copy some big video files to play on my Bluray player, but it only supports FAT and NTFS file systems, ExFAT is not an option and so far I haven't found any of the shelf bluray player that supports HFS. So yes I think Apple should add compatibility for that and for Ext3 & Ext4 filesystems so all common Operating Systems can interact with less pain, they charge enough for their under-spec just good looking computers to incorporate that. That is one of the reasons I am seriously considering going back to windows after 20 years with Apple.
Before anything, I know FAT is supported by OSX but the files I am trying to store are 35 and 40Gb each so FAT is not an option.
dfsdfgdsfgfgjhfdhsgfhgjksdfghj wrote:
Your response lacks any objectivity
No, it was specific to the situation posted, and it acknowledged the possible necessity for some people.
They're slowly getting there, but will take years before all software for the Mac is working as Apple is pushing vendors to do.
Support for .3 or .4 character file name extensions came along with Unix with the very first version of OS X, as did basic support for a three button wheel mouse. However, just coming from OS 9, Apple couldn't just do a full switch to a Windows style OS. All Mac apps and files used Type and Creator codes in the resource to signify what they were to the system. You couldn't just toss those out without making every Mac user out there flaming mad.
In Snow Leopard, Apple officially dropped Type and Creator codes and vendors were supposed to start using file name extensions. They're also supposed to use Uniform Type Identifiers to avoid the Windows issue of a specific extension being stuck to only one app. In Windows, an .eps file can only be assigned to one app, no matter which of multiple apps it may have come from. Output an .eps from Photoshop? Too bad, it's still going to open in Illustrator when you double click it if Illustrator is what you assigned .eps to. With Uniform Type Identifiers, an .eps saved from Photoshop will open in Photoshop, or whichever app created it despite all of them using .eps as the extension. Though you can screw that up yourself by assigning a file type to a specific app. Then OS X will open any file with that extension in the app you chose. You can also reset the file association database if you want to, or need to.
Anyway, Apple appears to be working towards a single fork system. They had to shoehorn in a dual fork system for OS X in the first place since Unix itself doesn't support it. With the original release of the CC apps from Adobe, they no longer save a resource fork with any files. That at Apple's own request as the resource fork itself has been deprecated. So expect as some point in the future for the dual fork file system Apple has always used to someday disappear. For now, it will still recognize and read Type and Creator codes if the file has no extension. But that will also break the day Apple goes to a single fork system.
Free solution: Installing the combination of Fuse, NTFS-3G and Fuse-wait. However, NTFS-3G has many cons:
- Complicated installation
- Commonly face a nightmare error of "NTFS-3G could not mount"
- Read/write speed to NTFS partition is not similar to native HFS+
- Limited to accessing to big number of files and large volume of Data
- Does not support completely all NTFS versions
- No functions to create, verify and repair NTFS partitions
- Operations on SSDs is not optimized
To avoid potential error, I strongly recommend installing NTFS-3G using command lines through Terminal.
Paid NTFS drivers: There are only 2 applications: Paragon NTFS 14 and Tuxera NTFS 2015
For more information, look at the comparison table here Paragon NTFS 14 vs Tuxera 2015 vs NTFS-3G.
Yup, I already know about these. Good information though for those who don't.
NTFS-3G was actually maintained by Tuxera as an open source NTFS add on. I purposely never mention the older NTFS-3G as an option anymore because, as the link shows, it no longer works well. You'd have to go back to Snow Leopard or older for it to be useful.
This is pretty annoying how the "World's Best Operating System" cannot write to one of the most common file systems out there. I understand that Apple wants to be a snob and push people to use hfs partitions, which is fine.
Lacking basic NTFS write support only makes me want to go back to using Linux and Windows.
Buy yourself a PC, then you won't suffer from Apples 'failings'.
And remember that if you used a PC no other file systems will work, it's that flexible.
And the world's most used OS can't write to an Apple formatted drive, OR even read one! What snobs those folks are at Microsoft.
Apple doesn't license HFS to anyone, just as MS doesn't license NTFS to anyone. Apple at least took the time to figure out how to read an NTFS drive. Though that ability may have come along with BSD Unix OS X sits on top of.
But regardless, nice of you to complain about Apple not doing something that MS doesn't, either.
If someone is still using a pre OS X El Capitan, Paragon NTFS for Mac is free for personal use.
Get it here http://www.paragon-software.com/home/ntfs-mac-yosemite/
And the best advice to folks who think this way ("...makes me want to go back to using Linux and Windows...") is to go back to Windows, since those thoughts strongly imply that they have selected the wrong operating system entirely.
We switched over to Apple more than 9 years ago, after being subjected to the most inefficient operating systems and applications from an arrogant company for more than 20 years (20 years of pure administrative agony and torture) and wouldn't trade that 9 years of productivity for anything. As vendors in enterprise networked office systems, we unfortunately were forced to inherit the burden of resolving Windows issues (again, enterprise level) all too frequently (almost every major corporate installation), since Windows refused to acknowledge that their OSs, apps or platforms could be the culprits.
Further, it is Microsoft who is the "unfriendly" organization with its aging, dinosauric NTFS file system (23 years ancient; 30+ years considering that the NT system bowered most of its features from OS/2) , a proprietary system. Even mounting newer NTFS volumes in older Windows versions (and visa versa obviously) is a convoluted, time consuming and extremely cumbersome process at best. Additionally, the new file system MS began working on more than 4 years ago, ReFS, intended to resolve many of the well-hidden (from the general public) reliability, management, compatibility, etc issues is in fact encountering more and more issues as MS attempts to develop that system (near maximum disk capacity resulting in massive failures, possibly very serious disk redundancy conversion issues, unrecoverable/repairable ReFS failures and the list goes on).
No, the advantage of having full compatibility on OS X with an ancient, problematic and unreliable file system, NTFS, is FAR outweighed by the amazing productivity we (and our clients) have attained since leaving, running away from MS.
Again, the best advice we can offer to those who question the administrative and productive viabilities of Apple's OS is to either stay with MS or go back to MS. If those thoughts of abandoning OS X for Multiple Sclerosis ("Windowless") are even faint echos in Apple users' minds, then they have chosen the wrong company, an entirely wrong OS. If there's a slight hint of bitterness in these comments toward Microsoft, well, after more than 30 year of abuse, yeah, there's probably a great deal of pent up bitterness and hostility, considering the extensive, profusive loss in productivity and being forced to compensate for Microsoft's known issues (incompatible, unreliable, very fragile OSs, apps and file systems all the way up through large corporate enterprise).
Excellent thoughts, DRailroad.
Sounds like you would already know this, but MS has created their own very deep hole by trying to continue backward support for even DOS programs that are over 30 years old. eWeek covers lots of computer related topics, mostly towards the business end. They noted a couple of years ago that some very large, important firms still use custom software written for them decades ago as DOS apps. The hardware gets replaced at the desks of the users who need to access that app, so the need to continue to have an OS that will run it on the new computer remains. These companies have a lot of clout with MS because they each have multiple thousand seat licenses for Windows. As such, they can demand that new versions of Windows do not break their ability to use this old software. Why? Because getting it rewritten as an up-to-date Windows app, which would also require translating the massive amounts of data would cost millions of dollars in development time, testing, and down time.
A local furniture store chain had that same kind of setup. Everything nice and modern about the place except for the 286 and 386 DOS PCs at every service/order desk. We're talking old. Computers where the once light beige plastic monitor and computer chassis' were now a puke yellow. They used this system up until just a year or so ago. Either they were running out of old computers they could find to replace ones that died, or they just didn't like how backwards it made the organization appear, but they finally updated their ordering system to an all new Windows app and replaced their relic hardware with new computers.
I've read about that issue with NTFS a few times. One article suggested MS does it on purpose to make it harder for third party vendors to reverse engineer it. They think they have it, and MS changes NTFS again. Personally, I would thing MS changes NTFS to make it more efficient where they can, and to fix bugs that had gone unnoticed. Sounds more logical to me anyway than the conspiracy theory approach.
I still use Windows where necessary (very little, but still some need). I liked Windows 7 and think Windows 10 is pretty nice (the new Edge browser definitely needs work yet). But then MS occasionally reminds me why I try to avoid Windows. We were trying to install the demo of a 3D modeling app for testing. Wouldn't install under Windows 10 as the pull installer kept saying it couldn't find the remote server. The vendor says the paid app will run under Windows 10, but not the demo. Use Windows 7 or 8. Okay, so I wiped a laptop (after backing it up) that had Win 10 on it and installed Win 7, which it came with, from scratch. Per a very common and known issue with Windows 7, everything goes smoothly until after the SP1 update is done applying. It then forces you to update the updater before it will go any further. As soon as you do that, Windows Update stops working. It just spins forever looking for updates without ever finding anything. Called MS. To their credit, they did spends hours trying to figure out why Win 7 wouldn't update, including much time via remote access. They finally said they would do whatever it took to fix it for a one time fee of $99. I said, "Are you frickin' kidding? You want me to pay to fix an issue your own software created?" I hung up on them. After searching for hours, I finally found a user posted fix that actually worked.
Enable NTFS Write support on Mac OS X El Capitan
