NTFS for Mac OS X breaks down the barriers between Windows and Mac OS X. Effectively solves the communication problems between the Mac system and NTFS, providing full read and write access to Windows NTFS partitions under Mac OS X. Excellent solution for end users, SOHO and Enterprise, supports all NTFS versions from Windows NT 3.1 to Windows Vista (NTFS versions 1.2, 3.0 and 3.1) and mounts the NTFS volumes as native ones.
NTFS for Mac OS X allows you to:
Natively read and write your data to any Windows NTFS partition.
Notice to version numbers. 8.0, 9.0. This company never try to fix anything with their software. I have reported some finding to them, they said that they will fix them and closed the cases but none of them fixed. Instead, they released a new version. I do not believe that there's anything new with this version, because NTFS is NTFS. New versions are to want more money from their old customers. If you pay an upgrade price for a new version, later they starts to sell the new version for the upgrade price you paid.
This software is dangerous! My bootcamp volume corrupted many many times and I had to repair it. If you report these kind of problem to their tech support, they suggest you to repair the disk with Disk Utility. Why would I have to repair my NTFS volume every time?
I uninstalled it. Dangerous software and poor support. That's it!
I recently bought a copy and had a problem so I tried to contact them but they don't even list their support email address at their corporate website! Or at least they don't advertise it well, as I couldn't find it there.
So I contacted them via their web support form but am yet to receive any replies from them after more than a week.
The NTFS driver itself seems to work well; my problem was that it didn't work at all with anything other than the Finder. It seems that it was because the volume name of the NTFS partition was not in plain ASCII (mine was in Korean.) After I renamed it in English, everything seems to work fine.
I should revise my review. A few days after I wrote the above review, they contacted me and they do seem to have a proper support process, but seem to have been very busy rolling out the new release (9.0).
So please disregard the 'unresponsive' part above.
NTFS for Mac transfers files between Snow Leopard and NTFS-formatted external hard drives perfectly fine. In fact, I think it does a very good job of it.
However, users planning to use this to access a Boot Camp partition, beware!
When I have tried moving something from the Windows partition to the mac partition (which I have done 3 times), I often get strange errors like "-36". Sometimes it takes a few errors, in the most recent incident it only took one, but the common result is an unbootable Windows partition with at least a corrupted registry.
Strangely enough, after the NTFS partition is rendered unbootable, I can copy files from it onto my mac partition just fine. Ironically, that is just what I am doing right now, saving my personal documents before I am forced to reinstall Windows.
Conclusion? This works awesome with external hard drives. Never once have I gotten an error of any kind. But if you want to use this with your Windows for Boot Camp, you might be in for a lot of pain.
Edit: I've actually moved stuff from the windows to mac partition a lot more than 3 times, in fact, its probably somewhere in the 20s.
3 times is the number of times my Windows partition has been corrupted because of this piece of software. Fortunately, it totally avoidable if you don't try to move files to and from said partition.
I tried this software on my iMac and all went good, fast read/write documents from/to BOOTCAMP partition except for a thing:
DiskUtility and Diskwarrior found a critical error on ".coldrush" file in usr/bin?/... (I don't remember the exactly location of it) that cannot be repaired.
When the trial ended I removed ParagonNTFS 8 but the error still exist, so I found and removed it manually, after a restart everything was okay.
Please developers, fix that issue 'cuz is a bit sad that you find an error that couldn't be repaired. Thanks.
In every aspect, this software is far better than Tuxera NTFS.
- It's above all much faster
- It's more reliable and easier to use
- Better features
- No error messages like -36 and no file write permission error which I have encountered with Tuxera NTFS
Own and use the most recent versions of NTFS for Mac and the companion HFS+ for Windows. Use on OSX 10.6.5 and Win7. As others have noted, stability and data transfer corruption issues seem to have been addressed since version 8.0.
When writing to esata or 1394B external volumes via HFS+ for Windows, I am definitely not getting native HFS+ speeds - I would estimate 40% slower - but better than MacDrive.
Have experienced periodic BSODs under Win7 due to the HFS+ for Windows driver. Not often enough to make me give up on it.
If you only wish to read an HFS+ volume under Windows, there is a free option here: http://hints.macworld.com/article.php?story=20101112214346176
I moved from Windows Vista to Macbook Pro and have a home network of Windows Machines and USB storage drives formatted as NTFS used for sharing and backups. I had several programs that would only run under Windows so Installed Vista (later Windows 7) under Bootcamp.
Being somewhat naive about Mac, I didn't find the free NTFS nor become aware of the virtual machine (VM) options for MAC like VMware and Parallels (I tried Oracle/Sun's free VM but it was much too technical for me). Here's my experience with NTFS for Mac and the companion HFS for Windows.
1. HFS for Windows does not support encrypted Mac disks. If you select Filevault (may have been the Mac default), the Mac disks from Windows show up as Bands and you can't read them from Windows.
2. Both NTFS for MAC and HFS for Windows are disabled when running under a virtual machine, and the functions they perform are provided by the 2 VM's I tested, but only when those VM's and virtual OS (Windows) are running.
3. However, NTFS for MAC will give you read/write access when you don't want to boot up or allocate the resources for a VM, for example, just to access an external USB Drive or a file under the VM (Or Bootcamp). Running the VM, even on dual 2.53GHZ processors and 4GB of memory, is resource intensive. You have the usual slow boot and shutdown times of Windows and MACOS slows down noticeably and Windows is often very slow. (D) not to install HFS for Windows under a VM, only under Bootcamp.
4. Paragon's Tech support says installing HFS for WIndows under the VM can cause a BSOD (Windows Blue Screen of Death). I installed it under Bootcamp, then installed the VM and didn't see this problem.
5. Paragon tech support can be slow to respond, they provide only e-mail support for free for a very limited time (though they did respond beyond that timeframe for an issue opened in the timeframe) and there are occasionally minor language issues.
6. Paragon's refund policy is a short 30 days after purchase, so if you encounter a problem like I did, you may have to ask for a refund first and then perhaps work the issue with tech support in parallel. I asked for an extension of the refund window given the lack of warning in marketing materials about two common conditions (use of a VM and encryption of MAC disks), but they repeatedly refused.
7. I asked Paragon to post items 1-4 on their marketing materials so customers are not surprised, but haven't got confirmation yet that they will do it.
8. I did not have any stability problems with the software. I didn't measure the performance but it didn't notice any delays vs. native access or from a VM.
9. The instructions for installing HFS for Windows (Read only) weren't very clear. Despite re-reading the doc and help files I had to contact technical support to figure it out.
I've noticed a few issues relating to Paragon's NTFS for Mac and I just wanted to share them.
(1) Incompatible with VMware Fusion: In order to run VMware Fusion I have to go to Disk Utility and unmount the volume before I can run it.
(2) Safari Download Issue: When attempting to download a file via Safari, if the NTFS volume is mounted on the desktop the Safari will hang for about 15 seconds before it continues the download normally.
(3) Name In Finder: Though the volume's name is "Mimmic" both in Disk Utility and in Windows, it's mounted as "Mimmic 1" and no amount of changing on my part can fix this. It will change temporarily but the next time I mount the volume it will be "Mimmic 1" all over again.
(4) Finder Eject: I cannot unmount the volume by key command or dragging to the trash, I have to unmount it via Disk Utility.
It's a good little utility and once these issues are ironed out it'll be an invaluable piece of software.
Please login or create a new MacUpdate Member account to use this feature
Watch Lists are available to MacUpdate Desktop Members Upgrade Now
Download and auto-install
using MacUpdate Desktop. Save
time moving folders and cleaning-up.
NTFS for Mac OS X breaks down the barriers between Windows and Mac OS X. Effectively solves the communication problems between the Mac system and NTFS, providing full read and write access to Windows NTFS partitions under Mac OS X. Excellent solution for end users, SOHO and Enterprise, supports all NTFS versions from Windows NT 3.1 to Windows Vista (NTFS versions 1.2, 3.0 and 3.1) and mounts the NTFS volumes as native ones.
NTFS for Mac OS X allows you to:
Natively read and write your data to any Windows NTFS partition.
Easily transfer data between Windows and Mac computers using external or thumb drives with NTFS partitions.
Access NTFS partitions without having any complex translation applications or file services like AFP or Samba protocols.
hobaid reviewed on 17 Jan 2012
+1
2y2d reviewed on 30 Sep 2011
http://dl.paragon-software.com/demo/ntfsmac_trial.dmg
-1
-1
Watmor reviewed on 17 Jun 2011
+6
+35
This software is dangerous! My bootcamp volume corrupted many many times and I had to repair it. If you report these kind of problem to their tech support, they suggest you to repair the disk with Disk Utility. Why would I have to repair my NTFS volume every time?
I uninstalled it. Dangerous software and poor support. That's it!
+1
+6
Lvalue reviewed on 03 May 2011
I recently bought a copy and had a problem so I tried to contact them but they don't even list their support email address at their corporate website! Or at least they don't advertise it well, as I couldn't find it there.
So I contacted them via their web support form but am yet to receive any replies from them after more than a week.
The NTFS driver itself seems to work well; my problem was that it didn't work at all with anything other than the Finder. It seems that it was because the volume name of the NTFS partition was not in plain ASCII (mine was in Korean.) After I renamed it in English, everything seems to work fine.
+1
+6
So please disregard the 'unresponsive' part above.
+2
+5
Atlasica reviewed on 30 Mar 2011
However, users planning to use this to access a Boot Camp partition, beware!
When I have tried moving something from the Windows partition to the mac partition (which I have done 3 times), I often get strange errors like "-36". Sometimes it takes a few errors, in the most recent incident it only took one, but the common result is an unbootable Windows partition with at least a corrupted registry.
Strangely enough, after the NTFS partition is rendered unbootable, I can copy files from it onto my mac partition just fine. Ironically, that is just what I am doing right now, saving my personal documents before I am forced to reinstall Windows.
Conclusion? This works awesome with external hard drives. Never once have I gotten an error of any kind. But if you want to use this with your Windows for Boot Camp, you might be in for a lot of pain.
+1
+5
3 times is the number of times my Windows partition has been corrupted because of this piece of software. Fortunately, it totally avoidable if you don't try to move files to and from said partition.
+72
greatwave reviewed on 17 Mar 2011
DiskUtility and Diskwarrior found a critical error on ".coldrush" file in usr/bin?/... (I don't remember the exactly location of it) that cannot be repaired.
When the trial ended I removed ParagonNTFS 8 but the error still exist, so I found and removed it manually, after a restart everything was okay.
Please developers, fix that issue 'cuz is a bit sad that you find an error that couldn't be repaired. Thanks.
+3
-10
Josdans reviewed on 11 Jan 2011
- It's above all much faster
- It's more reliable and easier to use
- Better features
- No error messages like -36 and no file write permission error which I have encountered with Tuxera NTFS
+1
+10
Dhess01 reviewed on 16 Nov 2010
When writing to esata or 1394B external volumes via HFS+ for Windows, I am definitely not getting native HFS+ speeds - I would estimate 40% slower - but better than MacDrive.
Have experienced periodic BSODs under Win7 due to the HFS+ for Windows driver. Not often enough to make me give up on it.
If you only wish to read an HFS+ volume under Windows, there is a free option here: http://hints.macworld.com/article.php?story=20101112214346176
+2
+2
Pc2mac reviewed on 07 Oct 2010
Being somewhat naive about Mac, I didn't find the free NTFS nor become aware of the virtual machine (VM) options for MAC like VMware and Parallels (I tried Oracle/Sun's free VM but it was much too technical for me). Here's my experience with NTFS for Mac and the companion HFS for Windows.
1. HFS for Windows does not support encrypted Mac disks. If you select Filevault (may have been the Mac default), the Mac disks from Windows show up as Bands and you can't read them from Windows.
2. Both NTFS for MAC and HFS for Windows are disabled when running under a virtual machine, and the functions they perform are provided by the 2 VM's I tested, but only when those VM's and virtual OS (Windows) are running.
3. However, NTFS for MAC will give you read/write access when you don't want to boot up or allocate the resources for a VM, for example, just to access an external USB Drive or a file under the VM (Or Bootcamp). Running the VM, even on dual 2.53GHZ processors and 4GB of memory, is resource intensive. You have the usual slow boot and shutdown times of Windows and MACOS slows down noticeably and Windows is often very slow. (D) not to install HFS for Windows under a VM, only under Bootcamp.
4. Paragon's Tech support says installing HFS for WIndows under the VM can cause a BSOD (Windows Blue Screen of Death). I installed it under Bootcamp, then installed the VM and didn't see this problem.
5. Paragon tech support can be slow to respond, they provide only e-mail support for free for a very limited time (though they did respond beyond that timeframe for an issue opened in the timeframe) and there are occasionally minor language issues.
6. Paragon's refund policy is a short 30 days after purchase, so if you encounter a problem like I did, you may have to ask for a refund first and then perhaps work the issue with tech support in parallel. I asked for an extension of the refund window given the lack of warning in marketing materials about two common conditions (use of a VM and encryption of MAC disks), but they repeatedly refused.
7. I asked Paragon to post items 1-4 on their marketing materials so customers are not surprised, but haven't got confirmation yet that they will do it.
8. I did not have any stability problems with the software. I didn't measure the performance but it didn't notice any delays vs. native access or from a VM.
9. The instructions for installing HFS for Windows (Read only) weren't very clear. Despite re-reading the doc and help files I had to contact technical support to figure it out.
+4
+49
Thanks
+1
+125
(1) Incompatible with VMware Fusion: In order to run VMware Fusion I have to go to Disk Utility and unmount the volume before I can run it.
(2) Safari Download Issue: When attempting to download a file via Safari, if the NTFS volume is mounted on the desktop the Safari will hang for about 15 seconds before it continues the download normally.
(3) Name In Finder: Though the volume's name is "Mimmic" both in Disk Utility and in Windows, it's mounted as "Mimmic 1" and no amount of changing on my part can fix this. It will change temporarily but the next time I mount the volume it will be "Mimmic 1" all over again.
(4) Finder Eject: I cannot unmount the volume by key command or dragging to the trash, I have to unmount it via Disk Utility.
It's a good little utility and once these issues are ironed out it'll be an invaluable piece of software.
Wishbone rated on 26 Jan 2012
Vid rated on 15 Dec 2011
-1
Husch rated on 14 Dec 2011
formaher rated on 12 Jul 2011
bigkung rated on 03 Jul 2011
Jmsoho rated on 24 Jun 2011
+3
mymon rated on 17 Apr 2011
dbbowman rated on 24 Mar 2011
+1
Elnacho rated on 23 Feb 2011