Does anyone have experience packaging Open Text Exceed 14 (previously known as Hummingbird Exceed)? I neeed to package this application for distributing to Windows 7 (64-bit).

I've installed the Admin version and used the "sconfig" utility as per their documentation. This allows creating a transormation file (.mst) that can be used for silently deploying the app. It works fine and I'm able to deploy the software. When users logs into any .xs sessions, it's supposed to bring up a Unix shell window. Problem is, this shell window doesn't come up after users logs on. There's no error message either.

If I perform the same installation manually, it all works fine. If you need more information, please let me know.



0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



My guess is that the session data is stored in the user's profile, either in a registry value of a set-up file (INI, XML. whatever). In order to propogate this data, you'll need to either build in to your transform (Note: 'transform', not 'transformation') what is called 'self-healing', or use Active Setup. My preference is for the former, since AS is only a one-hit operation.

Google for 'John +McFadyen +self +healing'. Read the blog and have a go at editing your transform. Revert here for any queries you may have.

Next, these changes will be *incredibly* painful unless you have an understanding of the fundamentals of Windows Installer so you may want to also read Phil Wilson's e-book 'The Definitive Guide to Windows Installer'. If you persevere, you'll find a free version but the cost of the paid-for ones isn't exactly usurous.

Lastly, the above pain will be lessened considerably by using a proper MSI authoring tool. You *can* use a basic MSI editing tool such as Orca or InstEdit but, again, you would need to know your MSI tables inside out if you want to avoid becoming bald.

Answered 09/09/2013 by: VBScab
Red Belt

Please log in to comment