Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

MSI Patching and Shortcut problem


4 replies to this topic

Gripper4Hire

Gripper4Hire
  • Members
  • 9 posts

Posted 07 December 2001 - 03:57

Hi all,

I'm having this problem getting a patch to apply correctly using ISWI 2.03's
patching wizard and MSI 1.2.

Here's the info:

The patch is for a small update between our 6.0 version of our software and
a new pending 6.01 release. Given that this is a small update, I left the
ProductCode and UpgradeCode alone for the new 6.01 install project, and
merely changed the ProductVersion from 6.00.0000 to 6.01.0000. We change
PackageCodes for every build, as recommended from the SDK.

Using the Installshield Patch Wizard, I successfully build the patch .msp
file (which I call 600_2_601.msp). However, when I apply this patch to the
target machine using both the default syntax (MSIEXEC.EXE /p <patchfile>) or
the recommended Small Update Syntax (MSIEXEC.EXE /p <patchname>
REINSTALL=MainApp REINSTALLMODE=omus) the patch updates all my files
correctly...

However!?!? The Shortcuts in both the Start Menu and the Quick Launch bar
for launching my main app's executable no longer function. If you click on
them, you get an error from MSI: "The Windows Installer failed to install
the program associated with this shortcut. Please contact your system
administrator."

I only have one component that makes shortcuts, but it makes 2 shortcuts
(could this be a problem?) One in the StartMenu/Programs/<etc> and another
in the ApplicationData\Microsoft\Internet Explorer\Quick Launch directory.

The new 6.01 install package passes the rigorous DARICE.CUB MSI validation
with only a few warning messages in the MS provided MergeModules. Under the
same test, the older 6.00 install package had one ICE64 error with respect
to RemoveFiles and the QuickLaunch directory (but this should only effect
uninstall for a roaming scenario according to the SDK.)

Deleting the shortcuts and running Repair restores the shortcuts, but...
they still don't work (same "The Windows Installer failed to install..."
error comes up when you click on 'em)

The OS doesn't seem to matter as I've confirmed this problem on a 98gold,
ME, and WinXP using default install ghost images.

Any ideas why the patch is destroying the two shortcuts?

Thanks for any help in advance.

Regards,

Jon Baker
Logitech Inc.


Craig Post

Craig Post
  • Members
  • 8 posts

Posted 15 December 2001 - 00:03

You might want to do a windiff on your install directory to make sure it's only screwing up those two shortcuts.  My experience with patches has been very disheartening.  I have had trouble with patches wiping out all non-versioned files on my install.  

Just out of curiousity, do you originally install from a compressed MSI, or an uncompressed?

Craig Post
Software Engineer, R&D
Captaris, Inc.


Gripper4Hire

Gripper4Hire
  • Members
  • 9 posts

Posted 15 December 2001 - 01:04

Craig,

Thanks for the info.

I ran a windiff between the Patched update and a Full install of the update, and I noticed that the "non-versioned" files are not updated -- which in our case is just the help files. I believe I have a solution to this -- wrapping them (*.chm's) into a small Microsoft IExpress package (or possibly using IS 5.5 Pro) and chaining the help file update to the application patch processes. I already need to do this as the Application patch (using MSI patching) needs to be chained to a Driver Update (which is just a standalone full version ISPro 55 install that is small). In fact, I was thinking of using a simple BAT file to control this flow...

For example, the UnZip folder would have the MSI Patch for our Application (which still doesn't work for the shortcuts!), a Driver Installer, and now a Help File Update. Then an UPDATE.BAT would simply call each in order, the MSP Patch being applied using the "/qb" switch to minimize user interaction.

But, back to the issue... It seems that only the shortcuts are being screwed up -- I Windiff'ed the *.lnk files also, and they are different, with a 0.11kb file size difference, the patched shorctut being larger, and not working!

Thanks again for the suggestion!

Regards,

Jon Baker
Logitech, Inc.


Craig Post

Craig Post
  • Members
  • 8 posts

Posted 17 December 2001 - 22:09

You know, it almost sounds like your shortcuts are being reinstalled as advertised.  After all a shortcut is just a file that points to another file, right?  Have you tried turning off the Advertised switch on the shortcut?  That might solve your problem (unless you need them to be advertised shortcuts).


jsp

jsp
  • Members
  • 96 posts

Posted 18 December 2001 - 09:18

Hi Craig,
Can you confirm that the executables launched by your shortcuts are key file?
Can you also confirm that your shortcuts are not advertised?
An other think: when I make small update, I use the command REINSTALLMODE=vomus: you do not use 'v' that means you do not re-cache the local package, this may be a reason of your problems.
Hope this helps,
Regards,
JSP