Please wait while Windows configures <ProductName>
Hal Gibson
This started after she downloaded an updated EXE of our application via the
web. If she puts her original cd in, it lets her in. If not, she continues
to get this message. The new features added to our application via the
updated exe are available once she is in the program.
Exe is installed on customer's same machine as the original installation.
They downloaded from web and pasted the exe to the existing program folder,
overwriting the previous exe. Customer was logged on as the same user as in
the original install.
EXE is written in VB6, machine is XP
--Hal
Randem
What installer are you using to deploy your package?
"Hal Gibson" <ha...@disc-calif.com> wrote in message
news:0130824E-80FA-4A4A...@microsoft.com...
Randem
Actually, I need more info than that... What is the exact product name CD
that the Windows Installer is asking for?
If it is not yours then the app was installed with Windows Installer and a
component that you install/use is triggering the installation. What are the
new components you are deploying?
--
Randem Systems
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
http://www.rndem.com/installerproblems.html
httlp://www.randem.com/vistainstalls.html
http://www.financialtrainingservices.org
"Randem" <newsg...@randem.com> wrote in message
news:%23D%233IwSR...@TK2MSFTNGP05.phx.gbl...
Hal Gibson
hadn't done for weeks - she stopped getting the message.
Now I have another customer, same scenario.
We advised him to reboot, which seemed to resolve the issue, but it crops
about once a week, at which point he reboots and it will be fine for another
few days.
All necessary dlls and controls are included and installed during the
initial CD installation.
All of the code in the exe is the same except that certain flags have been
reset to allow the customer access to optional features of the program ( but
again, these features were included in the original exe, they just weren't
"turned on", otherwise the updated exe is indistinguishable from the
overwritten exe.)
I can understand how Windows Installer might detect that the exe file has
changed, and requires a reboot ( although it doesn't ask for one, but rather
asks for the original installation CD), but why would the issue keep
cropping up sporadically?
Any clues as to why this is happening?
"Randem" <newsg...@randem.com> wrote in message
news:%23nOHhLg...@TK2MSFTNGP03.phx.gbl...
Randem
missing and Windows Installer wants to put it there. You can use System
Internals FileMon and RegMon to find out what it is looking for. These
utilities are now owned by MS.
--
Randem Systems
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
http://www.rndem.com/installerproblems.html
http://www.randem.com/vistainstalls.html
http://www.financialtrainingservices.org
"Hal Gibson" <ha...@disc-calif.com> wrote in message
news:34DA33E4-C62F-46CE...@microsoft.com...
Hal Gibson
was inadvertently carried over from InstallShield 2.12 when we upgraded
InstallShield versions.
Some of the registration process in Axdist.exe is not completed until the
machine is restarted - which explains why rebooting helped, and, it gets
clobbered anytime a user clears out their temporary files - which explains
why the issue crops up again.
We intend to remove it from future CD updates and installations since MS
advises not to run Axdist.exe on systems that have Internet Explorer 3.0 or
higher installed.
The question is should we advise current users to uninstall the existing
installation first, before running the CD update? Vista seems to require
uninstallation of prior version automatically, XP and earlier do not.
"Randem" <newsg...@randem.com> wrote in message
news:Okoc6trT...@TK2MSFTNGP02.phx.gbl...
Randem
clients to do just that. Of course you should give very detailed
instructions to follow.
How did you find this out?
--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
http://www.rndem.com/installerproblems.html
http://www.randem.com/vistainstalls.html
http://www.financialtrainingservices.org
"Hal Gibson" <halg...@earthlink.net> wrote in message
news:49627781-5618-40DC...@microsoft.com...
Hal Gibson
some really outdated items.
I think InstallShield Express 2.12 (which used a proprietary engine) would
stick Axdist.exe in a temporary folder, run it, then delete it, but
InstallShield 2008 (which uses Microsoft's engine) just stuck it in the
folder.
We upgraded from InstallShield Express 2.12 to ISE 12, ISE 2008 and ISE 2009
respectively, with the reference to Axdist.exe being carried over with each
upgrade, unfortunately.
The people that were having the issue seemed to have triggered it when they
cleaned out their temp files.
We have removed Axdist.exe from our installation now, and are about to
embark on a series of CD updates of our installed product.
The question, and I don't mean it as a rhetorical one, is should we have our
customers manually uninstall the previous installation first, to get rid of
the reference to Axdist.exe, or would the new installation automatically
take care of that? BTW this is a minor update, there is no version number
change.
InstallShield has not responded to this question on their forum.
"Randem" <newsg...@randem.com> wrote in message
news:OUmfAAMV...@TK2MSFTNGP04.phx.gbl...
Randem
uses no such database. As much as I know about the Windows Installer is that
you should uninstall before the new install to prevent the afore-mentioned
problem.
--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
http://www.rndem.com/installerproblems.html
http://www.randem.com/vistainstalls.html
http://www.financialtrainingservices.org
"Hal Gibson" <halg...@earthlink.net> wrote in message
news:28DC5964-1FD9-4F63...@microsoft.com...