Problem installing a VB6 program

I am trying to install a couple of VB6 programs on to a computer
running WinXP that has been "updated" (with the so-called "critical"
updates) but does NOT have Service Pack 2 on it.

The programs were created on a unit running WinXP WITH Service Pack 2.
The install package for each program was created using the VB6 P&D
wizard.

I'm getting an error that I've never seen before. It is being
generated by the setup program - it says:

"Setup cannot continue because some system files are out of date on
your system. Click OK if you would like setup to update these files
for you now. You will need to restart Windows before you can run setup
again. Click cancel to exit setup without updating system files."

I allowed it to update "these files" (whatever files they are); it
appears to do something and then prompts for a re-boot, but when I run
setup again, the same error occurs.

Any thoughts as to what I need to do? Is the lack of SP2 the problem ?
(I thought it was just security related stuff).

Probably. If the app was developed on a PC with SP2, then it's likely that
it'll use DLLs that were updated by SP2, and are hence newer than those on
the target machine, which is why you get the out of date message. If you do
upgrade the machines to SP2, it will probably go away.

"Martin" <martinvalley@comcast.net> wrote in message
 news:s94ao0hqvai9ftlt8ouk8mg9ieoujlih9e@
4ax.com...
>I am trying to install a couple of VB6 programs on to a computer
> running WinXP that has been "updated" (with the so-called "critical"
> updates) but does NOT have Service Pack 2 on it.
>
> The programs were created on a unit running WinXP WITH Service Pack 2.
> The install package for each program was created using the VB6 P&D
> wizard.
>
> I'm getting an error that I've never seen before. It is being
> generated by the setup program - it says:
>
> "Setup cannot continue because some system files are out of date on
> your system. Click OK if you would like setup to update these files
> for you now. You will need to restart Windows before you can run setup
> again. Click cancel to exit setup without updating system files."
>
> I allowed it to update "these files" (whatever files they are); it
> appears to do something and then prompts for a re-boot, but when I run
> setup again, the same error occurs.
>
> Any thoughts as to what I need to do? Is the lack of SP2 the problem ?
> (I thought it was just security related stuff).

"Martin" <martinvalley@comcast.net> wrote in message
 news:s94ao0hqvai9ftlt8ouk8mg9ieoujlih9e@
4ax.com...
> I am trying to install a couple of VB6 programs on to a computer
> running WinXP that has been "updated" (with the so-called "critical"
> updates) but does NOT have Service Pack 2 on it.
>
> The programs were created on a unit running WinXP WITH Service Pack 2.
> The install package for each program was created using the VB6 P&D
> wizard.
>
> I'm getting an error that I've never seen before. It is being
> generated by the setup program - it says:
>
> "Setup cannot continue because some system files are out of date on
> your system. Click OK if you would like setup to update these files
> for you now. You will need to restart Windows before you can run setup
> again. Click cancel to exit setup without updating system files."
>
> I allowed it to update "these files" (whatever files they are); it
> appears to do something and then prompts for a re-boot, but when I run
> setup again, the same error occurs.
>
> Any thoughts as to what I need to do? Is the lack of SP2 the problem ?
> (I thought it was just security related stuff).

You are probably fighting XP's version of WFP (Windows File Protection).

Update the XP box.

-ralph

Martin wrote:
>
> I am trying to install a couple of VB6 programs on to a computer
> running WinXP that has been "updated" (with the so-called "critical"
> updates) but does NOT have Service Pack 2 on it.
>
> The programs were created on a unit running WinXP WITH Service Pack 2.
> The install package for each program was created using the VB6 P&D
> wizard.


If you have some reason for not putting SP2 on the user machine, then
odds are high you're going to have to build a new installation package.

Either on a machine without SP2, or by using a professional installation
packager (one that ships with its own 'lowest common denominator' libraries)



Bob
--

Hi Martin

I find the first part of your explanation to be perfectly normal, your setup
program has files that is newer than the same file on the machine.
Setup offers to update the machines files, this is perfectly normal, Your
problem is that the update does not take effect, your are back on the old
files again after reboot, I do not have very much experience with XP but I
assume W2K is not so far away and I have encounter the same on W2K if my
login rights is not enough to update driver files.

If it's not a question of user rights then it's probably a bug that XP
cannot accept update routines from VB-applications, I suggest you upgrade th
e
machine to latest service pack.

Kjell

OK - thanks for the replies.

I put SP2 on the target machine and the programs installed without a
hitch.

Martin



On Sun, 31 Oct 2004 09:39:32 -0700, Martin <martinvalley@comcast.net>
wrote:

>I am trying to install a couple of VB6 programs on to a computer
>running WinXP that has been "updated" (with the so-called "critical"
>updates) but does NOT have Service Pack 2 on it.
>
>The programs were created on a unit running WinXP WITH Service Pack 2.
>The install package for each program was created using the VB6 P&D
>wizard.
>
>I'm getting an error that I've never seen before. It is being
>generated by the setup program - it says:
>
>"Setup cannot continue because some system files are out of date on
>your system. Click OK if you would like setup to update these files
>for you now. You will need to restart Windows before you can run setup
>again. Click cancel to exit setup without updating system files."
>
>I allowed it to update "these files" (whatever files they are); it
>appears to do something and then prompts for a re-boot, but when I run
>setup again, the same error occurs.
>
>Any thoughts as to what I need to do? Is the lack of SP2 the problem ?
>(I thought it was just security related stuff).