Stuart,
	I have experienced this problem as well and there are documented fixes for it in the KB but the approach I took I found very easy
to use and implement. I downloaded the visual studio installer that creates msi installer packages. It is interfaced in the interdev
app as a new project type when it is installed. This software combined with ORCA allows me to create msi installation packages for
all Microsoft OS's. ORCA is needed to deploy an app to all users on Win2k and XP. You have to set an all users flag in the msi
package but that is another issue altogether. The download was not that big and it was easy to use.

HTH
Pat

PS if you choose to fix the p&d issue here is the kb article.....    q191096 number


I found it by searching http://www.google.com/microsoft.html


this searches microsoft related sites and always seems to retrieve pertinent results



-----Original Message-----
From: Stuart Naylor [mailto:indtec@e...]
Sent: Tuesday, November 19, 2002 2:35 PM
To: professional vb
Subject: [pro_vb] Package & Deployment Wizard Problem


I have a odd problem with app deployment. I have a network of 20 pc's and 
the installation goes fine on 17 of the Pc's but on three the following 
happens.

Windows2K SP2 and VBSP5.

I can tell straight away on the install that there is going to be a problem 
as the install package tells me that some of the system files are out of 
date and it goes through the tasks of installing the virtual machine and 
the rest. When it completes this it asks for the computer to be rebooted. 
Unfortunately on the restart the installation doesn't continue and when you 
manually choose to install the package again you get the same cycle every 
time with the install never getting to the point where it installs the 
application specific files and folders.

Anyone ever had this problem before?

Also the support company say there isn't anything wrong with the clients 
and they do not support non certified windows applications. 'Non certified' ?

I even created a project with a blank form and create a package and this 
does exactly the same.

I guess I will instruct them to delete msvbvm6 and then do a install what 
other files could be causing the problem ?

Thanks
Stuart