Another solution to this is to simply change the name of the MathLib you are using. Load the one of that name thus there is much more assurance that you are working with a version that is workable. Kinda defeats the reasoning for shared libraries but then, it seems there is a version trap happening here. You can also check the GetVersion call on MathLib and then notify the user of any conflict. Steve "unix geek " wrote: > What version of Mathlib are you using? Are you sending the users > the "working" version of Mathlib with each release? There are several > iterations out there. I had similar problems with an app I installed > (which came with a version of Mathlib) and then PocketC would fail > compilations. I used the one with PocketC, and now all is working fine. > > Try that... > > On Tue, 22 Sep 1998, SilverWARE wrote: > > > I have an application which uses the MathLib. I have several testers > > reporting a fatal exception when any call is made into the MathLib. I > > confirmed this when I sent a special version that made no calls into the > > MathLib and the error did not occur. > > > > It does not happen to all testers and does not seem to be machine > > specific although those reporting the problem are using a Palm III. The > > interesting thing is that there are others using the Palm III without > > incident. I cannot cause the problem to happen in the emulator or on my > > machine. > > > > Does this ring a bell for anyone. I am really stuck and was hoping to > > find someone who might know something regarding this problem. Maybe any > > clues on how to isolate it. > > > > -Scott > > SilverWARE > >
