Software Deployment

Hi Wozik,

Not that I've ever repackaged Opera this way, but if you are running it and its crashing/hanging do you get an error message? You can try to debug this problem, I would probably approach it by using either Filemon or Regmon from Sysinternals (www.sysinternals.com) - if you aren't familiar with these tools,Filemon monitors a programs attempts to access files, and Regmon monitors a programs attempts to access the registry. I use these all the time to diagnose errors like this, as programs are usually crashing because they can't access a file/reg setting, or need to create/write/delete a file/registry settings and don't have permissions - these tools will show you what is happening when the program crashes.

Hope that helps

Paul

I've done what you've advised me. But I get a lot of messages generated by Filemon or Regmon. It seems that Opera.exe file tries to access to files which are not connected with Opera. For example drwtsn32.exe. Either Regmon shows me that there is a lot of registry keys which opera.exe tries to use. I think that some of them are not connected with Opera.

How should I act when I get error message like "File not found". Should I put that file into installation package? The same problem is with registry, how should I act with registry keys which Opera tries to access?

I think that I have to explore that problem.

Anyway, how do you repackage Opera?

Wozik

Lets start over Wozik.

First of all get a clean machine and do a capture of the Opera install. Because this app is going to integrate into the OS, I would capture absolutely everything you can.

Once you have the capture, create a delta of the fileset and the reg keys. You will need to strip out the rubbish first. In case you dont know, a delta is just the fileset and registry keys that you will put in the msi. Once you have a good delta you can be pretty confident of getting the app working.

Now make a new clean machine and drop the delta onto it manually and see how it works. Copy the files to their folders and import the reg file. See if it runs. If it doesnt then check the Event Viewer and see if their any errors in there. Then run filemon and regmon to see how they look.

Get your basic delta right and then worry about packaging it. Once you have it running from the captured files.....thats when you package it to msi.

I've got a question regarding to the delta of the fileset and the reg keys. Which tool allows to do that?

How can I put it into msi file?

Wozik

That is what I have done:

1. I've captured an installation of Opera 7.52 with Wise Package Studio
2. I've created registry dump manually before and after install of Opera
3. I've cleaned the package and made delta from the reg files
4. Unfortunately Opera still doesn't work

Event viewer gives mi an error:

Faulting application opera.exe, version 7.0.3834.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any ideas?

--
Wozik

Faulting application errors are generally the product of dll version mismatches. Perhaps you have included a system dll by mistake. You may even have missed a dll registration.....I'm afraid its all hit and miss from here.

Are you packaging the Java or non-Java version?

I'm packaging the non-Java version. I don't think that I've missed some dll's. There's no file installed in Windows or Windows\System32 folders.

--
Wozik

Well I did a capture with WPS and it missed some files.

I redid the capture with Wininstall and got all the missing files and added them and its working ok for me.

Download Wininstall eval and redo your capture....you will see what I mean.

Thank you! I'll try with WinInstall.

--
Wozik

Now everything works fine! WinInstall did it :)

Another happy customer :)