Hello Yves,
surrel@[EMAIL PROTECTED]
(Yves Surrel) wrote in message
news:<4fe1a34c.0408131448.5306ee2@[EMAIL PROTECTED]
>...
>[snip]
> I get:
>
> Error # 220 Couldn't load shared library - see value system_err# for
> error
>
> system_err# .
> -2804
>
> What is wrong? I have put MySharedLib in the same directory as
> PowerMops
I am sorry to say that this seems to be a bug of PowerMops, though it
hardly
comes to the front on Mac OS 9.
If you have a resource fork editor, you can get to a tem****ary fix.
1. Open 'cfrg' ID=0 resource of your library "MySharedLib" with your
resource fork editor, and
2. Set the "Usage" field "0", which would initially be set "1".
3. Save edited resource and close the fork.
PowerMops should become able to "libcall" any entry word in the
SharedLibrary put in the same folder as PowerMops.
But this is not the end of the story. After calling a word
in SharedLibrary, installed AppleEventhandlers, esp. quitapphandler,
seem to be broken. So when you are going to quit PowerMops, do it via
its file menu. Don't quit PowerMops from ApplicationMenu
(PowerMops will crash).
This also seems to be caused from another bug of PowerMops.
These bugs will probably be fixed by the next release of
PowerMops, though I can't give the warranty ;-).
Sincerely,
Nao Sacrada


|