Hi ,
Iam doing adobe application. After installing the application, in adobe acrobat element folder, two dll's are present. two dll's have different version. but while installing my application that two dll's which are installed having same version. can any one help me with this issue??
0 Comments   [ + ] Show Comments

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.

Answers

0
Hi,

Let me just confirm your post - You are working on Adobe Acrobat Elements. The application has 2 dll files which are installed to a certain directory location. Both the .dll files are of names & different version. When you install your package both the .dlls are of the same version (whereas in the actual they are of different versions)
Firstly Adobe Acrobat Elements is a vendor msi and you need to create a transform to make your necessary changes (just confirming)
My initial check would be to install the main msi file and confirm the names of the two files and their version. Two different files can have same version. Then I would check by opening the .msi in ORCA or Wise or any tool that you use, confirm the file names, versions, components that they come from and if there are any conditions on the components. I am sure that this would help you to diagnose the problem. I suggest you check them again and re-post in detail if the problem remains unsolved.
Answered 02/17/2008 by: India_Repackaging
Blue Belt

Please log in to comment
0
Do two installs, both with verbose logging - one with your transform and one without - then compare the two logs. That will at least provide a clue as to where the issue lies.
Answered 02/18/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi thanks for your reply.

The problem is if i use short files names (given SHORTFILENAMES=TRUE) in command promt, those two dll's taking same shortfile names and any one of the dll is getting installed. even if i changed the short file for those two dll's it taking same short file name. Without shortfile names it is working fine.

And one more problem is, in verbose log iam gettig an error like " adobepdf.cat might be intalled in [programfilesfolder]\Adobe\ACROBA~1\Acrobat\Xtras\AdobePDF by two different conditionalized component on an SFN system. 'Distiller_Adobepdf.cat_BASE' and 'Distiller_Adobepdf.cat_PRO'. If the conditions are not manually exclusive, this will be break the component reference counting system." Please any one tell me how to solve this issue.
Answered 02/18/2008 by: madhukuti2007
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: madhukuti2007
The problem is if i use short files names (given SHORTFILENAMES=TRUE) in command promt, those two dll's taking same shortfile names and any one of the dll is getting installed. even if i changed the short file for those two dll's it taking same short file name. Without shortfile names it is working fine.

And one more problem is, in verbose log iam gettig an error like " adobepdf.cat might be intalled in [programfilesfolder]\Adobe\ACROBA~1\Acrobat\Xtras\AdobePDF by two different conditionalized component on an SFN system. 'Distiller_Adobepdf.cat_BASE' and 'Distiller_Adobepdf.cat_PRO'. If the conditions are not manually exclusive, this will be break the component reference counting system." Please any one tell me how to solve this issue.
....soooooooo....why use short filenames? You can change the name used anyway, by editing the file table. Here's an example I picked at random from my current client's projects:

PATCHA~1.DLL|PatchApplier.dll

Just edit the section preceding the vertical bar character '|' thus:

PATCHA~2.DLL|PatchApplier.dll

As for the condtionalised components, that will presumably be fixed either by not using short filenames or editing the filename(s) in the same way. Indeed, the relevant component's conditions may make the point moot anyway, which is what the log entry is telling you. It says "IF the conditions are not manually exclusive..." (BTW, was this pasted in directly or typed in by you? I think the message is actually "If the conditions are not mutually exclusive..." - "manually" makes no sense whatsoever.
Answered 02/19/2008 by: VBScab
Red Belt

Please log in to comment
0
thanks for the answer.

But i even changed the shortcut file name.

like CROBA~1.dll|Contextmenu.dll, CROBA~2.dll|Contextmenu64.dll

But both the dll's taking same shortfile name as CROBA~1.dll| and only one dll is installing. what we can do in this case.
Answered 02/20/2008 by: madhukuti2007
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: madhukuti2007
But i even changed the shortcut file name.

like CROBA~1.dll|Contextmenu.dll, CROBA~2.dll|Contextmenu64.dll

But both the dll's taking same shortfile name as CROBA~1.dll| and only one dll is installing. what we can do in this case.
It looks to me like you have a real mess there. Why don't the short filenames use the first 6 characters of the long filename? Surely those entries should be CONTEX~1.dll|Contextmenu.dll, CONTEX~2.dll|Contextmenu64.dll?

Looking at the names themselves, it seems obvious to me that the installation is doing exactly what it was designed to do. Do you not imagine that the second file shown, CONTEX~2.dll|Contextmenu64.dll, might only be installed on a 64-bit operating system? I'm guessing that THAT is the condition which the installer is testing and, as an OS cannot be both 32-bit and 64-bit *at the same time*, it will install only the one file.

I had it in mind to download the package, but then remembered that 'Elements' is some sort of Adobe 'branding' covering a few products so, tell us, WHICH Adobe product are we dealing with: Photoshop Elements? Acrobat Elements? Premier Elements?
Answered 02/21/2008 by: VBScab
Red Belt

Please log in to comment
0
Iam using Adobe Elements. Actually source is installing those two dll's, (contextmenu.dll and contextmenu64.dll) then why not application.
Answered 02/21/2008 by: madhukuti2007
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: madhukuti2007
Iam using Adobe Elements. Actually source is installing those two dll's, (contextmenu.dll and contextmenu64.dll) then why not application.
Once again, Photoshop Elements? Acrobat Elements? Premier Elements?

ORIGINAL: madhukuti2007
Actually source is installing those two dll's, (contextmenu.dll and contextmenu64.dll) then why not application.
I don't understand this at all. 'Source'? 'Application'?
Answered 02/22/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity