GetDiskFragment library name limited to 63 chars?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

bg-greece - 15 Nov 2006 10:35 GMT

Does anyone know how to overcome the 63 char limit in the fragName argument when calling
GetDiskFragment? So far, I have understood that I have to supply the full path name of the
native library.

Thanx

Reply to this Message

Paul Russell - 15 Nov 2006 10:55 GMT

> Does anyone know how to overcome the 63 char limit in the fragName argument when calling
> GetDiskFragment? So far, I have understood that I have to supply the full path name of the
> native library.

fragName
An optional name of the fragment. (This information is used
primarily to allow you to identify the fragment during debugging.)

So I think this a non-issue.

Paul

Reply to this Message

bg-greece - 17 Nov 2006 09:55 GMT

I also tried the following code, using MoreFilesX.c, (I have omitted the err != noErr and
other variables). my_Path is a Posix path: "/Users/byron...."

FSRef dirFSRef;
FSSPec fss;
long ID;

err = FSPathMakeRef((const UInt8*)my_Path, &dirFSRef, NULL);
err = FSGetNodeID(&dirFSRef,&ID,NULL);
err = FSMakeFSSpec(0,ID,(const unsigned char*)"\pMyLib",&fss);
err = GetFiskFragment(&fss, 0, kCFragGoesToEOF, (const unsigned char*)"", kLoadCFrag,
&implCon, (Ptr*)&CFMFunc);

When my_Path is something like /Users/byron/Desktop/MyApplication/MyPlugin,
GetDiskFragment works fine. But when called from inside a Java application bundle, where
the path is more than 100 characters, GetFiskFragment fails with -2806. Is there a
character limit in the path we pass to FSPathMakeRef? If so, can we overcome this?

Best

Reply to this Message

Mac Forum / Programming / CodeWarrior / November 2006

GetDiskFragment library name limited to 63 chars?