photoshop cs3 install fail

Rafaz wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):

I had problem installing CS3 trail before the official CS3 was released, and for some reason I couldn’t be able to get pass the "Agreement". So I had to wait for the official CS3, and even after my CS3 arrived I had to wait for almost 2 weeks reading reports from many difference sources, but none reported the similar problem I had with the CSE Trail.

After almost 2 weeks waiting, I decided to install and this time the installation reported that something was wrong with the IE7 (which I disabled) and recommend to have the IE7 removed for CS3 installation to continue. And it took me few days to find the option to remove IE7 from my system in order to install CS3. I don’t remember the step to remove IE7

Joel wrote:

Rafaz wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):

I had problem installing CS3 trail before the official CS3 was released, and for some reason I couldn’t be able to get pass the "Agreement". So I had to wait for the official CS3, and even after my CS3 arrived I had to wait for almost 2 weeks reading reports from many difference sources, but none reported the similar problem I had with the CSE Trail.
After almost 2 weeks waiting, I decided to install and this time the installation reported that something was wrong with the IE7 (which I disabled) and recommend to have the IE7 removed for CS3 installation to continue. And it took me few days to find the option to remove IE7 from my system in order to install CS3. I don’t remember the step to remove IE7

Removing something as tied into your machine as IE7 is ZERO excuse for Adobe not getting their installer right. We had a horrific mess installing it in our studios too. On about 80% of our machines the installs failed, for no apparent reason. Registry hacks and brute force eventually got it to work. Given we were paying over £1000 a license, and we ordered MANY licenses, I really wish we could have billed Adobe for the time lost. It would have been tens of thousands of £. Their testing department needs to be fired, and actually find someone who can do the job!

I use Creative Suite 3 everywhere… zero issues at all installing it on my Macs. Just Windows machines it doesn’t get along with.

Best trick; run Adobe’s registry clean tool. UNPLUG your machine from the Internet. Remove any antivirus software you have. Make sure you are logged on as Adminstrator. Copy CS3 install media to c:\. Remove and software marked Adobe or Macromedia (including the Flash player). Reboot. Install from the copy you made. With a bit of luck it will work. Reinstall your antivirus. Reboot. Reconnect to the Internet 🙂

This kinda worked for us. Just a horrible experience. Adobe should be ashamed. I’d hate to have been a less skilled home user, or a small studio with no technical person on call.

Having gone through all of that… I still adore PhotoShop CS3 and Flash CS3 and Illustrator CS3. They are VERY good! 🙂

—

x theSpaceGirl (miranda)

http://www.northleithmill.com

-.-

Kammy has a new home: http://www.bitesizedjapan.com

SpaceGirl wrote:

Joel wrote:

Rafaz wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):

I had problem installing CS3 trail before the official CS3 was released,
and for some reason I couldn’t be able to get pass the "Agreement". So I had to wait for the official CS3, and even after my CS3 arrived I had to wait for almost 2 weeks reading reports from many difference sources, but none reported the similar problem I had with the CSE Trail.
After almost 2 weeks waiting, I decided to install and this time the installation reported that something was wrong with the IE7 (which I disabled) and recommend to have the IE7 removed for CS3 installation to continue. And it took me few days to find the option to remove IE7 from my
system in order to install CS3. I don’t remember the step to remove IE7

Removing something as tied into your machine as IE7 is ZERO excuse for Adobe not getting their installer right. We had a horrific mess installing it in our studios too. On about 80% of our machines the installs failed, for no apparent reason. Registry hacks and brute force eventually got it to work. Given we were paying over £1000 a license, and we ordered MANY licenses, I really wish we could have billed Adobe for the time lost. It would have been tens of thousands of £. Their testing department needs to be fired, and actually find someone who can do the job!

I know what your saying, but the information was incorrect, to which you have replied.

It actually says you have IE running please close the program. It says nothing about the removal.

There is nothing different between the trial and having the real thing. It was the botched Beta version that introduced the problems, now that was the bad installer. I could not install, or get a CS3 serial number with my CS2 number to make it work, so I waited till CS3 was finally released.

There are so many reports where the Beta has introduced problems into the final release install, its Adobe themselves and their tricky activation hiding place on the HDD.

I use Creative Suite 3 everywhere… zero issues at all installing it on my Macs. Just Windows machines it doesn’t get along with.
Best trick; run Adobe’s registry clean tool. UNPLUG your machine from the Internet. Remove any antivirus software you have. Make sure you are logged on as Adminstrator. Copy CS3 install media to c:\. Remove and software marked Adobe or Macromedia (including the Flash player). Reboot. Install from the copy you made. With a bit of luck it will work. Reinstall your antivirus. Reboot. Reconnect to the Internet 🙂

That’s a bit over the top, shouldn’t be necessary to carry that out.

This kinda worked for us. Just a horrible experience. Adobe should be ashamed. I’d hate to have been a less skilled home user, or a small studio with no technical person on call.

I have had no problems at all, with installs.

Having gone through all of that… I still adore PhotoShop CS3 and Flash CS3 and Illustrator CS3. They are VERY good! 🙂

Yep for those who haven’t used them should enjoy the experience.

SpaceGirl wrote:

<snip>

Removing something as tied into your machine as IE7 is ZERO excuse for Adobe not getting their installer right. We had a horrific mess installing it in our studios too. On about 80% of our machines the installs failed, for no apparent reason. Registry hacks and brute force eventually got it to work. Given we were paying over £1000 a license, and we ordered MANY licenses, I really wish we could have billed Adobe for the time lost. It would have been tens of thousands of £. Their testing department needs to be fired, and actually find someone who can do the job!

I use Creative Suite 3 everywhere… zero issues at all installing it on my Macs. Just Windows machines it doesn’t get along with.
Best trick; run Adobe’s registry clean tool. UNPLUG your machine from the Internet. Remove any antivirus software you have. Make sure you are logged on as Adminstrator. Copy CS3 install media to c:\. Remove and software marked Adobe or Macromedia (including the Flash player). Reboot. Install from the copy you made. With a bit of luck it will work. Reinstall your antivirus. Reboot. Reconnect to the Internet 🙂

