/build/static/layout/Breadcrumb_cap_w.png

PDA Connect

Hi all,

Does anyone know anything about Novell’s PDA Connect program? I created the msi and it compiles fine but when I click on the shortcut to sync the pocket pc I receive the following error: “unable to locate translator for name PocketPC” I did a capture without the hardware plugged in because we use various pocket pc models. Any suggestions to resolve this error would be greatly appreciated, thanks.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: viswakar 18 years ago
Senior Yellow Belt
0
Hi ,

If You are using Wise package studio for capture , You have to enable the option " Capture Changes in Hardware registry entries " for this package before setup capture .

Cheers !!
Posted by: rj01 18 years ago
Senior Yellow Belt
0
I don't have the hardware plugged in so would I still want to do a hardware capture?

On a different note I think I found the problem. A couple ini file weren't getting captured under the translator folder and once I added those to my msi the error messages went away.
Posted by: viswakar 18 years ago
Senior Yellow Belt
0
Hi ,

If the application makes any entry to HKEY_LOCAL_MACHINE\SYSTEM then you need to enable the specified option .
NB : Mark this only if all destination computers of the repackaged installation will have identical hardware configuration.

Cheers !!
Posted by: wiseapp 18 years ago
Second Degree Green Belt
0
I normally suggest that when you Wise to capture any package try using both the options SmartMonitor in conjunction with Snapshot since you get best of both the worlds.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