Re: CreateMovieStorage + valid path = bdNamErr -- Anyone out there?

OSErr err;

Handle dataRef;

OSType dataRefType;

err = QTNewDataReferenceFromFullPathCFString(

(CFStringRef)path,

kQTPOSIXPathStyle,

&dataRef,

&dataRefType

);

DataHandler dataHandler;

Movie movie;

err = CreateMovieStorage(

dataRef,

dataRefType,

'TVOD',

smCurrentScript,

createMovieFileDeleteCurFile,

&dataHandler,

&movie

);

and it works perfectly. No errors.

Yet, for some reason, your exact same code "always get -37 bdNamErr."

That, I submit, is a clue. Something about the "perfectly legit" paths your code generates isn't as legit as you're assuming.

Need code?

I asked you to post your code that manipulates the path. You still haven't done it. Instead you showed something that obviously isn't in your actual app.

What are you -really- doing to obtain these paths that "always" get error -37 bdNamErr ??

It most certainly is a valid path. The colon is not a path separator
it's part of the filename.

You forgot to add: "...in the context of POSIX/BSD. HFS calls have a different convention. At the intersection, for example in Quicktime, extra care is required."

Just because Finder special-cases colons to display them to as slashes (a concession made, I believe, to early Classic adopters), that doesn't mean HFS calls are happy to see mixed colons and slashes.

Stepping into CreateMovieStorage(), I see many HFS calls, ResolveAliasWithMountFlags(), PBMakeFSSpecSync(), et al. Could there be some combination of HFS API that get confused when your "perfectly legit" but rather unusual paths are converted variously to HFS paths, Pascal strings, legacy FSSpecs, aliases, aliases resolved back to FSSpecs...

Error -37 bnNamErr is telling you: yes, there is.

On Wed, 28 May 2008 20:45:55M, Seth Willits <email@hidden> wrote:

I think 4/5 questions I send to the list go unanswered. It's rather

depressing

It's rather frustrating to read repeated posts which:

-ignore their own blatant clues

-claim "OF COURSE <blatant clue> makes absolutely no sense" (emphasis added)

-don't post the relevant code

-don't post the relevant code *even after being specifically asked*

-generally project an assumption that the poster's code must be OK and that the system

returns error codes for no rationally discernible reason.

Some people who ignore all posts of that type.

Also, WWDC is almost here. Apple folks who might usually reply quickly are, perhaps, a little busy right now?

[@"Hello Bill" writeToFile:[@"~/Desktop/Today:Friday.txt"
stringByExpandingTildeInPath] atomically:YES];

Yup, you can use Cocoa, fopen(), whatever, to create a file called "Hello Bill" whose name includes a colon. And I have a Movie here named "Hello Seth" that shows the problem is in the code you haven't posted. Guess it's up to you whether you want to show the actual code, or just keep posting error codes and saying "it doesn't work."

Best of luck with your problem.