[totoymola]

This is what I did.

First, I entered my license number in the INI file, then ran this command.

start /w "Adobe Photoshop CS2.msi" transforms="Adobe Photoshop CS2.mst" /qb!-
I didn't run all the other msi's because I'm only concerned about the activation window. Luckily, it didn't show up because of the transform file. But I have to do a test again, on a clean system.

[orustom]

totoymola, on May 8 2005, 12:31 AM, said:

stupid double post.. 
<{POST_SNAPBACK}>

lol...I hate it when that happens!

I'm in the process of creating a fresh install of XP. Will update again later tonight after I try some stuff out.

[totoymola]

I attached the MST again. I tried it on my current system twice without any problem.

orustom, instead of editing the msi directly, try using the mst. I'm not familiar with Orca, but if you remove the custom action, you have to remove it to the sequence also. And should not delete it from the binary table. (If I'm not mistaken, it's under binary24) That's probably why you're getting an error.

The target of CA_ActivationCheckLicense is CallALMCheckLicense. That is the activation window. The custom action CA_ActivationCheckProductActivationStatus is also under binary24, that's why I thought you have to remove it also.

[totoymola]

Quote

I noticed that he did NOT remove CA_ActivationCheckLicense, which makes me more curious as to what changes he made

I download his msi so I can give you a good answer to you question.

Quote

Report of differences between original installation:
C:\Documents and Settings\xxx\Desktop\Adobe Photoshop CS2.msi  <---- This is my untouched retail msi
And updated installation:
C:\Documents and Settings\xxx\Desktop\adobe photoshop cs2 (modified).msi <---- This is his modified msi

Table Property, changed record:
From UNITYSELECTION | RETAIL    --- this doesn't
    To UNITYSELECTION | TRYOUT  --- really matter

Table InstallExecuteSequence, deleted record CA_ActivationCheckLicense.  <---- This is the only modification he made.

In short, we are going on the same direction. He also removed the custom action like what I did.

I hope this answers your question.

Wait, if you already have his modified msi, why do you have to make a new one?


mrmb, I think you should compress your msi (with winrar) to save bandwidth.
Uncompressed - 4.85 MB (5,091,328 bytes)
Compressed - 1.09 MB (1,145,971 bytes)

[orustom]

Thanks for the info. I'll post some results tomorrow evening. Gotta get to bed before I pass out on my keyboard.

[Astie]

totoymola, on May 8 2005, 01:07 AM, said:

Quote

I noticed that he did NOT remove CA_ActivationCheckLicense, which makes me more curious as to what changes he made

I download his msi so I can give you a good answer to you question.

Quote

Report of differences between original installation:
C:\Documents and Settings\xxx\Desktop\Adobe Photoshop CS2.msi  <---- This is my untouched retail msi
And updated installation:
C:\Documents and Settings\xxx\Desktop\adobe photoshop cs2 (modified).msi <---- This is his modified msi

Table Property, changed record:
From UNITYSELECTION | RETAIL     --- this doesn't
    To UNITYSELECTION | TRYOUT   --- really matter

Table InstallExecuteSequence, deleted record CA_ActivationCheckLicense.  <---- This is the only modification he made.

In short, we are going on the same direction. He also removed the custom action like what I did.

I hope this answers your question.

Wait, if you already have his modified msi, why do you have to make a new one?


mrmb, I think you should compress your msi (with winrar) to save bandwidth.
Uncompressed - 4.85 MB (5,091,328 bytes)
Compressed - 1.09 MB (1,145,971 bytes)


<{POST_SNAPBACK}>

wow you guys rock. i havvent replayd in this topic because i got banned without a reason.

ive tried your solution with Wise Package Studio, and search the msi script for CA_ActivationCheckLicense. I've removed that line (in total 3 in a row) and then run the installation (setup.exe /v/qb!). It really went sillently and i want to thank you all for helping me and many others with this problem.

greetz Astie

[totoymola]

Quote

i havvent replayd in this topic because i got banned without a reason.

Oh.. I'm sorry to hear that.. Well at least you're not banned anymore.

I'm glad it's working for you.

[orustom]

@ totoymola: I tried using your MST file on a clean install using the original unmodified MSI file, and it works perfectly - no activation window!

Of course the activation window DOES come up when I first start Photoshop after it's installed. The registration window also comes up the first time it's started. Any idea how to get rid of both of these? That would be the next step. My guess is its some form of registry edit....

Edit: OK, so I used Regshot to take a snapshot of the registry before and after doing the activation, and I saved the differences in a .reg file. Now to try it out from scratch on a clean install. Stay tuned!

Edit 2: Well, for whatever reason the registry edit didn't work. The .reg file I made was refusing to integrate into the registry using a simple double-click, so I had to cut back one key at a time until I determined that the keys that could not be updated were all in the following branch:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ADOBE_LM_SERVICE]

So using a .reg file that was missing that branch did not disable activation.

[Astalavista]

http://rapidshare.de...SI_MST.exe.html


msi w/ mst together in one file.

Notes: on using Rapidshare. click free, wait 30 seconds, downlaod file.

[lecben]

This might help you guys :

http://www.adobe.com...ocs/331261.html

[jelli]

Tried the MSI just now and thanks a lot for all your work on the unattended the fact that it now installs without the activation screen appearing is enough for me and i hope this makes your work that little bit nicer!

Thanks Everyone!

[blinkdt]

Discussion Removed.

This post has been edited by blinkdt: 16 February 2006 - 02:22 PM

[jelli]

Looks interesting couldnt you just create a couple of variables, place the desired data such as activation code, serial etc and use the script to activate the software using the code instead of using that generator which in theory would give you endless posibilities.

Sorry not that familiar with AutoIt so if my suggestion is so noobie then just disregard it

[blinkdt]

Discussion Removed.

This post has been edited by blinkdt: 16 February 2006 - 02:22 PM

[totoymola]

About the activation, we have to keep track of the file that is created when we activate. It can be a file(s), registry entry(s), or both. Just like the Adobe Acrobat Professional.

[Astie]

totoymola, on May 9 2005, 07:08 PM, said:

About the activation, we have to keep track of the file that is created when we activate.  It can be a file(s), registry entry(s), or both.  Just like the Adobe Acrobat Professional.
<{POST_SNAPBACK}>

here is the activation file located for every user of your pc. its a .dat file.

Documents and Settings\All Users\Application Data\Adobe Systems\Product licenses

[orustom]

Astie, on May 10 2005, 03:34 AM, said:

totoymola, on May 9 2005, 07:08 PM, said:

About the activation, we have to keep track of the file that is created when we activate.  It can be a file(s), registry entry(s), or both.  Just like the Adobe Acrobat Professional.
<{POST_SNAPBACK}>

here is the activation file located for every user of your pc. its a .dat file.

Documents and Settings\All Users\Application Data\Adobe Systems\Product licenses
<{POST_SNAPBACK}>

Sweet. Thanks for bringing this to my attention. Gonna have to try copying over this file along with the registry changes and see what happens.

[Muaitai]

Can we modify that to activate Creative instead of only Photoshop?

[orustom]

@ totoymola: Is it possible for you to make us an Illustrator CS2 MST file as well?

[totoymola]

I will try tomorrow. I can't do it now because I'm studying for my test.