BC 3.2.2 and Mac file errors

So how do such files end up in the Garmin\gpx folder?

To reproduce this, all I have to do is put a valid gpx file, rename it to something like ._RouteName.gpx and have Windows BaseCamp try to access it?

No and yes and make the file hidden. The content of the file may not be GPX. Take an executable or other binary file and rename it.

Today. both my Edge800 and GPSmap62 gave me the same kind of error.

Ok, but how would you end up with such files on your device?

I will still look into handling this more gracefully, but I currently do not understand how such files would end up on your device unless you willfully created them. Are these created by Mac BaseCamp?

Created by Mac OS X Finder (like Windows Explorer) If I edit directly with an application the Mac OS X wants to add extra information which does not fit into Fat32 file attributes and then creates a file with the same name and a dot in front or ._ in front.

It's not BaseCamp for Mac which does this, It's me who copies a GPX file to the \Garmin\GPX folder and open it with an notepad, edit something and then save it. And the Finder acts on this

This is known as the Apple Double file system. Apple has been using this for years (since the A/UX days). Any time Mac OS X writes forked files to a non-native files ystem (not HFS(+)) it will write in Apple Double.

http://en.wikipedia.org/wiki/AppleDouble
http://support.apple.com/kb/TA20578

Thank you for the explanation, I am a Windows guy (if you couldn't tell).

We'll see what we can do.

Falagar, I'm not a Mac guy either but Marco is talking about "fork" files.

Windows has no clue about the actual contents of a file and, therefore, no clue about what app to launch it with. The only, very primitive, thing it can do is associate a file type with an app. But Windows is not smart enough to do that. Either an app establishes its own file type associations when it installs or you have to add/modify the associations yourself.

The Mac is different. When a file is created or edited on the Mac, the app (not the Finder) adds a fork which contains information about what app to use (or was last used) for the file. In Marco's case, when he uses the Mac Notepad to look at or edit the file, it's the Notepad that's creating the fork.

So you can call a file pretty much anything you want, e.g. no file type needed, and the Finder will still figure out from the fork which app to launch the file with.

Find out if there's something like a standard header in Mac fork files, e.g. similar to the header of an XML file, (your Mac folks should know) and you should be able to trigger some sort of useful warning or simply know that it's okay to ignore it in the Windows BC. I have no idea of the construction of a Mac fork file so I don't know if it's plain text or binary.

...ken...