Hi, I'm just getting into packaging and I have a few questions. I'm using Wise 7 and followed the tut in the getting started guide without any problems. Last night I tried to package one of the apps that I'm going to need and package for my job, but ran into a little snag. During the edit package stage Wise comes back with a messagebox that states "Error 1904 Module. Java 1.5 is not installed properly." I ignored to see what would happen, but after completing all the steps and trying to install the app I received the same exact messagebox.

I have a few questions about this. Why did Wise not include Java in the package? It must have been installed during the inital install because I didn't receive the error when I installed it after the first capture. There is a JRE folder in the install directory. It seems to me it must not be full Java because there's nothing in the Control Panel or add remove programs for it. The basic tutorials that I have been reading don't cover things like this, but what if they already have Java on the machine? Obviously this is a fresh machine and Java is not installed at this point, but what if another machine already has it installed?

Is there anything special I have to do if an app wants to install another feature which has a seperate installer during the install? Example would be if the installer asks if you want to install a special toolbar which launches a seperate installer and than after completion the original installer continues. Will Wise pick that up? The reason I ask is because I thought I read that Wise get confused if multiple .exe's are used. Thanks.
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
Welcome to the wonderful world of packaging and JRE in particular.

I *hate* JRE-baxsded apps with a passion. Some vendors build apps which are tied to ONE flavour of JRE (e.g. 1.4.2_10) and will not work with an other, even newer ones. Past experience shows that these apps will work with newer versions if you can fool the app into thinking that the required version is installed. This requires nothing more complicated than divining the JRE information from the registry and 'ghosting' that information into the required entries. Use ProcMon and you'll see straight away what I mean. If you're still struggling, PM me and I'll dig out the code I have. Taking this route means you will need to acquaint yourself with Custom Actions and scripting, which is always fun.

BTW, it is my considered opinion that you CANNOT do this job without ProcMon or some similar tool. It's a free d/l from SysInternals, now subsumed into Microsoft.

Before I go, simply put, if your apps require JRE of any flavour, install that FIRST before capturing.
Answered 06/15/2007 by: VBScab
Red Belt

Please log in to comment
0
A friend that does packaging for a living helped me out yesterday. I had to go into setup editor and than selfreg and delete the java files from the selfreg. Worked like a charm. Thanks for taking the time to reply though VB. I really want to learn this stuff, so I appreciate the information. I have been using the sysinternals tools for some time now. Regmon and Filemon have saved me numerous times. Thanks again.
Answered 06/15/2007 by: notta
Orange Belt

Please log in to comment
0
Excellent. I'm glad you're sorted.

BTW, I hope your friend also advised you to *always* take stuff out of SelfReg: it's only useful purpose is to give you a list of files against which to run WiseComCapture. This utility produces .REG files for registerable DLLs and you then import these into your Wise project.

Good luck for the future.
Answered 06/15/2007 by: VBScab
Red Belt

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