/build/static/layout/Breadcrumb_cap_w.png

MindGenius Education v2.5 - PIDKEY field

Tryng to package this up - peeked via ORCA and noticed that it doesn't have any PIDKEY field in the Property table.

So I added it with the serial number and created an transform file. Then did a test install.

That worked. But upon first launch, I get a box coming up with the name and company name already fileld out including the serial number. I do nothing and clicked the OK button and it loaded up.

I thought that if I added the PIDKEY, it should automactilly accepts it and go straight toloading it up. But I guess not.

How do I get it not to come up?

Thanks all.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: zipsantro 15 years ago
Purple Belt
0
Application must have an entry point for the EXE to open that box. It can be registry key or ini file. You need to find that entry point and add it to your MST to some value so that this box will not appear.
You can capture that information by doing a gap-capture between first installation and first launch.

Jeeoo!
Santro
Posted by: anonymous_9363 15 years ago
Red Belt
0
PIDKEY is a generic property: not all apps will use it. IIRC, early versions of Office used it.

My guess would be that your package is just populating the relevant text box with the data but not doing anything with it. Take a snapshot of what happens when you enter the data. My money's on it being written to a key in HKEY_CURRENT_USER. Once you have that, you can add it to your package via your transform.
Posted by: tsutton 15 years ago
Orange Belt
0
Thanks for the replies.

That's what I suspect, so will get my tools out and get digging. :D
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