Package and deployment

**mayayana** · Jul 17 '05, 09:23 PM

Re: Package and deployment

You can skip packing the VB runtime files
(1 through 6) unless you're installing on an isolated
version of Win95 or 98. Other systems already have
those files.

ME, 2000 and XP don't allow system files to be
replaced. When your installer tries to install them
and reboot, the system file protection just puts
back the old versions. Unfortunately, it doesn't
inform the user of those shennanigans, so the result
is setups such as you're seeing.

The trick is to use older file versions, predating
ME and 2000. Put them in the folder
Wizards\PDWizar d\Redist so that the PDW will
use them by default.

The idea with that is to provide files to systems that
need them without trying to overwrite file protected by
SFP (where the file isn't needed anyway).

The versions that come with whatever service pack
you've installed should be good. Personally, I think
that every file version should be checked carefully
and a search done to make sure there are no known
problems. You can't just assume that Microsoft has
maintained smooth compatibility between versions.

(For a good example of possible problems, do a
search for the MS page that explains the different versions
of the RichText library. They've even published wholly
different versions, of very different size, with exactly
the same version number!)

For version comparison, in my Redist folder I have:

oleaut32.dll, asycfilt.dll, both v. 2.40.4275.

I also have comcat.dll v. 4.71

Those files were probably put there by a
service pack after problems were reported
with the use of later versions.
--
_______________ ______________

mayayXXana1a@mi ndYYspring.com
For return email remove XX and YY.
_______________ ______________
Bob Walpole <rwalpole@bluey onder.co.uk> wrote in message
news:HQ1Md.1$89 .0@fe3.news.blu eyonder.co.uk.. .[color=blue]
> I am somewhat a novice with vb6 however I have completed a program which
> needs to be shared by several people if it is to be of major use. I have
> used the Package and Deploymnet Wizard so that I can distribute it by CD.[/color]
I[color=blue]
> have also loaded the program for CD via set up back on to my computer in
> different directory successfully. However it fails to load onto other
> computers using windows XP (as is mine)
> The Program includes DatePicker, FlexGrid and Common Dialog modules. On
> forming the Package it tells me that the following are included:
> Uses1=msvbvm60. dll
> Uses2=oleaut32. dll
> Uses3=olepro32. dll
> Uses4=asycfilt. dll
> Uses5=stdole2.t lb
> Uses6=COMCAT.DL L
> Uses7=comdlg32. ocx
> Uses8=MSCOMCT2. OCX
> Uses9=MSFLXGRD. OCX
> Uses10=MSCOMCTL .OCX
> and these are set for \Windows\system 32
> Similarly when clicking on SetUp on another computer it states that some
> files don't exist or need updating. Continue seems to load these files[/color]
then[color=blue]
> states the Computer need to be restarted. On restart and clicking on set[/color]
up[color=blue]
> it still tells me that the files don't exist or need updating! and fails[/color]
to[color=blue]
> load the main program. Any ideas?
>
>[/color]

**Martin** · Jul 17 '05, 09:23 PM

Re: Package and deployment

I sympathise with you having been in a similar position myself having had
failures with Win95 -> Win 2000 and Win XP -> Win95 and Win Me and Win 2000.

However, it's now all sorted after many requests to VB newsgroups, and
reading between the lines!

The solution for me was:-

Get all VB6 updates (SP6) from Microsoft site.
Get Microsoft Visual Studio Installer from Microsoft site.
All the necessary downloads are FREE.

Using the updated VB Package & Deployment Wizard overcame my problems of
installing on
ANY platform!

Alternatively with very little extra work you can use Visual Studio
Installer. This has many added advantages such as being able to
automatically install Windows Installer (when needed) onto any Windows
Platform, automatic installation of Desktop Icons, Banner advertisements on
the Installation Dialog Forms etc........

Hope this helps.

Regards

Martin Double

Email: cadoss@btconnec t.com
Web Site: http://home.btconnect.com/cadoss

"Bob Walpole" <rwalpole@bluey onder.co.uk> wrote in message
news:HQ1Md.1$89 .0@fe3.news.blu eyonder.co.uk.. .[color=blue]
> I am somewhat a novice with vb6 however I have completed a program which
> needs to be shared by several people if it is to be of major use. I have
> used the Package and Deploymnet Wizard so that I can distribute it by CD.[/color]
I[color=blue]
> have also loaded the program for CD via set up back on to my computer in
> different directory successfully. However it fails to load onto other
> computers using windows XP (as is mine)
> The Program includes DatePicker, FlexGrid and Common Dialog modules. On
> forming the Package it tells me that the following are included:
> Uses1=msvbvm60. dll
> Uses2=oleaut32. dll
> Uses3=olepro32. dll
> Uses4=asycfilt. dll
> Uses5=stdole2.t lb
> Uses6=COMCAT.DL L
> Uses7=comdlg32. ocx
> Uses8=MSCOMCT2. OCX
> Uses9=MSFLXGRD. OCX
> Uses10=MSCOMCTL .OCX
> and these are set for \Windows\system 32
> Similarly when clicking on SetUp on another computer it states that some
> files don't exist or need updating. Continue seems to load these files[/color]
then[color=blue]
> states the Computer need to be restarted. On restart and clicking on set[/color]
up[color=blue]
> it still tells me that the files don't exist or need updating! and fails[/color]
to[color=blue]
> load the main program. Any ideas?
>
>[/color]

Package and deployment

Package and deployment

Comment

Comment