Some simple Mac questions

Started Jun 21, 2013 | Discussions thread
MikeFromMesa
Senior MemberPosts: 2,849
Like?
Re: Some simple Mac questions
In reply to Tom_N, Jun 22, 2013

Tom_N wrote:

The DVD may have been mastered with multiple sessions, one of which contains a HFS+ volume (for Macs) and another of which contains a volume in some other fomrat (for PCs).

Also, a Mac OS X application file is not a single file, but an entire directory tree – one marked so that the Finder will pretend the tree is a fille, unless you ask it to "Show Package Contents". This allows an application to contain many independently-loadable resources, while storing them in a more standard way than the mechanism ("resource forks") previously used for this purpose.

Windows and Linux do not know about the Mac's "package" convention, so I would expect them to see a Mac OS X application (or other package) as being a directory tree. No harm done, but if you were looking for a single file and you saw this tree instead, you might be confused.

Oh. OK. That makes sense.

He doesn't mean that you should enter your serial number in the search box.

He means that once you have a copy of Lightroom 4 (the version you own now), from whatever source (disc or download) installed on your Mac, you should enter the SN you are now using on your PC copy of Lightroom in the SN dialog in the Mac version of Lightroom.

That much I already knew.

If it is the same version, the SN should work on both platforms. I believe people have said before that Adobe allows you to have two installations of Lightroom, which can be on either platform (two PC installations, OR two Mac installations, OR one of each). With Photoshop, they only allow your installation(s) to be on a single platform (go figure).

According to Adobe's chat folks you cannot have one copy on each platform type. You can have 2 on Windows OR two on Mac, but NOT one on each.

According to Wikipedia, Microsoft does not publish details of its NTFS implementation – making it difficult for others to implement compatible filesystem drivers.

Presumably reverse engineering is illegal, but someone has found some way to figure out how to write to NTFS from Macs so either they did reverse engineer the software or they spent a lot of time guessing. I would think the former.

But if the information is available to NTFS-3G and if that is open source, then it should not be a big mystery. Unless NTFS-3G is really buggy.

Wikipedia also reports that recent versions of Mac OS X contain hidden, undocumented support for writing to NTFS volumes. Those who have turned this support on have found it to be full of bugs.

Well, that's not good.

If I was an Apple Engineering manager, I would not approve the default enabling of a "allow writes to NTFS" feature that would result in frequent kernel panics – or worse, the corruption of customer disks. It would be better not to have the feature at all than to ship THAT.

Of course. It is much better to not have the functionality at all than to provide a really bad implementation. The latter is a road to a good deal of grief.

If the same code could do a reliable job of reads (which might be less tricky, and which in any case would not pose a data corruption threat to the source disks) – then yes, it might be useful to support them, even without the writes.

Also, Apple may be figuring that given the existence of FAT32, exFAT, and third-party NTFS drivers, it isn't that important for them to spend their time on making their own NTFS write code work.

Given the market share of Windows as compared to Apple I can easily understand why few disc manufacturers worry about providing Mac drivers for the usb drives, but I would think that it would be a big deal to Apple itself. Apparently it is not, but I would have thought so.

Interestingly enough you can get a driver for the Mac to allow them to write to Seagate drives (and I don't think that the software is a FAT32 format app) and I have to wonder why that software would not work for other usb drives as well. Of course there could be Seagate-only restrictive code in their drivers (and I could see why Seagate might want that) but if there are such drivers around I still don't see why Apple doesn't incorporate some such code in the OS. Unless, of course, they don't really want to. Perhaps they don't want to make use of NTFS easier but prefer use of their own file system format.

Reply   Reply with quote   Complain
Post (hide subjects)Posted by
(unknown member)
Keyboard shortcuts:
FForum PPrevious NNext WNext unread UUpvote SSubscribe RReply QQuote BBookmark post MMy threads
Color scheme? Blue / Yellow