Thanks for the detailed information and I am glad I didn’t have to go that far. And for months I can’t get the beta installed without telling me what was going on, and luckily the final version report IE7 was the one causing problem.

I agree that’s ashamed for company like Adobe to depend on MS to create more problem.

This kinda worked for us. Just a horrible experience. Adobe should be ashamed. I’d hate to have been a less skilled home user, or a small studio with no technical person on call.

Having gone through all of that… I still adore PhotoShop CS3 and Flash CS3 and Illustrator CS3. They are VERY good! 🙂

As part of the testing team, I’m sure glad that I didn’t get fired.

Installation problems did happen by the time the software shipped, and a public beta was activated on December 15th of 2006, and although a few (less than 1/2 of 1%) of installation events did encounter a problem, it was cut to a tenth of that before ship date.

That is no excuse for your having problems — and no attempt at all on my part to diminish the problems (or the costs associated with those problems). I’ve been in the graphic arts industry longer than Adobe (and email, for that matter) and troubles associated with the kind of highly integrated environments that these technologies have generated brings with it a combination of horrific days and days where we get work done that fifteen years ago would have taken twelve times as long using twelve employees instead of two.

You can certainly contact me directly () and I would be
more than happy to work with you and try to figure out what the problem is. Doing that can not only help you feel better about Adobe but would help me
a) avoid the same exact thing happening at some time in our environment and
b) tell others how to avoid it.

But don’t be mad at Adobe. They’re not bad people. And there is no testing ‘department’. Roughly 2000 people wordl wide are chosen as outside testers who represented a wide stroke of markets and environments.

By time the software shipped, there were about 100 left. The drop off happens for a number of reasons, not the least of which is failure to work at making Adobe products work. And they do.

And we don’t get paid (I take that back — I have a signed box with the Creative Suite in it. We also paid for two dozen licenses worldwide for employees, too).

Gary poyssick in tampa, florida and staunch defender of Adobe. Would you trade an easier installation for a camera and type lead? I don’t think so 🙂

On 8/15/07 2:32 AM, in article ,
"Joel" wrote:

SpaceGirl wrote:

<snip>

Removing something as tied into your machine as IE7 is ZERO excuse for Adobe not getting their installer right. We had a horrific mess installing it in our studios too. On about 80% of our machines the installs failed, for no apparent reason. Registry hacks and brute force eventually got it to work. Given we were paying over £1000 a license, and we ordered MANY licenses, I really wish we could have billed Adobe for the time lost. It would have been tens of thousands of £. Their testing department needs to be fired, and actually find someone who can do the job!

I use Creative Suite 3 everywhere… zero issues at all installing it on my Macs. Just Windows machines it doesn’t get along with.
Best trick; run Adobe’s registry clean tool. UNPLUG your machine from the Internet. Remove any antivirus software you have. Make sure you are logged on as Adminstrator. Copy CS3 install media to c:\. Remove and software marked Adobe or Macromedia (including the Flash player). Reboot. Install from the copy you made. With a bit of luck it will work. Reinstall your antivirus. Reboot. Reconnect to the Internet 🙂

Thanks for the detailed information and I am glad I didn’t have to go that far. And for months I can’t get the beta installed without telling me what was going on, and luckily the final version report IE7 was the one causing problem.

I agree that’s ashamed for company like Adobe to depend on MS to create more problem.

This kinda worked for us. Just a horrible experience. Adobe should be ashamed. I’d hate to have been a less skilled home user, or a small studio with no technical person on call.

Having gone through all of that… I still adore PhotoShop CS3 and Flash CS3 and Illustrator CS3. They are VERY good! 🙂

Gary wrote:

As part of the testing team, I’m sure glad that I didn’t get fired.

😀

If you’d be working for me, you would have LOL

Installation problems did happen by the time the software shipped, and a public beta was activated on December 15th of 2006, and although a few (less than 1/2 of 1%) of installation events did encounter a problem, it was cut to a tenth of that before ship date.

All of our issues had nothing to do with the beta. We NEVER install beta software on production machines. It was mostly down two conflicts with the Flash player ("compontent failed to install") and other DLLs, and antivirus. None of this was resolved by Adobe I must add… we spent about a week getting it to work, which required removing of registry entries etc. Now we have some pretty wired technical people in our studio, so we got around it eventually. I would have been seriously pissed if I spent £1000 + on software only to hit the wall of denial we got from the official support at Adobe, and then having to hack my own computer to get the thing to work. If this had been one machine, or even two I’d have put it down to Windows being crap. But this happened on all but 4 of the 30 machines we ran installs on. Each machine had differing configuration, some different Windows versions. Even the AV we’re using isn’t the same on all machines. The only common thing between the machines… was the Adobe installer (Creative Suite 3 Web Edition)

That is no excuse for your having problems — and no attempt at all on my part to diminish the problems (or the costs associated with those problems). I’ve been in the graphic arts industry longer than Adobe (and email, for that matter) and troubles associated with the kind of highly integrated environments that these technologies have generated brings with it a combination of horrific days and days where we get work done that fifteen years ago would have taken twelve times as long using twelve employees instead of two.

That IS no excuse. The products themselves work (IMO) flawlessly. The installer was a nightmare. Bit pointless putting all that effort into wonderful things in PSCS3 (which, I cannot live without now) if you can’t even get it to unpack from DVD in the first place! Whoever was responsible for the building of the installers really let down the rest of the hard working Adobe team – the rest of the product is fantastic!

You can certainly contact me directly () and I would be
more than happy to work with you and try to figure out what the problem is. Doing that can not only help you feel better about Adobe but would help me
a) avoid the same exact thing happening at some time in our environment and
b) tell others how to avoid it.

Well we fixed our issues, eventually.

But don’t be mad at Adobe. They’re not bad people. And there is no testing ‘department’. Roughly 2000 people wordl wide are chosen as outside testers who represented a wide stroke of markets and environments.

