Enabling NTFS Support On OSX 10.8.5

Why go to all this trouble when there's a utility from a trusted vendor at a reasonable price? Simply put, I don't trust hacks especially ones like this since it is possible (likely?) that when Apple updates the OS you'd have to go through the entire process again.

The exFAT filesystem is read/write compatible beween OS X and Windows and supports large files (unlike the FATxx filesysems). It is the filesystem of choice for interchange.

Has anyone else used this feature?

Yes, and they sometimes experienced total data loss on the NTFS volume. Do not follow the irresponsible instructions on that page.

I've been through the tricks and third party solutions and have come to the conclusion that you just need to reorganize your existence to cease trying to write to NTFS volumes using OS X. External drives are just too inexpensive to be dealing with this issue anymore.

Third party NTFS-Mac writing support is spotty at best. The next thing you know is that an OS X update "breaks" the usability of the device driver, and by writing, your volume becomes corrupt, and lose your data. Then you wait for the third party entity to catch up, and the File System Implementation Mechanism is no longer maintained by the developer (MacFUSE). So, you wait for OSXFUSE to save you with a current OS X kernel extension, and hope that it continues to function through the next OS X update. Blech!

Use hands4's advice. Use exFAT for your drives that must be cross-usable and never have to worry.

Sorry to hear that. It looks like you cannot have your cake and eat it too. How often will you have files bigger than 4 GB?

exFAT: Read/write on the Mac, supports large files, not Windows 2000 compatible.

NTFS: Read-only on the Mac, supports large files, Windows 2000 compatible.

FAT32: Read/write on the Mac, does not support large files, Windows 2000 compatible.

NTFS will transport form Windows 2000 to the Mac but not the other way.

FAT32 will transport both ways but not for big files (4 GB maximum).

NTFS: Risk a 3rd-party utility that reads and writes NTFS on OS X.

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

See below, use paragon

OR TUXERA for Mac for NTFS:

http://www.tuxera.com/products/tuxera-ntfs-for-mac/

FORMAT TYPES

FAT32 (File Allocation Table)

• Read/Write FAT32 from both native Windows and native Mac OS X.
• Maximum file size: 4GB.
• Maximum volume size: 2TB
• You can use this format if you share the drive between Mac OS X and Windows computers and have no files larger than 4GB.

NTFS (Windows NT File System)

• Read/Write NTFS from native Windows.
• Read only NTFS from native Mac OS X
• To Read/Write/Format NTFS from Mac OS X, here are some alternatives:
  • For Mac OS X 10.4 or later (32 or 64-bit), install Paragon (approx $20) (Best Choice for Lion)
  • Native NTFS support can be enabled in Snow Leopard and Lion, but is not advisable, due to instability.
• AirPort Extreme (802.11n) and Time Capsule do not support NTFS
• Maximum file size: 16 TB
• Maximum volume size: 256TB
• You can use this format if you routinely share a drive with multiple Windows systems.

