I have been pulling my hair out trying to get to the bottom of an err -50
from CreateMovieFile() on Windows XP.
The first call to CreateMovieFile() fails w/ the error.
The 2nd time this module gets called, CreateMovieFile() succeeds. It would
appear that if the file is already there, then CreateMovieFile() will
proceed. But if it creates the file (as in the first pass), then it aborts
w/ an error -50. And sure enough I did check this; ie, even tho
CreateMovieFile() returned an error, it did create the file!
Not all XP systems do this! We could not make it happen on 4 systems, but a
5th system was predictable as heck...
Here is the code fragment:
err = FSMakeFSSpec( 0, 0, QTfilename, &QTfilespec);
...
err = CreateMovieFile( &QTfilespec,
FOUR_CHAR_CODE( 'TVOD' ),
smCurrentScript,
createMovieFileDeleteCurFile |
createMovieFileDontCreateResFile,
&destResRefNum,
&theMovie );
So my workaround could be:
does err == -50
does the qt file exist? (will do the FSMakeFSSpec() again)
if so, then CreateMovieFile() *again*
And, yes, this workaround does the job! I know NASA likes redundancy, but I
don't think this is what they had in mind...
Comments? Ideas? This problem seems to coincident to QT7 releases...
-harry
[Windows XP ServicePack 2, QuickTime 7.0.4]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
This email sent to email@hidden
