Problem with a visual basic setup and windows 2000

[Bickle]

I have created a set-up (for a VB .exe) using the Project & deployment wizard of Visual Studio and when I try to install it on Windows 2000, I have an error which says "Your system files are outdate" and then it has to update them and restart Windows...

afterwards, I have the same message if I try and relauch the setup ? Has anybody come accross any problems with the Project & deployment wizard of Visual Studio and Windows 2000 ? Thank you...

 

[CCLINT]

You have some program(s) running in the background that loads itself on windows start. This program is using files that need to be replaced. Windows will not replace them when they are in use (likely a printer manager). And the P&D doesn't force a replacement.

You can:

1. Close the program(s) running (also 3rd party system programs) that are using the files (AntiVirus, Print Manager, etc). You can determine which files the may be by running something like process explorer and mathing up the files that those programs are using with the files your setup is trying to install.

2. Have the client update the system with the most recent SP.

Or,

2. determine which files these are (probably MFC42.dll) and remove them from the set up - your program may still run correctly.

Or,

3. Determine which files these are, switch to DOS mode and copy them to the windows system folder, reboot and then register them by hand.

Or,

4. Change the P&D setup1.vbp and add the API function that will force a file replacement.

Or,

5. Get a more professional installer that already handles this problem.

[/b][/i][/u]*******************************************************
_{General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[zemp]

This is a common problem with the P&D wizard. It may be simple and easy to use but it is far from perfect. What happens is that the P&D is trying to replace a file that is currently is use by windows and windows won't allow the P&D to do that when the P&D wants to. You basically have couple of options.

1. Try another installation package. Visual Stidio installer or INNO are two good ones that are free. INNO can be found at

http://www.jrsoftware.org.

2. Replace the file manually through DOS. This is not practical for distribution and not recommended.

3. Check out the solition found in thread222-304179.

Hope this helps. Thanks and Good Luck!

zemp