Thanks. It works now. After tripple-checking I found the culprit - the good'ol'typo classic mistake... The error message was leading me to a different direction, so I didn't immediately found the error. Perhaps "path not found" instead of "path not accessible" would be better? Something to remember for the future. Tom
2009/9/14 Dave Keck <davek...@gmail.com> > > using NSTask, or something else? > > Woops, missed your subject line; NSTask, got it. But yes, I would see > if you're able to read the executable as plain data, using NSData's > dataWithContentsOfFile: to make sure the path is in fact accessible. > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
