Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This Reddit post is interesting for files on the homepage
 

Attachments

  • 1623792124961.png
    1623792124961.png
    2.3 MB · Views: 290
...there are and always have been corruption issues with writing to NTFS. Even if you use a MAC, it doesn't include write access, it used to be considered that Microsoft didn't open source the spec so you had to license it from Microsoft. If you wanted to get write access to NTFS you had to add file system support from a third party vendor, even that was less than 100% stable. Basically, there is nothing great about NTFS, it is a good bridging technology because Windows can't read apple formats (what year is this?). So apple or Microsoft to blame? I guess Microsoft will support Apple drives in about 2075
2075 - isn't that the launch date for Finder on iPadOS 69?
 
Ugh, It's all Apple fault for trying to promote iPad as a computer replacement. People are nitpicking and comparing to macOS and other normal OSs. Just make iPad and Mac 2 in 1 separately so people would be satisfied.
 
iOS/iPad OS doesn't cache writes the way Mac OS does. There is no corruption risk and no need for unmount.

Maybe that works in theory but my real-world experience says otherwise.

I've had an exFAT-formatted USB drive get completely corrupted after connecting to iPad. Drive was completely unreadable and formatting wouldn't work. Had to rebuild the MBR.
 
Why has NTFS support on MacOS been read-only for so many years? And now the version they bring to iPadOS is read-only too!

Is there just some licensing they don't want to pay for? Linux has had read-write NTFS support for years.
On my Mac, I use Paragon software to enable NTFS write-support. This is for any external drives which I need to connect to a Windows device or tv. The application works really well, I've never had file corruption problems other than with improperly ejected disks from the tv or Roku (there's no 'eject' USB device option!).
 
The Files app was never part of iOS in the early days. NTFS (read-only) on Mac has always had a longer stay.
 
Today after I read this post I tried to access my Samsung external HDD NTFS format file with my Ipad Air 4 running IPADOS 14.6 and it already works. It can read but cannot write, but is already working.
 
Wonder if the files app will finally connect to a Time Capsule.
Apple employee here? Why?

Time capsules were discontinued 3 years ago or so and those old 5400 RPM drives in them are on the their last legs and they are really just bog standard old school routers. The internal drive is really mean for time machine only. The argument you could make is that you can connect a USB drive to it for "cloud" storage but again bog slow usb drive connected to a USB port that the traffic is going to have to route over old AC wifi.
 
I use Jettison & Automounter on Mac for SD card safety, as it stays inserted 24/7 (music)

File Browser on iPadOS/iOS/tvOS is great.

I keep hearing contradictory statements on whether or not to eject/unmount SD cards, USB drives (directly attached to Mac) or router (NAS-lite) when sleeping or shutting down my Mojave Mac, so I just use those two apps just in case…
 
Nice, now add an unmount/eject media button so that users avoid file system corruption.
The NTFS support is said to be read-only, so it doesn't matter. And FAT filesystem handlers are generally made to promptly write at least metadata (directory and allocation information, timestamps, etc) on the age-old assumption that people may remove removable media (going back to floppies with manual eject) without following any particular procedure. So there shouldn't be much filesystem corruption happening anyway.

Having said that, wherever there's a mount, there should be an explicit unmount possible, rather than a forced unmount after the media has already been yanked. But many people will do the wrong thing anyway, so it should generally work regardless.
 
  • Like
Reactions: Kal Madda
I use Jettison & Automounter on Mac for SD card safety, as it stays inserted 24/7 (music)

File Browser on iPadOS/iOS/tvOS is great.

I keep hearing contradictory statements on whether or not to eject/unmount SD cards, USB drives (directly attached to Mac) or router (NAS-lite) when sleeping or shutting down my Mojave Mac, so I just use those two apps just in case…
Most Unix-like OSs unmount (logically eject) filesystems as part of shutdown (ancient Unix didn't explicitly flush or even have a clean flag, so once down to single-user, one would sync, wait a bit, and just hit break, and checks would be run at every boot; but nothing that runs un-emulated on remotely modern hardware behaves like that anymore). An in-memory sleep might become something else if the battery runs down, so it's possible that an unmount might not always happen when it should, but I don't see much risk there, esp. if you have backups. Unmount of network shares, might depend on the sharing mechanism whether it matters; usually it doesn't too much, because there's too many things (client, server, network) that could fail anyway, so they're designed to cope.
 
give us icon previews and default app assignment to open particular file types
Default app assignment is nice, but if there's more than one app that can handle something, I want the option to choose rather than be locked into the default (i.e both Open and Open with:). And I'd kind of like the option to choose what the default is (like on a Mac in Finder Get Info, choosing Open with: and Change All; or scrounging the Default Apps preference pane).
 
Any improvement to the Files app is welcome :). Good to have progress indicator along with NTFS support.
 
iOS/iPad OS doesn't cache writes the way Mac OS does. There is no corruption risk and no need for unmount.

Even if the OS doesn't cache writes, you don't know that all processes that have file handles open don't still have a buffer that isn't flushed.

And, I mean, if you copy a large file to a disk, and pull out the disk in the meantime, what's the OS to do? The OS can't anticipate that you were going to pull the disk out, so you end up with inconsistent data no matter what. Reducing buffers can only mitigate that (and comes with its own host of issues).
 
The platform vendor implementing most of the important features while third parties can do enhanced versions with even more features is, IMHO, exactly how it should work.
Well no. What happens is IT support in the workplace just bans third party file managers.

I just want a file manager as functional as MacOS finder. That’ll do.
 
Last edited:
  • Like
Reactions: onlinespending
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.