On Mon, Aug 28, 2000 at 03:38:20PM -0500, Bradly J. Barton wrote:
> > Using the user list which usually causes a message about the
> > installaide dll not being found...
>
> Under a Mac, I don't know how you could do this, but the problem on Windows
> is that the InstallAide.dll is in a directory that is not in the path.. so
> you have to find it. How do you find it? Well, one way would be to look up
> in the directory what the default application is that handles PRC and/or PDB
> files. Once you have that, you'll have a path for it. Change your working
> directory to that path and then use LoadLibrary to open InstallAide.dll ...
> or have one program change to that working directory and launch your app
> that links to InstallAide.dll ... either way, you will have to look in the
> directory.
Basically do it the way OReilly's book suggests - include the current
condmgr.dll, use it to ask where the directory is, then maybe load the
condmgr.dll in the palm directory and verify that it is the real path.
Yuk.
(The Mac doesn't have any of these problems - it finds things without
a registry or other nonsense; the only difficulty I have there is that
there is no "trivial" example, just big, integrated programs, and that
the SDK is for an obsolete version of CodeWarrior so doesn't work
right as installed, but both problems are tractable, though annoying)
The problem is that if I am going to hack the registry anyway, I may
as well do the entire process of installation via the hack.
It is not that I cannot do what I want to do. It is that I cannot do
it using only the documented and official API. And if I have to hack
for one call, I may as well do it for all since any one might break in
a new version.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/