Jump to content

orustom

Member
  • Posts

    32
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Barbados

Posts posted by orustom

  1. Hello Evrybody  :hello:

    I'm very glad to have found such wonderful community. I've been browsing the forum and reading the threads as well as going through the unattended guide over and over again for about a month now. This is really helpful and informative. Thank you for the wonderful and huge effort you're making.

    Excuse my long opening, but this is my first post and I'm very excited  :D

    One thing that's not working for me is the download links. I've seen this happening to others but neither the alternative links are working. I think because we share a proxy server here (ALL the country). This download for example is very difficult to get and from your reviews I am eager to get it.

    Nonetheless ... Great work, and keep up the good work.

    Welcome to the forums!! :thumbup Hope you enjoy your stay. :D

  2. I have a question for everyone watching this thread...

    Choice A: Build Winamp MSI based off of 5.09

    Choice B: Wait for 5.091 which is SUPPOSED to be out at the end of the week, so that all of 5.09's bugs are fixed and no one complains.

    Just post your vote

    How do you know B is coming out the end of this week?

    If you're sure about it, then I vote for B, otherwise both A & B :P:blushing:

  3. At the moment we've got 1]editing abcopy.inf, 2]using modified msi, 3]using mst files, 4]autoIT scripts, 5]keygenerators, 6]copying .dat files and godknows what else. People are also posting in this thread about Illustrator, too!

    I would love to do a guide if I can get the darn thing working! :realmad:

    Btw, the postings about Illustrator are ok since both programs use the same method for activation, store their .dat files in the same location, and make very similar registry changes. So from what I can tell, a guide for one is a guide for both, if anyone ever creates one. :whistle:

  4. @orustom,

    Sorry, its by design actually. I've noticed that very few people actually use those buttons on MSN, and its more of an unwanted thing for most people.. So I removed it. If there are others who think that the Inbox button is essential, then I'll gladly include it :)

    Btw, if you really want the Inbox button, then you could use Version1 instead.

    Sounds good. IMO the link to the Inbox is the most useful non-messaging-related function of MSN. I'll use version 1. Thanks :thumbup

  5. I really wanna jump on the WinINSTALL LE bandwagon, but it seems like the latest version of WinINSTALL LE required a serial? I thought it was supposed to be a free program. Does anyone know where I can download the previous version that is free?

  6. 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.

    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

    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.

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

    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! :whistle:

    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.

  8. Sorry but I can't really help you on that because I don't use Orca.
    I noticed that he did NOT remove CA_ActivationCheckLicense, which makes me more curious as to what changes he made

    He removed that for sure, because that is the custom action that triggers the activation window. Well, there are other possible ways to disable that. Maybe he didn't remove the action, but he changed the condition so it will not be called. Or maybe he didn't remove it from the table, but he removed it in the execute sequence.

    I have zero experience with editing MSI's, so got no clue what he did. I've been messing with Orca a total of about 2 hours. As an added note, I tried using /qr when installing, and I got further than before. At least the install started this time. Instead though, I end up with it asking me if I want to open the readme file, and then upon trying to launch Photoshop, it says the serial number provided isn't valid (or something to that effect), which is probably normal since I never provided one in the Abcpy.ini file. No sign of any activation wizard yet either.

  9. I edited the MSI by using Orca. All I did was remove that one line called CA_ActivationCheckLicense from the CustomAction section as you suggested we do, and resaved the file.

    Interestingly enough, I get the same result with mrmb's posted MSI. It could be a problem with my setup though. I'm testing in Virtual PC 2004 (w/o SP1). It's NOT a clean install. I've had Photoshop CS installed previously and recently uninstalled it to see if I can get Photoshop CS2 to install silently. Stay tuned for more meaningful results.

    Also, when I open up mrmb's MSI, I noticed that he did NOT remove CA_ActivationCheckLicense, which makes me more curious as to what changes he made, if in fact his MSI works on others' systems.

  10. I edited the MSI file directly to remove CA_ActivationCheckLicense from the CustomAction section of the MSI as per totoymola's suggestion above. I used Orca to do this.

    About to test now. Stay tuned for the feedback... :whistle:

×
×
  • Create New...