[RESOLVED] Out of date system files ?

Trying to install a VB6 application on a machine running XP-Pro The installation halts with the message

"Install is unable to continue as some of your system files are out of date. Click yes and install will update them"

However clicking yes does not appear to fix the problem as install goes through the same routine next time you try.

The annoying thing about windows error messages is that they are not informative, i.e. why not tell me which files ?

I went to the MS website and updated the op system, but still no go.

Anyone know how to correct this ?

Which is the application? How did you created the setup file?
I think the system in which you are installing the software may already contains some vb runtime files. And while you are installing the program, one of the files(either one of them from the setup file or the one system) is out of date. Thats what I think. I think you are using package & deployment wizard to create the setup file. Have you tried installshield or inno setup.
- Akhilesh

Thread moved from Application Deployment forum, which is for questions about installing/distributing your software

There is an article about that in the FAQs at the top of this forum.

To save readers trawling through the FAQs

the answer to this problem is here

http://support.microsoft.com/kb/191096

cheers all

tinker

There are a number of possible factors involved. Also see:

http://support.microsoft.com/kb/831491

... and ultimately go through:

Best practices for deploying Visual Basic 6.0 applications

What it comes down to is that VB6 is old now, and Windows has evolved without bringing VB along. There are many issues surrounding the use of the aging PDW today, and many years worth of KB articles giving out bits of advice for coping with changes in the Windows ecosystem.

These factors have made VB6 deployment more of a challenge than it was in the early days. Simply changing installer technology is not a solution in itself, though some alternative packaging systems can make it easier to build successful deployment packages.


This particular problem seems to be a recurring theme here, we get a question just like this here every two weeks or so. There is no cookbook answer, but it generally comes down to your setup package trying to deploy dependencies it shouldn't. Usually this is the result of failing to update the "hints" PDW relies upon to decide whether to package a given dependency. Alternatively you must manually exclude those non-deployables when you go through the Wizard.

No single PDW update could even do this for you. The packaging requirements vary somewhat depending on your target OS, and get hairier if you want to build a single setup targeting multiple Windows versions.

Hi All
I have marked this thread as Resolved, not because there is a definitive answer, rather the contrary

The solution whereby you set a path to C:\TEMP worked in my case.

I will leave it up to others to find their own solution.

I agree VB6 is old. I retired at 60 years of age and am simply working to keep the “little Gray Cells” around for a little bit longer, and VB6 plus PIC programming are the chosen way. I suspect VBnet will be rather expensive to buy, but I will look into it.

Cheers all
Tinker

Quote:

---

Originally Posted by vb6tinker

I suspect VBnet will be rather expensive to buy, but I will look into it.

---

There are a few editions, and the price varies... but for most people the Express Edition (which is free!) is good enough. :)

I wasn't trying to disparage VB6. I have to do a lot with it yet myself.

It is old and neglected though, which means we just need to be clever to get the most out of it.

Glad you found a path around your problem.