GreatStella
Great Stella is a legacy install that I have bundled into an MSI. The problem is that after installing the MSI, upon first launch the software wants a license file to register itself. I generated the MSI with Wise Package Studio using the setup capture method:
1. Did first snapshot
2. installed and licensed software
3. restarted system
4. took after snapshot
I have tried using the first launch options in Package Studio with no results. I have found what i believe are the registry keys generated by licensing and a file and made a transform out of them but the software still wants to be registered. Anyone have any ideas?
1. Did first snapshot
2. installed and licensed software
3. restarted system
4. took after snapshot
I have tried using the first launch options in Package Studio with no results. I have found what i believe are the registry keys generated by licensing and a file and made a transform out of them but the software still wants to be registered. Anyone have any ideas?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Wow...you take your time packaging, don't you? :)
Run the application alongside ProcMon and see what file/registry activity is taking place to trigger the license prompt. Pound to a penny it's going to be file/registry permissions or it's accessing a file/registry key which you excluded from the capture.
Run the application alongside ProcMon and see what file/registry activity is taking place to trigger the license prompt. Pound to a penny it's going to be file/registry permissions or it's accessing a file/registry key which you excluded from the capture.
Posted by:
pisanom
16 years ago
I have tried all of that. It seems that the licensing changes. What I need to do is figure out a way to enter the info upon forst launch by a non admin. And yes I have tried to capture first launch info and get that into my package. Any ideas?
Posted by:
anonymous_9363
16 years ago
I have tried all of that. It seems that the licensing changes. What I need to do is figure out a way to enter the info upon forst launch by a non admin.So that sounds like you have the information you need but now need to know how to have it already populated when each user logs in. Is that right? If so, what do the changes comprise? File or registry changes? If file changes, where are the files located? In the user profile? If registry, which hive/keys are involved?
And yes I have tried to capture first launch info and get that into my package....and....what? You couldn't get it in? Didn't know how? Too complicated to figure out?
More info, please.
Posted by:
pisanom
16 years ago
Well I found some information on licensing in the registry but copying out does not work. I contacted the maker and he responded:
"The licensing is deliberately cryptic and designed so that you can't
easily copy it from one machine to another, and I'm sure you'll
understand if I don't wish to devulge how it works. You're right
though that copying data from the registry won't work."
The keys are HKLM\software\stellasoft\stella
and HKCU\software\stellasoft\stella
There is an encrypted file wid60p.sgb in system32 that seems to be added after the software is licensed but I cant figure it out.
The first launch stuff is added no problem but when installed on a clean machine it requires the same first launch licensing info.
"The licensing is deliberately cryptic and designed so that you can't
easily copy it from one machine to another, and I'm sure you'll
understand if I don't wish to devulge how it works. You're right
though that copying data from the registry won't work."
The keys are HKLM\software\stellasoft\stella
and HKCU\software\stellasoft\stella
There is an encrypted file wid60p.sgb in system32 that seems to be added after the software is licensed but I cant figure it out.
The first launch stuff is added no problem but when installed on a clean machine it requires the same first launch licensing info.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.