Personally I’m VERY mad at Adobe, but also in Love. CS3 has changed the way I work, forever, and for the better. I could never go back. But at the same time I feel really let down. Fantastic products let down by what should have been one of the more simpler parts of the suite… the installer. I’m hardly alone in this… 2 minutes googling will bring back 1000s of reports of issues with the installer. Whatever real world testing was done for installing was clearly hopelessly inadequate.

By time the software shipped, there were about 100 left. The drop off happens for a number of reasons, not the least of which is failure to work at making Adobe products work. And they do.

No software is perfect. That’s not the issue really. Adobe was very slow to react when issues started being reported and… come on… 40 minutes to install a bit of software? That’s just crazy. You can install the whole of Windows in less time. Now try doing that install 6 times in one day because the installer fails every time…

I’m very glad I use Macs at my home studio! 20 minutes install, no problems at all.

And we don’t get paid (I take that back — I have a signed box with the Creative Suite in it. We also paid for two dozen licenses worldwide for employees, too).

Gary poyssick in tampa, florida and staunch defender of Adobe. Would you trade an easier installation for a camera and type lead? I don’t think so 🙂

No, but I won’t let any of my clients or studios upgrade to CS4. Not until the next round of upgrades are proven, no matter how good they are. I’m not going through that headache again!

—

x theSpaceGirl (miranda)

http://www.northleithmill.com

-.-

Kammy has a new home: http://www.bitesizedjapan.com

SpaceGirl ha scritto:

Gary wrote:

As part of the testing team, I’m sure glad that I didn’t get fired.

😀

If you’d be working for me, you would have LOL

Installation problems did happen by the time the software shipped, and a public beta was activated on December 15th of 2006, and although a few (less
than 1/2 of 1%) of installation events did encounter a problem, it was cut
to a tenth of that before ship date.

All of our issues had nothing to do with the beta. We NEVER install beta software on production machines. It was mostly down two conflicts with the Flash player ("compontent failed to install") and other DLLs, and antivirus. None of this was resolved by Adobe I must add… we spent about a week getting it to work, which required removing of registry entries etc. Now we have some pretty wired technical people in our studio, so we got around it eventually. I would have been seriously pissed if I spent £1000 + on software only to hit the wall of denial we got from the official support at Adobe, and then having to hack my own computer to get the thing to work. If this had been one machine, or even two I’d have put it down to Windows being crap. But this happened on all but 4 of the 30 machines we ran installs on. Each machine had differing configuration, some different Windows versions. Even the AV we’re using isn’t the same on all machines. The only common thing between the machines… was the Adobe installer (Creative Suite 3 Web Edition)

That is no excuse for your having problems — and no attempt at all on my part to diminish the problems (or the costs associated with those problems).
I’ve been in the graphic arts industry longer than Adobe (and email, for that matter) and troubles associated with the kind of highly integrated environments that these technologies have generated brings with it a combination of horrific days and days where we get work done that fifteen years ago would have taken twelve times as long using twelve employees instead of two.

That IS no excuse. The products themselves work (IMO) flawlessly. The installer was a nightmare. Bit pointless putting all that effort into wonderful things in PSCS3 (which, I cannot live without now) if you can’t even get it to unpack from DVD in the first place! Whoever was responsible for the building of the installers really let down the rest of the hard working Adobe team – the rest of the product is fantastic!

You can certainly contact me directly () and I
would be
more than happy to work with you and try to figure out what the problem is.
Doing that can not only help you feel better about Adobe but would help me
a) avoid the same exact thing happening at some time in our environment and
b) tell others how to avoid it.

Well we fixed our issues, eventually.

But don’t be mad at Adobe. They’re not bad people. And there is no testing
‘department’. Roughly 2000 people wordl wide are chosen as outside testers
who represented a wide stroke of markets and environments.

Personally I’m VERY mad at Adobe, but also in Love. CS3 has changed the way I work, forever, and for the better. I could never go back. But at the same time I feel really let down. Fantastic products let down by what should have been one of the more simpler parts of the suite… the installer. I’m hardly alone in this… 2 minutes googling will bring back 1000s of reports of issues with the installer. Whatever real world testing was done for installing was clearly hopelessly inadequate.

By time the software shipped, there were about 100 left. The drop off happens for a number of reasons, not the least of which is failure to work
at making Adobe products work. And they do.

No software is perfect. That’s not the issue really. Adobe was very slow to react when issues started being reported and… come on… 40 minutes to install a bit of software? That’s just crazy. You can install the whole of Windows in less time. Now try doing that install 6 times in one day because the installer fails every time…

I’m very glad I use Macs at my home studio! 20 minutes install, no problems at all.

And we don’t get paid (I take that back — I have a signed box with the Creative Suite in it. We also paid for two dozen licenses worldwide for employees, too).

Gary poyssick in tampa, florida and staunch defender of Adobe. Would you trade an easier installation for a camera and type lead? I don’t think so 🙂

No, but I won’t let any of my clients or studios upgrade to CS4. Not until the next round of upgrades are proven, no matter how good they are. I’m not going through that headache again!

"I hate and (yet) I love" (in Latin, Odi et amo) was written by the Roman poet Catullus for his mistress Lesbia
🙂
Jokes apart…
I’ve tried to install PSCS3 without the firewall and without the anti-virus. I’ve erased any possible reference about Adobe in any folder and in any register-key. The only thing I can do now is a low level format of HDD or erase the hidden info Adobe written on my HDD (but I don’t know where). Nevertheless I think the problem is on a missed path value. Here follow a part of 2 logs, the first generated from the installer on my PC (failed), the second one generated from the installer on another PC (win XP pro like mine) (success)

