I am packaging Thai dicionary.

We purchased this software twice. One for company "Comp AA" and the other for "Comp BB"
and the vendor programmed to show customer's company name in status bar. So it is the same software(Thai dictionary) but when I install for company "Comp AA", then I use company "Comp AA"'s CD. and for company "Comp BB", I use "Comp BB" CD.

My problem is that I don't want to develop package for each CD only to show company name differently in status bar. I asked vendor if they can delete company name for both and provide me just one CD but they rejected. So I asked if we can use common part "Comp" in 2 companies name but they also rejected. Vendor said that it is required to know what company outflow the source in the dark market illegally.

I wonder if anyone can adivse me which file(text, dll or whatever, registry) in the source files contains "Status Bar" information? --> I don't know if such kind of file exists but vendor told me that they can't let me know.

Ps) I searched registry and text file and msi file but didn't find it yet.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


As you don't say exactly what software this is, nobody - other than the vendor - would likely be able to tell you.

There are a few ways which vendors use to encode this information. These include:

- as a registry entry (normally hashed/encrypted in some way, so as to be illegible)
- as a hashed data file
- as part of the EXE (less common these days)

It should be simple enough to capture both installs and compare the two resulting MSIs or, if is is already in MSI format, to install both and log the installs. Once you have identified the location of the information, you can use/create one MSI but with a separate transform for each company, containing the hashed registry entry or file.
Answered 06/23/2008 by: VBScab
Red Belt

Please log in to comment