Since I use the last version, nothing but troubles.
The onexecute event doesn't work anymore. I didn't change the source only update to the latest version. The Creator ID is the same as the Palm program in the PDA. The config event does work and the conduit is registered. What to do?
Please help.
With regards,
Spencer Schols
DreamDives
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very weird. The major change from previous versions of the software is that now the library dynamically loads in the DLLs at runtime rather than statically linking to them. But that shouldn't be a cause of your conduit failing to execute at all.
I'd recommend de-registering and then re-registering your conduit again. Double-check the creator Id and that the program with a matching creator Id is still on the Palm. Failing that, you have the source code for the full library - try putting a breakpoint at the very start of the OpenConduit method in pfgPalmComp.pas - this is the externally visible DLL method that HotSync Manager should call to handle the conduit - this method is responsible for passing control to your conduit event handling code. This way, you can at least determine for sure whether the problem is the HotSync Manager not calling your conduit at all, as opposed to a problem in your code.
Paul.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm also having this problem. Config works fine. Execute doesn't get called at all. I've tried unregistering and reregistering to no avail. I've also tried checking the OpenConduit method but it never is called either.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>I'd recommend de-registering and then re-
>registering your conduit again. Double-check the
> creator Id and that the program with a matching
>creator Id is still on the Palm. Failing that, you
>have the source code for the full library - try
>putting a breakpoint at the very start of the
>OpenConduit method in pfgPalmComp.pas - this is
>the externally visible DLL method that HotSync
>Manager should call to handle the conduit - this
>method is responsible for passing control to your
>conduit event handling code. This way, you can
>at least determine for sure whether the problem is
>the HotSync Manager not calling your conduit at
>all, as opposed to a problem in your code.
Tried this one, it doesn't call the OpenConduit method at all.
Please helps, with regards,
Spencer
DreamDives
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is *really* weird. OpenConduit is the core method that's meant to be called by HotSync Manager. I'd almost say that your conduit isn't properly registered, although the previous mention that a configuration dialog was still coming up is somewhat of a puzzler.
The pfgPalmComp.pas contains both the OpenConduit method and the exports directive that Delphi uses to make a DLL function externally visible. You might want to run a program on a compiled DLL to check it's exports, in particular that OpenConduit exists - one such I use a lot is the Dependency Walker (check on Google for "depends.exe").
As long as the OpenConduit method is present, then the only reason why OpenConduit wouldn't be called is if an application isn't present on the Palm with the same Creator Id as that of your conduit. This is important, as it has to be program, and not a data file. Even a minor difference such as casing can stop a conduit from being activated. You might want to use a program like Db Explorer (freeware) to double-check the Creator Id of your compiled Palm program.
Hope this helps you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Since I use the last version, nothing but troubles.
The onexecute event doesn't work anymore. I didn't change the source only update to the latest version. The Creator ID is the same as the Palm program in the PDA. The config event does work and the conduit is registered. What to do?
Please help.
With regards,
Spencer Schols
DreamDives
Very weird. The major change from previous versions of the software is that now the library dynamically loads in the DLLs at runtime rather than statically linking to them. But that shouldn't be a cause of your conduit failing to execute at all.
I'd recommend de-registering and then re-registering your conduit again. Double-check the creator Id and that the program with a matching creator Id is still on the Palm. Failing that, you have the source code for the full library - try putting a breakpoint at the very start of the OpenConduit method in pfgPalmComp.pas - this is the externally visible DLL method that HotSync Manager should call to handle the conduit - this method is responsible for passing control to your conduit event handling code. This way, you can at least determine for sure whether the problem is the HotSync Manager not calling your conduit at all, as opposed to a problem in your code.
Paul.
I'm also having this problem. Config works fine. Execute doesn't get called at all. I've tried unregistering and reregistering to no avail. I've also tried checking the OpenConduit method but it never is called either.
Hi Paul,
>I'd recommend de-registering and then re-
>registering your conduit again. Double-check the
> creator Id and that the program with a matching
>creator Id is still on the Palm. Failing that, you
>have the source code for the full library - try
>putting a breakpoint at the very start of the
>OpenConduit method in pfgPalmComp.pas - this is
>the externally visible DLL method that HotSync
>Manager should call to handle the conduit - this
>method is responsible for passing control to your
>conduit event handling code. This way, you can
>at least determine for sure whether the problem is
>the HotSync Manager not calling your conduit at
>all, as opposed to a problem in your code.
Tried this one, it doesn't call the OpenConduit method at all.
Please helps, with regards,
Spencer
DreamDives
This is *really* weird. OpenConduit is the core method that's meant to be called by HotSync Manager. I'd almost say that your conduit isn't properly registered, although the previous mention that a configuration dialog was still coming up is somewhat of a puzzler.
The pfgPalmComp.pas contains both the OpenConduit method and the exports directive that Delphi uses to make a DLL function externally visible. You might want to run a program on a compiled DLL to check it's exports, in particular that OpenConduit exists - one such I use a lot is the Dependency Walker (check on Google for "depends.exe").
As long as the OpenConduit method is present, then the only reason why OpenConduit wouldn't be called is if an application isn't present on the Palm with the same Creator Id as that of your conduit. This is important, as it has to be program, and not a data file. Even a minor difference such as casing can stop a conduit from being activated. You might want to use a program like Db Explorer (freeware) to double-check the Creator Id of your compiled Palm program.
Hope this helps you.