wrong
=====
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey0000000100000005Value00000000000000020000000100000004Nam e00000009AdobeCode0000000100000005Value00000038{2E4528EC-5AC B-4D19-98DD-6CC3594EB1A1}000000020000000100000004Name0000001 9LanguageIndependent0000000100000005Value000000011
(Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey
(Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library:
(Adobe) Path does not exist
(Adobe) #_AdobeError_# 1603
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

right
=====

(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey0000000100000005Value00000081C:\Programmi\File
comuni\Adobe\Adobe Anchor
Service\adobelm_service_installer.dll00000002000000010000000 4Name00000009AdobeCode0000000100000005Value00000038{2E4528EC -5ACB-4D19-98DD-6CC3594EB1A1}000000020000000100000004Name000 00019LanguageIndependent0000000100000005Value000000011
(Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library: C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) AdobeCode: {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} Language: ALL Mode: 1
(Adobe) Installing ALM…
[ 2116] Tue Jul 31 10:35:16 2007 INFO
(Adobe) ALM return code: 0
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

as you can see the path value "C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll" is missing on the "ALMInstallLibFileKey " variable.
I looked for this value on *.xml files of the installation package but nothing… 🙁

I didn’t want to indicate I didn’t feel bad for you, SpaceGirl — the worst part of the entire process; two years in alpha, beta, then gamma were troubled with installer problems. I’ll probably get hung for saying this, but some of us on the beta teams felt that a Suite-wide installer waited waaaaaayyyyyyy to long to appear. During the two year process, each team has its own installers.

That sounds really stupid at first glance, but let me explain a little bit; and again, I’m not an Adobe employee — I’ve just been testing since the first 11 Type1 fonts (no software yet).

And none of this will make you less pissed at Adobe — just perhaps more understanding. The fact that you still love the software despite the problems is cool enough 🙂

When the beta teams start working on new software, they’re really a standalone group. They have their own specific product managers, their own engineering teams, and their own agendas. Most importantly to this discussion is that they have — and select personally for a wide variety of reasons — their own testing teams. Although Macromedia’s absorption into the Adobe family had some impact (the public beta was purely a MM thing; Adobe would never had let anybody see Photoshop before it was shipped), overall the process remained the same. Product managers ran the engineering teams and personally — like sign the papers personally — approve of any prior or newly suggested testers.

Those people then get invited, sign 12 pounds of deadly-results non-disclosures, and get the software. Sometimes new ‘builds’ — new versions — come out every few weeks. Other times they could come 4 a day for a week. Build releases depend on a lot of issues, but suffice it to say that individual serial numbers, and raw — in some cases literally — applications begin getting passed around. The security is insane, and still doesn’t stop the mob (of all flavors) from selling the software for $80 two weeks after release.

So lots of testers — most, in fact — don’t have access to entire ‘suites’. The problem doesn’t appear — and didn’t this time around — because nobody is installing all the apps as they were going to appear in the suites. Don’t forget — Flash and Dreamweaver and Fireworks caused major structural changes to the offerings from Adobe, not to mention the fact that the underlying code was rewritten to run on Universal Intel machines.

Testers were yelling about the cross-application installer problems, believe me SpaceGirl. And I’m personally really sorry that the process brought you stress. But there were 12 apps being betad all at the same time, and the suite installers didn’t appear until December 2006.

That having been (all) said, now that a cross-platform installer exists, it will never need to be created again. The problem will disappear at all levels before CS4 sees the ground.

Am I politically acceptable again???

On 8/15/07 12:52 PM, in article ,
"SpaceGirl" wrote:

Gary wrote:

As part of the testing team, I’m sure glad that I didn’t get fired.

😀

If you’d be working for me, you would have LOL

Installation problems did happen by the time the software shipped, and a public beta was activated on December 15th of 2006, and although a few (less than 1/2 of 1%) of installation events did encounter a problem, it was cut to a tenth of that before ship date.

All of our issues had nothing to do with the beta. We NEVER install beta software on production machines. It was mostly down two conflicts with the Flash player ("compontent failed to install") and other DLLs, and antivirus. None of this was resolved by Adobe I must add… we spent about a week getting it to work, which required removing of registry entries etc. Now we have some pretty wired technical people in our studio, so we got around it eventually. I would have been seriously pissed if I spent £1000 + on software only to hit the wall of denial we got from the official support at Adobe, and then having to hack my own computer to get the thing to work. If this had been one machine, or even two I’d have put it down to Windows being crap. But this happened on all but 4 of the 30 machines we ran installs on. Each machine had differing configuration, some different Windows versions. Even the AV we’re using isn’t the same on all machines. The only common thing between the machines… was the Adobe installer (Creative Suite 3 Web Edition)

That is no excuse for your having problems — and no attempt at all on my part to diminish the problems (or the costs associated with those problems). I’ve been in the graphic arts industry longer than Adobe (and email, for that matter) and troubles associated with the kind of highly integrated environments that these technologies have generated brings with it a combination of horrific days and days where we get work done that fifteen years ago would have taken twelve times as long using twelve employees instead of two.

That IS no excuse. The products themselves work (IMO) flawlessly. The installer was a nightmare. Bit pointless putting all that effort into wonderful things in PSCS3 (which, I cannot live without now) if you can’t even get it to unpack from DVD in the first place! Whoever was responsible for the building of the installers really let down the rest of the hard working Adobe team – the rest of the product is fantastic!

You can certainly contact me directly () and I would be
more than happy to work with you and try to figure out what the problem is. Doing that can not only help you feel better about Adobe but would help me
a) avoid the same exact thing happening at some time in our environment and
b) tell others how to avoid it.

Well we fixed our issues, eventually.

But don’t be mad at Adobe. They’re not bad people. And there is no testing ‘department’. Roughly 2000 people wordl wide are chosen as outside testers who represented a wide stroke of markets and environments.

Personally I’m VERY mad at Adobe, but also in Love. CS3 has changed the way I work, forever, and for the better. I could never go back. But at the same time I feel really let down. Fantastic products let down by what should have been one of the more simpler parts of the suite… the installer. I’m hardly alone in this… 2 minutes googling will bring back 1000s of reports of issues with the installer. Whatever real world testing was done for installing was clearly hopelessly inadequate.

By time the software shipped, there were about 100 left. The drop off happens for a number of reasons, not the least of which is failure to work at making Adobe products work. And they do.

No software is perfect. That’s not the issue really. Adobe was very slow to react when issues started being reported and… come on… 40 minutes to install a bit of software? That’s just crazy. You can install the whole of Windows in less time. Now try doing that install 6 times in one day because the installer fails every time…

I’m very glad I use Macs at my home studio! 20 minutes install, no problems at all.

And we don’t get paid (I take that back — I have a signed box with the Creative Suite in it. We also paid for two dozen licenses worldwide for employees, too).

Gary poyssick in tampa, florida and staunch defender of Adobe. Would you trade an easier installation for a camera and type lead? I don’t think so 🙂

No, but I won’t let any of my clients or studios upgrade to CS4. Not until the next round of upgrades are proven, no matter how good they are. I’m not going through that headache again!

Gary wrote:

I didn’t want to indicate I didn’t feel bad for you, SpaceGirl — the worst part of the entire process; two years in alpha, beta, then gamma were troubled with installer problems. I’ll probably get hung for saying this, but some of us on the beta teams felt that a Suite-wide installer waited waaaaaayyyyyyy to long to appear. During the two year process, each team has its own installers.

I see!

That sounds really stupid at first glance, but let me explain a little bit; and again, I’m not an Adobe employee — I’ve just been testing since the first 11 Type1 fonts (no software yet).

And none of this will make you less pissed at Adobe — just perhaps more understanding. The fact that you still love the software despite the problems is cool enough 🙂

I spent the last two hours working with SmartObjects between IllyCS3 and PSCS3 and copying stuff into Flash for reuse… how can I be pissed at Adobe when stuff like this is even possible? 😀 Love it love love it!

When the beta teams start working on new software, they’re really a standalone group. They have their own specific product managers, their own engineering teams, and their own agendas. Most importantly to this discussion is that they have — and select personally for a wide variety of reasons — their own testing teams.

I wish that it was possible to install individual apps from inside CS3. If you try run the MSI’s by hand (on Windows) it complains and won’t accept the serial number of the whole sweet. That was very poor I thought… there was no work around. I couldn’t just Install Illy + PS + Flash one at a time. It was "use the suite installer, which doesn’t work, or nothing". I spent two weeks with a beatifully boxes copy of CS3 sat on my desk, while doing production work in CS2! That sucked after all the hype… plus having put my neck on the line justifying the huge spend on upgrading! ah well, it all worked out 😀

Although Macromedia’s absorption into
the Adobe family had some impact (the public beta was purely a MM thing; Adobe would never had let anybody see Photoshop before it was shipped), overall the process remained the same. Product managers ran the engineering teams and personally — like sign the papers personally — approve of any prior or newly suggested testers.

Okay…

Those people then get invited, sign 12 pounds of deadly-results non-disclosures, and get the software. Sometimes new ‘builds’ — new versions — come out every few weeks. Other times they could come 4 a day for a week. Build releases depend on a lot of issues, but suffice it to say that individual serial numbers, and raw — in some cases literally — applications begin getting passed around. The security is insane, and still doesn’t stop the mob (of all flavors) from selling the software for $80 two weeks after release.

Yeah I saw lots of leaks online, but that’s what happens when you are so popular! Everyone wants a bit of you one way or another.

So lots of testers — most, in fact — don’t have access to entire ‘suites’. The problem doesn’t appear — and didn’t this time around — because nobody is installing all the apps as they were going to appear in the suites. Don’t forget — Flash and Dreamweaver and Fireworks caused major structural changes to the offerings from Adobe, not to mention the fact that the underlying code was rewritten to run on Universal Intel machines.

Seems more of a recompile. DWCS3 smacks of not having time to finish it. It’s one of the weak points in the suite, with the horrible old UI. They managed with Flash though!

Testers were yelling about the cross-application installer problems, believe me SpaceGirl. And I’m personally really sorry that the process brought you stress. But there were 12 apps being betad all at the same time, and the suite installers didn’t appear until December 2006.

Oh I totally understand it must have been a vast and horrible process. Even the relatively tiny projects I get involved in have me tearing my hair out at times, despite our testers, project managers, betas…. blah

That having been (all) said, now that a cross-platform installer exists, it will never need to be created again. The problem will disappear at all levels before CS4 sees the ground.

Am I politically acceptable again???

You never weren’t sweetie 🙂 It’s nice to have someone who was involved in the product actually here, I didn’t want to chase you off 🙂

—

x theSpaceGirl (miranda)

http://www.northleithmill.com

-.-

Kammy has a new home: http://www.bitesizedjapan.com

Rafaz wrote:

<snip>

"I hate and (yet) I love" (in Latin, Odi et amo) was written by the Roman poet Catullus for his mistress Lesbia
🙂
Jokes apart…
I’ve tried to install PSCS3 without the firewall and without the anti-virus. I’ve erased any possible reference about Adobe in any folder and in any register-key. The only thing I can do now is a low level format of HDD or erase the hidden info Adobe written on my HDD (but I don’t know where). Nevertheless I think the problem is on a missed path value. Here follow a part of 2 logs, the first generated from the installer on my PC (failed), the second one generated from the installer on another PC (win XP pro like mine) (success)

I did have to go that far by disabling firewall, anti-virus, safe-mode but just can’t be able to install the BETA version, and it never reported what the problem was. And luckily the final version reported it had some issue with IE7 and I was able to remove and be able to install CS3.

Gary ha scritto:

I didn’t want to indicate I didn’t feel bad for you, SpaceGirl — the worst part of the entire process; two years in alpha, beta, then gamma were troubled with installer problems. I’ll probably get hung for saying this, but some of us on the beta teams felt that a Suite-wide installer waited waaaaaayyyyyyy to long to appear. During the two year process, each team has its own installers.

That sounds really stupid at first glance, but let me explain a little bit; and again, I’m not an Adobe employee — I’ve just been testing since the first 11 Type1 fonts (no software yet).

And none of this will make you less pissed at Adobe — just perhaps more understanding. The fact that you still love the software despite the problems is cool enough 🙂

When the beta teams start working on new software, they’re really a standalone group. They have their own specific product managers, their own engineering teams, and their own agendas. Most importantly to this discussion is that they have — and select personally for a wide variety of reasons — their own testing teams. Although Macromedia’s absorption into the Adobe family had some impact (the public beta was purely a MM thing; Adobe would never had let anybody see Photoshop before it was shipped), overall the process remained the same. Product managers ran the engineering teams and personally — like sign the papers personally — approve of any prior or newly suggested testers.

Those people then get invited, sign 12 pounds of deadly-results non-disclosures, and get the software. Sometimes new ‘builds’ — new versions — come out every few weeks. Other times they could come 4 a day for a week. Build releases depend on a lot of issues, but suffice it to say that individual serial numbers, and raw — in some cases literally — applications begin getting passed around. The security is insane, and still doesn’t stop the mob (of all flavors) from selling the software for $80 two weeks after release.

So lots of testers — most, in fact — don’t have access to entire ‘suites’. The problem doesn’t appear — and didn’t this time around — because nobody is installing all the apps as they were going to appear in the suites. Don’t forget — Flash and Dreamweaver and Fireworks caused major structural changes to the offerings from Adobe, not to mention the fact that the underlying code was rewritten to run on Universal Intel machines.
Testers were yelling about the cross-application installer problems, believe me SpaceGirl. And I’m personally really sorry that the process brought you stress. But there were 12 apps being betad all at the same time, and the suite installers didn’t appear until December 2006.

That having been (all) said, now that a cross-platform installer exists, it will never need to be created again. The problem will disappear at all levels before CS4 sees the ground.

Am I politically acceptable again???

On 8/15/07 12:52 PM, in article ,
"SpaceGirl" wrote:

Gary wrote:

As part of the testing team, I’m sure glad that I didn’t get fired.

😀

If you’d be working for me, you would have LOL

Installation problems did happen by the time the software shipped, and a public beta was activated on December 15th of 2006, and although a few (less than 1/2 of 1%) of installation events did encounter a problem, it was cut to a tenth of that before ship date.

All of our issues had nothing to do with the beta. We NEVER install beta software on production machines. It was mostly down two conflicts with the Flash player ("compontent failed to install") and other DLLs, and antivirus. None of this was resolved by Adobe I must add… we spent about a week getting it to work, which required removing of registry entries etc. Now we have some pretty wired technical people in our studio, so we got around it eventually. I would have been seriously pissed if I spent £1000 + on software only to hit the wall of denial we got from the official support at Adobe, and then having to hack my own computer to get the thing to work. If this had been one machine, or even two I’d have put it down to Windows being crap. But this happened on all but 4 of the 30 machines we ran installs on. Each machine had differing configuration, some different Windows versions. Even the AV we’re using isn’t the same on all machines. The only common thing between the machines… was the Adobe installer (Creative Suite 3 Web Edition)

That is no excuse for your having problems — and no attempt at all on my part to diminish the problems (or the costs associated with those problems). I’ve been in the graphic arts industry longer than Adobe (and email, for that matter) and troubles associated with the kind of highly integrated environments that these technologies have generated brings with it a combination of horrific days and days where we get work done that fifteen years ago would have taken twelve times as long using twelve employees instead of two.

That IS no excuse. The products themselves work (IMO) flawlessly. The installer was a nightmare. Bit pointless putting all that effort into wonderful things in PSCS3 (which, I cannot live without now) if you can’t even get it to unpack from DVD in the first place! Whoever was responsible for the building of the installers really let down the rest of the hard working Adobe team – the rest of the product is fantastic!

You can certainly contact me directly () and I would be
more than happy to work with you and try to figure out what the problem is. Doing that can not only help you feel better about Adobe but would help me
a) avoid the same exact thing happening at some time in our environment and
b) tell others how to avoid it.

