Out of date system files?

I have a database run program that I used the pdw to compile a setup file/folder using winxp pro. Now, when I run the install from a cd on any other comp (i've tried on win me and win 2000) it says that my system files are out of date and need to be updated and will be done so automatically. Once finished it says I must restart, once done, and running the setup again-- I get the same error!. Any ideas!? -sTEVE

MSDN article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191096

Other thread:
http://www.visualbasicforum.com/showthread.php?threadid=56807&highlight=restart+setup

I tried installing 2.7 andrunning it again and still got the same error. -sTEVE

I just tried again on a different win2k comp and still nothin. -sTEVE

I'm having the same trouble with a program installing on XP. I checked out the articles in the links above, but neither of them referred to XP. I did find out though that I am using version 2.0.0.3002.15 of mdac-typ.exe. Should I upgrade this? If so, where can I get it? What does that file actually do? Do I have to send it in the package?

BTW, on 2 of 3 XP computers, the program could be installed after rebooting, on the third one, it just continued to loop the error message. Any further suggestions on what to check on would be greatly appreciated.

P.S. I am using two additional - paid for - ocx's - that couldn't be causing system file overwrites though, could it?

You can't install mdac 2.0 on XP. Check http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp for
more info on what you can and can't do with data access components
on XP.

Thanks, Thinker, but I couldn't find one reference to XP on that page. Anyway, I believe you about that. But - my problem is still there with this message coming up and the eternal loop between reboot and error message.

Of my Beta-Testers only the XP-users have complained about this (so far). That makes me wonder what is happening. BTW, I sent a similar program (using package and deployment wizard) to the same Beat-Testers and there were no problems.

The only difference in the programs were the size (one program I'm distributing now has a couple hundred files to install and the CAB is 6 MB) and in this current program I have added to third-party ocx's. Any ideas?

I notice that if I copy bootstrapfiles first to c:\winnt\system32 and registry those files, I can continue installation. So.. I think I create bat file which copy bootstrapfiles to winsyspath and register those files and after that continue installation.

Any comment?

make

Never was able to solve this with the package and deployment wizard, so I decided to try Inno Setup - and I'll never go back to VBs alternative. Inno is so flexible and so easy to learn. I recommend it to everyone.