Install exe compiled with Windows 2000 at WinNT station

[kkl_mal]

Hi,
I have written an application with VB 6 at Windows 2000 OS. Now I would like to install this application at another PC with WinNT OS. I couldn't install it as some files are different, e.g comcat.dll, oleaut32.dll, olepro32.dll, comdlg32.ocx, mscomctl.ocx, etc.


The dates of the files in WinNT OS PC are pretty old, 1997 but the one I had in Windows OS is 2003.

Please advise.

[RhinoBull]

... I couldn't install it as some files are different...

Of course they are, so what happend when you tried?

[kkl_mal]

Of course they are, so what happend when you tried?

I was prompted with a message telling me that a newer version is needed. I couldn't continue with the installation.

[RhinoBull]

You know, you just remainded me something: few years ago we had to have an NT machine so we could compile new releases and also build distribution directly on NT for NT - that was the only way at the time as our main development platform was already XP.

[kkl_mal]

You know, you just remainded me something: few years ago we had to have an NT machine so we could compile new releases and also build distribution directly on NT for NT - that was the only way at the time as our main development platform was already XP.

So, that is the only way, find a NT PC, install VB6, compile it again? No other alternatives?

Thank you.

[MartinLiss]

So, that is the only way, find a NT PC, install VB6, compile it again? No other alternatives?

Thank you.

I moved your thread here which is where we talk about installation problems, and no, you don't need to recompile your app. Just use the P&D Wizard, Inno, or other 3rd-party installer tool to create a set of installation files. Those files will contain everything that is needed for someone to install your app.

[RhinoBull]

So, that is the only way, find a NT PC, install VB6, compile it again? No other alternatives?

Thank you.

Perhaps there is but that is the safe way.
And you only have to build distribution package once unless you add new components to your project. After that you would only need to compile new exe.

One good alternative if you (or your company) can afford it is to use CITRIX.
With CITRIX deployment is a breeze - it really doesn't matter anymore what paltform your end user is on - they all will run the same executable directly from the CITRIX server through virtual layer. Some extra hardware would be required though...