Well we fixed our issues, eventually.

But don’t be mad at Adobe. They’re not bad people. And there is no testing ‘department’. Roughly 2000 people wordl wide are chosen as outside testers who represented a wide stroke of markets and environments.

Personally I’m VERY mad at Adobe, but also in Love. CS3 has changed the way I work, forever, and for the better. I could never go back. But at the same time I feel really let down. Fantastic products let down by what should have been one of the more simpler parts of the suite… the installer. I’m hardly alone in this… 2 minutes googling will bring back 1000s of reports of issues with the installer. Whatever real world testing was done for installing was clearly hopelessly inadequate.

By time the software shipped, there were about 100 left. The drop off happens for a number of reasons, not the least of which is failure to work at making Adobe products work. And they do.

No software is perfect. That’s not the issue really. Adobe was very slow to react when issues started being reported and… come on… 40 minutes to install a bit of software? That’s just crazy. You can install the whole of Windows in less time. Now try doing that install 6 times in one day because the installer fails every time…

I’m very glad I use Macs at my home studio! 20 minutes install, no problems at all.

And we don’t get paid (I take that back — I have a signed box with the Creative Suite in it. We also paid for two dozen licenses worldwide for employees, too).

Gary poyssick in tampa, florida and staunch defender of Adobe. Would you trade an easier installation for a camera and type lead? I don’t think so 🙂

