Hi all..! I'm going to have to repackage PalmOne's Palm desktop 4.1.4. I read up on it first and it seems to be an Installshield MSI.. Extracted contents, but the ways to bypass the Installshield installer so the MSI can be transformed and deployed using sms don't seem to work with version 11 of the installshield installscript client. So.. That leaves me with some options..

* Make a vbscript to install the Installshield client first, then install the transformed MSI.. (self repair using advertised shortcut and full control on the program files\
palm directory for users, haven't tried this before, see if it works)
* repackage the complete install..
* Install the ISScript engine, install package, try to uninstall isscript engine.. (i read this can't be done?!?)

I don't think either options are good.. Never repackage an MSI is one of the first rules of repackaging so... And i basically don't want the Instalshield client installed on my clients.. So any ideas on how to go about it, i'm open to suggestions.. :P
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 neo,
please read this: http://www.appdeploy.com/packages/detail.asp?id=162
and this: http://www.appdeploy.com/messageboards/tm.asp?m=18826

Then, eliminate the ISScript MSI by integrating the merge module.
Then make the package multi-user compatible by moving the HKCU reg-entries to separate features.
Use this guide: http://itninja.com/question/distribution-message21
to use self healing or Active Setup bring the user settings to the profiles.
Hope, this gives you the ideas to do it.
Regards, Nick
Answered 08/18/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Installshield MSI horror

isnt it funny how these words seem to be at home together when used in the same sentence.
Answered 08/20/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Hate to be a nay-sayer, but good luck with that one.

I've tried numerous times to repackage it (including the documented methods on this site), and numerous times to deploy it silently with the vendor install, and the only way I've ever gotten it to work was in an environment where all users were local admins, and I ran the install with user rights.

It's an ugly beast.
Answered 08/21/2007 by: Bladerun
Green Belt

Please log in to comment
2
I did manage to create a transform for using Palm Desktop on a multi user client.
Here are some notes I saved during this task, have in mind that it was some time I did this so can't recall exactly.

You will need to install the "Palm USB Driver" using the DIFxApp merge module or DPInst32.exe (32-bit DPInst.exe) / DPInst64.exe (64-bit DPInst.exe). The required files are: PalmDevC.dll, palmusbd.cat, PalmUSBD.inf and PalmUSBD.sys.
I used DPInst.exe with parameters "/sa /q /f" during install and "[#DPInst.exe] /u PalmUSBD.inf /d /q" for uninstall.

I recall from somewhere that you can change where the palm user folder should be created which would prevent open up security permission on the whole "%ProgramFiles%\PalmOne" folder, just can't find the info for that right now.

Before installing PalmDesktop.msi you will need to install isscript.msi (ISScript 7.4.0.377).
I tip regarding validating your own modification (transform).
First validate PalmDesktop.msi using ORCA and save the result to a text file.
Then apply the transform, save the result to another file and make a diff on these two.
The once that differs are your modifications from the transform.

1. Install the application on a test client
2. Extract the HKCU\Software registry for Palm and "U.S. Robotics" to a .REG file
3. Edit the .REG file and change hard-coded values to property instead
4. Create an MST file
- Import the HKCU.REG (CurrentUser Component)
Remove the "HotSync Manager" shortcut from the "\<install user>\Start Menu\Programs\Startup"
(seems to be created by a InstallShield custom action, so remove it after InstallFinalize)
- Change HKLM..\run entry to HKCU\..\run (CurrentUser Component)
"C:\Program Files\palmOne\HOTSYNC.EXE"
- Remove the Desktop Extension ("palmOne Quick Install")
(
remove the following registry keys from the Registry table:
Registry5
Registry698
)

- Add execute installed files for "C:\Program Files\palmOne\PIL.exe" on install/repair
Change regular shortcuts to advertised


The "\English\Helpnote\Handbooks\*.pdf" are missing in the "C:\Program Files\palmOne\helpnote" directory,
add them manual. This happens due to missing installation files not taken from the CD.

CustomAction:
PostInstallLauncher
Description: execute PIL.exe
Execute Deferred
Before InstallFinalize
Name: PostInstallLauncher
Type: 1042
Execute: PIL.exe
Processing: Asynch, No wait
Answered 08/21/2007 by: AngelD
Red Belt

Please log in to comment
0
Thanks all.. I think i'm having another go at it tomorrow.. Seems like the less time i have to repackage apps, the higher the number of challenging apps..! :P
Answered 08/23/2007 by: neo2000
Purple Belt

Please log in to comment
0
It's a beast..! [&:] [;)]

Having trouble with the IS engine.. If i install it manually, no problem. If i try to add the merge module of Installshield 11, add the property ISSETUPDRIVEN with the value of 1, setup still fails after 30 secs. It doesn't show the "ISScript is not installed on this machine" dialogue though. Tried everyting mentioned in http://itninja.com/question/msi-corporate-standardiser6 that you suggested AngelD, but still no luck..
Answered 08/27/2007 by: neo2000
Purple Belt

Please log in to comment
2
No one said it was gonna be easy [;)]
The InstallShield engine version must match exactly so there may not exist a Merge Module version for it. The "ISSCRIPT_ENGINE_VERSION" property should tell you what version that it requires.

Depending on your deployment solution you could pre-install isscript.msi before installing the actual msi.

Never repackage an MSI is one of the first rules of repackaging
We all know about the rules of engagement and we would follow it strictly if it wouldn't be for these crappy packages out there and specially with InstallShield script based MSIs.
If you feel it takes too long to get this working then a faster solution would be to re-package it instead.
You will get alot of entrypoint registry entries so make sure to remove any junk and Windows Installer related info.
Answered 08/27/2007 by: AngelD
Red Belt

Please log in to comment
0
AngelD, tried your first post and that worked for me..! Thanks again..!

I was under the impression that the Installshield merge modules were a replacement for the ISScript engine.. Too bad there are that many versions around of the Isscript engine apparantly. Just thought (hoped [:D]) there were just 10, 10.5, 11.0and 11.5 versions going around, which could be replaced by corresponding merge modules. Well, maybe in an ideal world.. [;)] Thanks anyways, rated your post..
Answered 09/03/2007 by: neo2000
Purple Belt

Please log in to comment
0
The reason people say dont repackage an MSI is that you take over complete responsibility of that package from then on. If the vendor releases a patch, you have to snap it, if you have a problem with the package and the vendor finds out you repackaged their MSI, I doudt they would help you.

If your confortable with those issues then repackagage away.

Paul
Answered 09/03/2007 by: Inabus
Second Degree Green Belt

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