Jeff Ishaq <[EMAIL PROTECTED]> wrote:

> I am confused by your usage of "Plug-in."  Is this a Network Prefs Panel
> Plugin (i.e. a PRC with the 'NPPI' creator ID?)  That's the only kind of
> "plug-in" that I'm aware exists for PalmOS.  If so, email me.
>

I don't know what the name of this in detail... but
"plug-in" has not PilotMain() but at least one code resource.
Other app can load this code resource and call the entry function.
Goto 3Com development support knowledge base page:

   http://oasis.palm.com/devzone/knowledgebase.cfm

and search "plug-in"
You can find the following article (Article ID: 1157)

   http://oasis.palm.com/devzone/knowledgebasearticle.cfm?article_id=1157

This article has a sample code of "plug-in".
Try to add SysLibFind() api (just 1line) to this plug-in
and check if you get the result or not. You can know what happens.

> If not, I assume you mean a shared library.  Unless you've burned a new
> SmallROM or WholeROM image, you should have no problem opening "Net.lib".
>

This is not a shared lib like SampleLib in SDK.

> Try using the OS-defined global, GSysLibNet.  This should always be valid.
> You probably should still try and find out why you can't open Netlib, a
> library that is installed by default each time the device is reset.  Only if
> the device is out of memory should this library not be around, and I suspect
> you will have a ton of problems if that's the case.
>

Instead of GSysLibNet, I tried SysLibTblEntry() (so I can check it in POSE,
Keith :)
and enumerated a few entries and compared lib name with "Net.lib".
After that, I got the refnum finally.
But still using this refnum makes plug-in very unstable after that.
Ive not checked it enough, though...

So maybe there is something about memory problem in PalmOS ???


Best Regards,
Hiroyuki Okamoto
mailto:[EMAIL PROTECTED]





Reply via email to