HFS+ ((((MAC FORMAT)))) (Hierarchical File System, a.k.a. Mac OS Extended (Journaled) Don't use case-sensitive)

• Read/Write HFS+ from native Mac OS X
• Required for Time Machine or Carbon Copy Cloner or SuperDuper! backups of Mac internal hard drive.
• To Read HFS+ (but not Write) from Windows, Install HFSExplorer
• Maximum file size: 8EiB
• Maximum volume size: 8EiB
• You can use this format if you only use the drive with Mac OS X, or use it for backups of your Mac OS X internal drive, or if you only share it with one Windows PC (with MacDrive installed on the PC)

EXFAT (FAT64)

• Supported in Mac OS X only in 10.6.5 or later.
• Not all Windows versions support exFAT.
• exFAT (Extended File Allocation Table)
• AirPort Extreme (802.11n) and Time Capsule do not support exFAT
• Maximum file size: 16 EiB
• Maximum volume size: 64 ZiB
• You can use this format if it is supported by all computers with which you intend to share the drive. See "disadvantages" for details.

reliable fine, good idea. NO

youve got all data in once locus primed for major failure and a tragedy of data loss.

When (not if) your drive goes,....poof, its all gone.

Exercise redundancy above all else and get at least ONE more drive to have a minimum of 2 copies of vital data you "dont dare lose" OFF the computer.

data ON the computer does not count as a copy in the 2-copy scheme of protection.

there are two commercial NTFS drivers, Paragon's NTFS for Mac® OS X, Tuxera NTFS for Mac, and the opensource NTFS-3G.

http://macntfs-3g.blogspot.com/2010/01/ntfs-3g-for-mac-os-x-2010116.html

Data redundancy (copies) makes all HD crashes inconsequential, an irrelevancy.

There are only two kinds of hard drives, those that have failed, and those that will fail, regardless of quality of manufacture.

Any Macbook or desktop should be idealized as a working platform computer system, containing all your applications, documents, and weekly-use necessary files; and all media files such as ‘big-data’ (music/PDF collections/video/pictures), unless directly needed in the near future, should be kept off the computer and on external storage USB or likewise bare hard drives.

Never consider any computer a data storage device at any time under any circumstance, rather a data creation, sending, and manipulation device. Anyone who thinks data is safe on any computer, even copied upon multiple partitions is making a mistake that will, without fail, strike.

SP Forsythe wrote:

I've been through the tricks and third party solutions and have come to the conclusion that you just need to reorganize your existence to cease trying to write to NTFS volumes using OS X. External drives are just too inexpensive to be dealing with this issue anymore.

Absolutely 100% correct, its just short of insanity to keep messing with communication software for reading and writing to HD. 😢

people need to spend $60 on another HD, ...Mac OSX format it and be done with it all.

anything else is masochistic

Linc Davis wrote:

Do not follow the irresponsible instructions on that page.

Claiming irresponsibility in the face of properly mentioned caution demonstrates nothing more than ignorance.

I just noticed youre the author of those several articles Ive seen here and there on various OSX topics.

Greetings Earthling. (waves~) 😊

As for NTFS bi-di communication in the MacOSX,..

the question needs to be raised in the era of 'cheaper than dirt' HD, not "could you" , but "should you".

Of course your article mentions: "If you are dealing with important data, or need to access numerous different NTFS volumes, then third-party drivers may still be the best (if not most convenient) choice."

Id counter with the premise that if said data is more valuable than 'utterly worthless', then dropping another $60 on 1TB is the best choice, rather than a terminal tweak or using the far less than reliable Paragon or Tuxera

I disagree. That stance suggests that the only route to take is to use a third-party solution, or one that is officially supported by Apple. That is not the only route, and with proper precaution, it may be beneficial to some folks to use the hidden NTFS functionality that is built into the OS.

While perhaps one or two people have had problems, I've not at all seen any suggestion that this is a rampant issue, or even one that has affected more than one or two individuals (hardly a statistical significance). Instead, many (most) who have followed those instructions to enable NTFS write support have had perfectly good results.

Is there a chance problems can arise? Sure, when is there ever not?

Suggesting a third-party FUSE options as an alternative is not necessarily a better choice, as this can also result in broken and damaging functionality in the face of OS updates or changes to FUSE or the associated drivers. In fact, along these lines the use of any NTFS-writing option in OS X, be it through FUSE, Apple's hidden NTFS support, or even through a VM, will ultimately be circumventing the OS's native abilities and come with at least some risk.

Even Boot Camp functionality is not supported. Apple offers drivers to get Windows running, but offers no guarantee at all for the ability to read NTFS even in this environment.

The stance some folks take to avoid any modification of the system by any means, and only use it by what Apple intended, is an extreme that is quite odd for anyone besides official Apple support to take.

This stance can be followed by those who choose, but for those who wish to explore their systems (which can be done quite safely) there are plenty of options available, and it is by NO MEANS irresponsible to discuss or outline them, especially with proper warning of consequences. Claiming irresponsibility in this manner is defamatory, plain and simple.

I'd suggest to anyone that if data is valuable, then rely only on redundancy to protect it. If you need to read a drive, then be sure it is backed up (preferibly in multiple locations). Additionally, when using OS X, the most supported formatting option will be HFS+, but even this format has issues with corruption through continuous use. There was discussion of ZFS in OS X to help overcome some of these problems with HFS+. While Journaling has helped, HFS+ still requires continual maintenance through format checking routines (Disk Utility, etc.), as even some of the seemingly more benign actions can result in formatting inconsistencies and other issues.