Coral -- thanks for the tip on Inno Setup. I've been fighting the P&D
Wizard for years, not knowing that something as simple and elegant as Inno
Setup even existed. This could change my life...
Pete
-----Original Message-----
From: Coral Johnson [mailto:coral.johnson@r...]
Sent: Friday, August 30, 2002 2:54 AM
To: professional vb
Subject: [pro_vb] RE: ADO Rollout problem & XP
We have run into this problem and similar ones many times, and have changed
to using Inno Setup to do our installs, which is free. It has solved all
the problems we have come across so far. We have installed 4 very different
applications, some using mdac, on over 100 different computers over which we
have no control, and it has proven much more reliable than the P&D wizard,
and the users seem to like it as well. http://www.jrsoftware.org/isinfo.php
Coral
> TANGENT:
>
> Since Matt's so good at taking us there, allow me to go off on a tangent.
> I also used the Wise demo, but refused to pay the price (pun?). I
> had been
> using Setup Factory for a while but for some reason uninstalled
> it about a
> year ago and have been using the P&D. (hhhmmm...that reminds
> me...ought to
> put Castle Wolfenstein back on the puter....) I remember being real
> satisfied with Setup Factoryand I don't ever remember having any big
> problems with it, but didn't program in VB a lot back then. It has a lot
> of aesthetically pleasing ways to customize your install interface, and
> was very easy to use. Setup Factory is at least $100 less than
> Wise retail
> (I think I got mine on e-bay much cheaper). I was wondering if anyone has
> encountered significant drawbacks with Setup Factory concerning packaging
> VB programs??? It seems every time I use P&D some nasty issue comes up -
> sometimes fatal, sometimes not. Of course I don't know for sure
> until I've
> tested the install.
>
> Thanks...
>
> Kevin
>
>
>
> > Jeff,
>
> Don't know if this helps, and it seems like the wrong way to go
> about a fix
> (and I'm sure it is); but I ran into this problem as well. On 98, XP and
> 2K.
> I didn't know what the hell to do; played around for a long time, tried
> using WISE install and installshield express (you can download a 30 day
> trial from either; I preferred Wise's tho).
>
> Anyway, they both fixed whatever the problem was. But then my eval ran out
> and I didn't want to pay for the product.
>
> So I went back to the VB installer tool. In my case, the system would list
> the files that it thought were out of date when installing. A
> reboot didn't
> help; got the same message.
>
> Finally, I just removed the dependency references to the files (inside the
> P&D wizard) the system was having problems with. Everything installed and
> ran OK after that. I know it's not a fix, and I sure don't feel
> comfortable
> not knowing why it resolved the problem, but I had better things
> to do than
> fight the installer. Anyway, it let me move on to other more pressing
> issues.
>
> If I still worked at Sprint, I would tell you to tell your users "we don't
> support XP. Use NT 4.0".
>
> (Sorry, laid off last year, and after 8 years there, I havn't
> quite gotten
> back to thinking like a human again).
>
> Good luck!
>
> Matt
>
>
> ----- Original Message -----
> From: "Peter N. Kipe" <pkipe@c...>
> To: "professional vb" <pro_vb@p...>
> Sent: Wednesday, August 28, 2002 5:26 PM
> Subject: [pro_vb] RE: ADO Rollout problem & XP
>
>
> > There are several articles on the Microsoft Knowledgebase that address
> this
> > problem. Here's one, and you can follow links to others...or just do a
> > search on "Setup cannot continue" for Visual Basic.
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;Q191096
> >
> > Pete
> >
> > -----Original Message-----
> > From: THOMAS, JEFFREY W. [mailto:jeff.thomas@p...]
> > Sent: Wednesday, August 28, 2002 12:52 PM
> > To: professional vb
> > Subject: [pro_vb] RE: ADO Rollout problem & XP
> >
> >
> >
> > Thanks Simon. Here is my connection string:
> >
> > conn.Provider = "Microsoft.Jet.OLEDB.3.51"
> > conn.Mode = adModeRead
> > conn.ConnectionString = "Data Source=" & DBFilename & _
> > ";Jet OLEDB:System database=" & SysFilename
> > conn.Open , username, password
> >
> > And is my P&D file:
> >
> > [Root]
> > Most Recent Package=Standard Setup Package 1
> >
> >
> > [Package|Standard Setup Package 1|Root]
> > SubWizProgID=PDWizard.SetupPkgSubWiz
> > BuildFolder=G:\Hosts Database\hosts-src\Package
> >
> > [Package|Standard Setup Package 1|Configure DAO ISAMs]
> > Applicable=No
> >
> > [Package|Standard Setup Package 1|Configure DAO ODBC]
> > JetWorkspace
> > ODBCDirect
> >
> > [Package|Standard Setup Package 1|Files Found]
> >
> > [Package|Standard Setup Package 1|Files Released]
> >
> > [Package|Standard Setup Package 1|Missing Dependency Information]
> > C:\WINDOWS\system32\wininet.dll
> >
> > [Package|Standard Setup Package 1|Out-of-Date Dependency Information]
> >
> > [Package|Standard Setup Package 1|Files Added]
> >
> > [Package|Standard Setup Package 1|Files Removed]
> >
> > [Package|Standard Setup Package 1|Files In Project]
> > G:\Hosts Database\hosts-src\HostsCreator.exe=Yes
> > C:\WINDOWS\system32\msvbvm60.dll=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\OLEAUT32.DLL=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\OLEPRO32.DLL=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\ASYCFILT.DLL=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\STDOLE2.TLB=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\COMCAT.DLL=Yes
> > C:\WINDOWS\system32\wininet.dll=Yes
> > C:\WINDOWS\system32\MSADODC.OCX=Yes
> > C:\WINDOWS\system32\MSSTDFMT.DLL=Yes
> > C:\WINDOWS\system32\COMCTL32.OCX=Yes
> > C:\WINDOWS\system32\MSINET.OCX=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\MDAC_TYP.EXE=Yes
> > C:\Program Files\Microsoft Visual
> Studio\VB98\Wizards\PDWizard\SETUP.EXE=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\SETUP1.EXE=Yes
> > C:\WINDOWS\system32\VB6STKIT.DLL=Yes
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\ST6UNST.EXE=Yes
> >
> > [Package|Standard Setup Package 1|Configure Registry Files]
> > Applicable=No
> >
> > [Package|Standard Setup Package 1|Configure Remote Servers]
> > Applicable=No
> >
> > [Package|Standard Setup Package 1|Install Locations]
> > G:\Hosts Database\hosts-src\HostsCreator.exe=$(AppPath)
> > C:\WINDOWS\system32\msvbvm60.dll=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\OLEAUT32.DLL=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\OLEPRO32.DLL=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\ASYCFILT.DLL=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\STDOLE2.TLB=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\COMCAT.DLL=$(WinSysPathSysFile)
> > C:\WINDOWS\system32\wininet.dll=$(WinSysPath)
> > C:\WINDOWS\system32\MSADODC.OCX=$(WinSysPath)
> > C:\WINDOWS\system32\MSSTDFMT.DLL=$(WinSysPath)
> > C:\WINDOWS\system32\COMCTL32.OCX=$(WinSysPath)
> > C:\WINDOWS\system32\MSINET.OCX=$(WinSysPath)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\MDAC_TYP.EXE=$(AppPath)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\SETUP.EXE=$(AppPath)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\SETUP1.EXE=$(WinPath)
> > C:\WINDOWS\system32\VB6STKIT.DLL=$(WinSysPathSysFile)
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\ST6UNST.EXE=$(WinPath)
> >
> > [Package|Standard Setup Package 1|Configure Shared Files]
> > Applicable=Yes
> > G:\Hosts Database\hosts-src\HostsCreator.exe=No
> > C:\Program Files\Microsoft Visual
> > Studio\VB98\Wizards\PDWizard\Redist\MDAC_TYP.EXE=No
> >
> > [Package|Standard Setup Package 1|Distribution]
> > Type=single
> > Size
> > Title=HostsCreator
> >
> > [Package|Standard Setup Package 1|Package]
> > PackageFolder=G:\Hosts Database\hosts-src\Package
> > ProjectFolder=G:\Hosts Database\hosts-src
> > ServerSideCab
> > File1=G:\Hosts Database\hosts-src\Package\setup.exe
> > File2=G:\Hosts Database\hosts-src\Package\Setup.Lst
> > File3=G:\Hosts Database\hosts-src\Package\HostsCreator.CAB
> > Handler1=PDWizard.FolderDplySubWiz
> > Handler2=PDWizard.WebPostDplySubWiz
> >
> > Thanks again
> > Jeff
> >
> > -----Original Message-----
> > From: Lester, Simon [mailto:Simon.Lester@c...]
> > Sent: Wednesday, August 28, 2002 12:09 PM
> > To: professional vb
> > Subject: [pro_vb] RE: ADO Rollout problem & XP
> >
> >
> > Hi Jeff
> >
> > What have you included in the P&D script? By default ADO 2.1 gets
> included,
> > also what does your ADO connection string look like (this will identify
> > which driver you are trying to use).
> >
> > -----Original Message-----
> > From: THOMAS, JEFFREY W. [mailto:jeff.thomas@p...]
> > Sent: 28 August 2002 16:59
> > To: professional vb
> > Subject: [pro_vb] ADO Rollout problem & XP
> >
> >
> >
> > I'm have this problem and I'm not sure where to go from here:
> >
> > Some time ago I wrote a small VB/Access97 application, and used the
> Package
> > and Deployment Wizard to build a package to build a package so a few
> others
> > users could install this on their PCs. Everything was fine until one of
> the
> > users replaced their PC with Windows XP.
> >
> > Now the application is getting the following error:
> >
> > "Error Accessing Database (Provider cannot be found. It may not be
> > properly installed.)"
> >
> > If they re-run the setup package the get the following:
> >
> > "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."
> >
> > If you say OK, the system reboots, but when you run setup again, you get
> the
> > same message.
> >
> > I did a fresh install of Windows XP Professional on my PC. Reinstalled
> VB
> > 6.0 SP5. I'm using ADO 2.7. Rebuilt the application and package. The
> > application works fine for me, but I tried it on two other PCs
> and we are
> > getting the above errors...
> >
> > Any ideas where to look?
> > Thanks
> > Jeff
> >
> >
> >
> > ---
> > Visual C# - A Guide for VB6 Developers
> > This book will make it easy to transfer your skills
> > from Visual Basic 6 to C#, the language of choice
> > of the .NET Framework.
> > http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
> >
> >
> >
> > THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY
> > PRIVILEGED. If you are not the addressee, any disclosure, reproduction,
> > copying, distribution or other dissemination or use of this
> communication
> is
> > strictly prohibited. If you have received this transmission in error
> please
> > notify the sender immediately and then delete this e-mail.
> > Opinions, advice or facts included in this message are given without any
> > warranties or intention to enter into a contractual
> relationship with the
> > Corporation of London unless specifically indicated otherwise by
> agreement,
> > letter or facsimile signed by an authorised signatory of the
> Corporation.
> > Any part of this e-mail which is purely personal in nature is not
> authorised
> > by the Corporation of London. All e-mail through the Corporation's
> gateway
> > is potentially the subject of monitoring.
> > All liability for errors and viruses is excluded.
> >
> >
> >
> > ---
> > Visual C# - A Guide for VB6 Developers
> > This book will make it easy to transfer your skills
> > from Visual Basic 6 to C#, the language of choice
> > of the .NET Framework.
> > http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
> >
> >
> >
> > ---
> > Visual C# - A Guide for VB6 Developers
> > This book will make it easy to transfer your skills
> > from Visual Basic 6 to C#, the language of choice
> > of the .NET Framework.
> > http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
> >
> >
> >
> >
> > ---
> > Visual C# - A Guide for VB6 Developers
> > This book will make it easy to transfer your skills
> > from Visual Basic 6 to C#, the language of choice
> > of the .NET Framework.
> > http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
> >
>
---
Visual C# - A Guide for VB6 Developers
This book will make it easy to transfer your skills
from Visual Basic 6 to C#, the language of choice
of the .NET Framework.
http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059