No, but I won’t let any of my clients or studios upgrade to CS4. Not until the next round of upgrades are proven, no matter how good they are. I’m not going through that headache again!

I think your discussion was out of the meaning of the main problem. I think Gary was the right man at the right place at the right time for the solution I need. Please have you any idea/solution about my problem? thanks

Hey Raf. I just found your response this morning, and I jumped in for the Cat Woman and never even saw yours. Sorry bout that. And thanks for your kind words — our team just came off of writing 2000 pages of training content, and I’m happy to spend time up here with what I hope are humans (never know inside this place 🙂 )

I really think — and this was certainly the case internally with Adobe’s testing teams — that this is all related either to the path issue you bring up or to the installer’s inability at some level to find something it (thinks) it needs.

If you’re on a Windows machine (Vista included) go to the Applications Add/Remove and remove Adobe xxxxx (I’m assuming it’s photoshop, but if you’re running (or almost running) the Suite, then do them all one at a time.

If you’re on a Macintosh we were provided an uninstaller app, which can be found in App support somewhere — I think inside the Application Support/Adobe/Uninstall. Run it.

The invisible, hidden files every one is talking about — and the ones at the basis of this problem — happen with all applications. There’s more junk laying around your system then you could ever imaging (although judging by the somewhat (?!) technical issue you’re providing here, you know that already.

Don’t try to find Adobe stuff and get rid of it — just do the Win or Mac uninstalls, and all will be well.

That’s the same to 99% of the problems I’ve seen here. Even the catwoman’s maybe 🙂 In the case of the trial, just uninstall the trial version that’s there — the uninstaller is one of the first things that gets put on your box, so it should be there (Mac users; Win or Vista comes with its own).

g

On 8/13/07 5:31 AM, in article MxVvi.24085$,
"Rafaz" wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):
wrong
=====
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey00000001000000 05Value00000000000000020000000100000004Name00000009AdobeCode 0000000100000005Va lue00000038{2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1}00000002000 0000100000004Name0 0000019LanguageIndependent0000000100000005Value000000011 (Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey
(Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library:
(Adobe) Path does not exist
(Adobe) #_AdobeError_# 1603
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

right
=====

(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey00000001000000 05Value00000081C:\Programmi\File
comuni\Adobe\Adobe Anchor
Service\adobelm_service_installer.dll00000002000000010000000 4Name00000009Adobe Code0000000100000005Value00000038{2E4528EC-5ACB-4D19-98DD-6C C3594EB1A1}0000000 20000000100000004Name00000019LanguageIndependent000000010000 0005Value000000011 (Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library: C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) AdobeCode: {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} Language: ALL Mode: 1
(Adobe) Installing ALM…
[ 2116] Tue Jul 31 10:35:16 2007 INFO
(Adobe) ALM return code: 0
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

Anyone can help me, please?
Many thanks

Gary ha scritto:

Hey Raf. I just found your response this morning, and I jumped in for the Cat Woman and never even saw yours. Sorry bout that. And thanks for your kind words — our team just came off of writing 2000 pages of training content, and I’m happy to spend time up here with what I hope are humans (never know inside this place 🙂 )

I really think — and this was certainly the case internally with Adobe’s testing teams — that this is all related either to the path issue you bring up or to the installer’s inability at some level to find something it (thinks) it needs.

If you’re on a Windows machine (Vista included) go to the Applications Add/Remove and remove Adobe xxxxx (I’m assuming it’s photoshop, but if you’re running (or almost running) the Suite, then do them all one at a time.

If you’re on a Macintosh we were provided an uninstaller app, which can be found in App support somewhere — I think inside the Application Support/Adobe/Uninstall. Run it.

The invisible, hidden files every one is talking about — and the ones at the basis of this problem — happen with all applications. There’s more junk laying around your system then you could ever imaging (although judging by the somewhat (?!) technical issue you’re providing here, you know that already.

Don’t try to find Adobe stuff and get rid of it — just do the Win or Mac uninstalls, and all will be well.

That’s the same to 99% of the problems I’ve seen here. Even the catwoman’s maybe 🙂 In the case of the trial, just uninstall the trial version that’s there — the uninstaller is one of the first things that gets put on your box, so it should be there (Mac users; Win or Vista comes with its own).
g

On 8/13/07 5:31 AM, in article MxVvi.24085$,
"Rafaz" wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):
wrong
=====
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey00000001000000 05Value00000000000000020000000100000004Name00000009AdobeCode 0000000100000005Va lue00000038{2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1}00000002000 0000100000004Name0 0000019LanguageIndependent0000000100000005Value000000011 (Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey
(Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library:
(Adobe) Path does not exist
(Adobe) #_AdobeError_# 1603
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

right
=====

(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey00000001000000 05Value00000081C:\Programmi\File
comuni\Adobe\Adobe Anchor
Service\adobelm_service_installer.dll00000002000000010000000 4Name00000009Adobe Code0000000100000005Value00000038{2E4528EC-5ACB-4D19-98DD-6C C3594EB1A1}0000000 20000000100000004Name00000019LanguageIndependent000000010000 0005Value000000011 (Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library: C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) AdobeCode: {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} Language: ALL Mode: 1
(Adobe) Installing ALM…
[ 2116] Tue Jul 31 10:35:16 2007 INFO
(Adobe) ALM return code: 0
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

Anyone can help me, please?
Many thanks

The uninstall by control panel was the first trial I performed (obviously). Following I used the Adobe’s cleaner script.

Did the trial work OK? I’m trying not to sound stupid — just trying to isolate the issue. I thought that the trial worked until you had a real serial number, then you could activate it.

Have you tried re-downloading the trial and using your now-new serial number on it? And have you been running CS2 apps on the same machine? Has it happened on more than one machine on the same network?

g

On 8/17/07 10:45 AM, in article Avixi.447$,
"Rafaz" wrote:

Gary ha scritto:

Hey Raf. I just found your response this morning, and I jumped in for the Cat Woman and never even saw yours. Sorry bout that. And thanks for your kind words — our team just came off of writing 2000 pages of training content, and I’m happy to spend time up here with what I hope are humans (never know inside this place 🙂 )

I really think — and this was certainly the case internally with Adobe’s testing teams — that this is all related either to the path issue you bring up or to the installer’s inability at some level to find something it (thinks) it needs.

If you’re on a Windows machine (Vista included) go to the Applications Add/Remove and remove Adobe xxxxx (I’m assuming it’s photoshop, but if you’re running (or almost running) the Suite, then do them all one at a time.

If you’re on a Macintosh we were provided an uninstaller app, which can be found in App support somewhere — I think inside the Application Support/Adobe/Uninstall. Run it.

The invisible, hidden files every one is talking about — and the ones at the basis of this problem — happen with all applications. There’s more junk laying around your system then you could ever imaging (although judging by the somewhat (?!) technical issue you’re providing here, you know that already.

Don’t try to find Adobe stuff and get rid of it — just do the Win or Mac uninstalls, and all will be well.

That’s the same to 99% of the problems I’ve seen here. Even the catwoman’s maybe 🙂 In the case of the trial, just uninstall the trial version that’s there — the uninstaller is one of the first things that gets put on your box, so it should be there (Mac users; Win or Vista comes with its own).
g

On 8/13/07 5:31 AM, in article MxVvi.24085$,
"Rafaz" wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):
wrong
=====
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey000000010000 00
05Value00000000000000020000000100000004Name00000009AdobeCode 0000000100000005 Va
lue00000038{2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1}00000002000 0000100000004Nam e0
0000019LanguageIndependent0000000100000005Value000000011 (Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey
(Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library:
(Adobe) Path does not exist
(Adobe) #_AdobeError_# 1603
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

right
=====

(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- BEGIN – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-
(Adobe) Requesting property: CustomActionData
(Adobe) Value
00000003000000020000000100000004Name00000020ALMInstallLibFil eKey000000010000 00
05Value00000081C:\Programmi\File
comuni\Adobe\Adobe Anchor
Service\adobelm_service_installer.dll00000002000000010000000 4Name00000009Ado be
Code0000000100000005Value00000038{2E4528EC-5ACB-4D19-98DD-6C C3594EB1A1}00000 00
20000000100000004Name00000019LanguageIndependent000000010000 0005Value0000000 11
(Adobe) Allocating istringstream:
(Adobe) Stream extraction to recordset
(Adobe) Number of Properties: 3
(Adobe) Name, Value: ALMInstallLibFileKey C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) Name, Value: AdobeCode {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} (Adobe) Name, Value: LanguageIndependent 1
(Adobe) ALM language: ALL
(Adobe) Path to ALM installer library: C:\Programmi\File comuni\Adobe\Adobe Anchor Service\adobelm_service_installer.dll (Adobe) AdobeCode: {2E4528EC-5ACB-4D19-98DD-6CC3594EB1A1} Language: ALL Mode: 1
(Adobe) Installing ALM…
[ 2116] Tue Jul 31 10:35:16 2007 INFO
(Adobe) ALM return code: 0
(Adobe) -*-*-*-*-*-*-*-*-*-*-*-*- END – Adobe_InstallALMService -*-*-*-*-*-*-*-*-*-*-*-*-

Anyone can help me, please?
Many thanks

The uninstall by control panel was the first trial I performed (obviously). Following I used the Adobe’s cleaner script.

Gary schreef op 17-08-2007 22:28:

I’m trying not to sound stupid

Than just quote the good way. 🙂
<http://www.netmeister.org/news/learn2quote.html>

—
Mvg, ßiagio®

I am not overly fond of MS or IE 7 so we ran a script that prevents our machines from downloading IE 7 and we have not had any problems installing the trial products nor the actual purchased software.

"SpaceGirl" wrote in message

Joel wrote:

Rafaz wrote:

Hi, I tried to install photoshop cs3 trial but the Adobe License Manager fail the installation caused by a missing path, here follows my installation log and a correct installation log (to compare):

I had problem installing CS3 trail before the official CS3 was released, and for some reason I couldn’t be able to get pass the "Agreement". So I had to wait for the official CS3, and even after my CS3 arrived I had to wait for almost 2 weeks reading reports from many difference sources, but none reported the similar problem I had with the CSE Trail.
After almost 2 weeks waiting, I decided to install and this time the installation reported that something was wrong with the IE7 (which I disabled) and recommend to have the IE7 removed for CS3 installation to continue. And it took me few days to find the option to remove IE7 from my
system in order to install CS3. I don’t remember the step to remove IE7

Removing something as tied into your machine as IE7 is ZERO excuse for Adobe not getting their installer right. We had a horrific mess installing it in our studios too. On about 80% of our machines the installs failed, for no apparent reason. Registry hacks and brute force eventually got it to work. Given we were paying over

Rob wrote:

<snip>

I know what your saying, but the information was incorrect, to which you have replied.

Actually your firmed info is incorrect (it’s a normal thing often happen to many others)

It actually says you have IE running please close the program. It says nothing about the removal.

In most cases then YES you are right, but you are wrong because you never run into problem others have to have the experience others do.

For long time, I read so much information about IE6 and IE7 can’t be uninstalled. And I don’t know if there is any difference between "uninstall" and "remove" or not, but I have to GOOGLE for the option to "REMOVE" IE7 from my system in order to install CS3.

And believe it or not, I was able to install CS3 after did the remove option (little different than uninstall), and IE (I don’t use IE often to check if it’s IE6 or IE7?) is still on my system. Or I have no idea what "Remove" did … may be it remove IE7 and restored IE6?

There is nothing different between the trial and having the real thing. It was the botched Beta version that introduced the problems, now that was the bad installer. I could not install, or get a CS3 serial number with my CS2 number to make it work, so I waited till CS3 was finally released.

Believe it or not! there may not much different *but* there is some. Cuz I had run into both

– CS3 beta, for months I just can’t get pass the "Agreement" window. The CS3 beta didn’t report anything, it just didn’t give me the "OK" to continue the installation *but* "CANCEL" option only.

– CS3 final, I didn’t dare to install CS3 but spent almost 2 weeks to search for installing problem, and didn’t find anything close to what I had. I then decided to install CS3 and this time it reported IE7 problem and suggested me to have it removed for CS3 to continue the installation.

There are so many reports where the Beta has introduced problems into the final release install, its Adobe themselves and their tricky activation hiding place on the HDD.

Joel wrote:

Rob wrote:

<snip>

I know what your saying, but the information was incorrect, to which you have replied.

I have now encountered problems with installing the Web Premium DVD, although I have some separate parts installed. PS, DW and Fl.

All I wanted to see if there was anything worthwhile in Illustrator CS3 as I’ve been using CS2 version.

I get up an Internet Explorer box Critical error incorrect payloads and to check the install log.

My reply from Adobe was

http://www.adobe.com/go/kb400615

and to follow the instructions.

and this may sort out most of the install problems.

r