Jump to content

Recommended Posts

Posted

Has anybody successfully installed Macromedia Studio MX 2004 on x64 (ideally Server 2003)?

 

This is a bit of a killer app for me moving to x64 terminal servers so any suggestions would be welcomed. The error I get when trying to install is a problem copying iKernel.exe (or similar) to the Program Files (x86) folder. I'm purely guessing but I think that this is simply an InstallShield problem. :(

Posted

@kmount: I don't know why I didn't think of trying that... alas it does not work though. Exxactly the same message so the MSI must simply be a wrapper for InstallShield.

 

Any other ideas?

Posted

Hmm, just looking at ours (mind you, cc3 package..) and the MSI seem to be legit..

 

Maybe extract the msi and see if there's something 'else' asides from the installshield.

Posted
@kmount: I've tried it from a share, a mapped drive and a local drive too to no avail. I am re-installing the machine with 32bit because I need it up for next week... I have another that I can afford to keep out of my Citrix farm for now so I will give it a blast on that when I get time.
Posted

Hi

 

When I was at Carr Hill I spent hours trying to get this to work and had to install it by hand and put the key in to every computer on the curric network.

 

So goo luck with this one and if you do find a solution please could you let me know.

 

Richard

Posted
Hi

 

When I was at Carr Hill I spent hours trying to get this to work and had to install it by hand and put the key in to every computer on the curric network.

 

So goo luck with this one and if you do find a solution please could you let me know.

 

Richard

 

You were installing onto 32 or 64 bit?

Posted
I have mine fully automated at the end of a RIS build with a log on. I seperated alll the seperate programs and made answer files for them. I use a reg import to sort the key but you must run flash first for it to work. Using the same method you can use an MSI wrapper to install them as well I believe. I am sure theres an old post around here somewhere about it.
Posted
Looks like it could be a problem with the wrapper and, at least in the instance of the kb article their solution is an unwrapped installation. It may be an idea to contact them to see if they have one of these avalible for your software.

 

This is correct, it will work if you unwrap it.

Posted
This is correct, it will work if you unwrap it.

 

If you could enlighten me as to how to perform this unwrapping I would be very grateful!

 

At the moment I use the separate installers as ChrisH mentions and then a reg import for the key. It's just that all the installers use this same wrapper (not just the one for installing everything together).

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...