Automatic link created by web update not correct
Automatic link created by web update not correct
Hello,
I'm trying the automatic web update feature.
Then installing on the target machine, the item gets created in the sheduler, but the lnk created is the following Accrimed Updates for All Users.lnk
Running this item from the sheduler gives an error that it cannot start.
When looking in the folder c:\\windows\\Installer, I find a lnk, but the name is not the same, it's #TITLE# Updates for All Users.lnk
That's the exact filename.
Dominique.
I'm trying the automatic web update feature.
Then installing on the target machine, the item gets created in the sheduler, but the lnk created is the following Accrimed Updates for All Users.lnk
Running this item from the sheduler gives an error that it cannot start.
When looking in the folder c:\\windows\\Installer, I find a lnk, but the name is not the same, it's #TITLE# Updates for All Users.lnk
That's the exact filename.
Dominique.
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
I have the same Problem.
The Messagebox Text also doesnt expand correctly. it also shows #TITLE#.
I´ve tried to change #TITLE# to $TITLE$ in the updates include script, but this also doesnt help.
The Taskplaner refers to a file with the title expanded, and thus never get called.
My Version: "Version 6.0 (Build gwinnett_rtm.060606)"
(Updated last with the version containing Internet Explorer 7; Autoupdate says no further updates available).
Can you suggest a workaround for this? i wanted to release my setup this week, but cant without auto-updates working.
FYI: I have changed the Language to German.
Kind Regards,
Stefan
The Messagebox Text also doesnt expand correctly. it also shows #TITLE#.
I´ve tried to change #TITLE# to $TITLE$ in the updates include script, but this also doesnt help.
The Taskplaner refers to a file with the title expanded, and thus never get called.
My Version: "Version 6.0 (Build gwinnett_rtm.060606)"
(Updated last with the version containing Internet Explorer 7; Autoupdate says no further updates available).
Can you suggest a workaround for this? i wanted to release my setup this week, but cant without auto-updates working.
FYI: I have changed the Language to German.
Kind Regards,
Stefan
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
OK, you first said you have:
gwinnett_sp3.111106
But now you say you have:
gwinnett_rtm.060606
Which is older. I suspect you didn't regenerate and reinstall your license file. Please do that and try again. Just build an empty setup that just displays #TITLE# in a MessageBox. When that works, your update will also.
gwinnett_sp3.111106
But now you say you have:
gwinnett_rtm.060606
Which is older. I suspect you didn't regenerate and reinstall your license file. Please do that and try again. Just build an empty setup that just displays #TITLE# in a MessageBox. When that works, your update will also.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Stefan,StefanB wrote:I have the same Problem.
FYI: I have changed the Language to German.
Stefan
if you localize your setup, expand all references to #TITLE# in your German translation. Compiler variables are not expanded in localized setups.
Mike, one is StefanB, the other is bernaert. Stefan should update to the latest version.OK, you first said you have:
gwinnett_sp3.111106
But now you say you have:
gwinnett_rtm.060606
ouch, the latest version only works on Win XP but i am still on Win2000.
So i expect all future versions will only work in XP, right?
I will try to expand #TITLE# in first place and take care on the new version problem later.
[Edit] unfortunately neither changing #TITLE# to $TITLE$ nor to Productname directly does change anything.
as i cant install the latest version immediately, and i havent generated a new license file for the version including IE7: is there any chance to generate a license file for the IE7 Version? on the generate License link i only can make one for the latest version.
[/Edit]
thanks for advice
So i expect all future versions will only work in XP, right?
I will try to expand #TITLE# in first place and take care on the new version problem later.
[Edit] unfortunately neither changing #TITLE# to $TITLE$ nor to Productname directly does change anything.
as i cant install the latest version immediately, and i havent generated a new license file for the version including IE7: is there any chance to generate a license file for the IE7 Version? on the generate License link i only can make one for the latest version.
[/Edit]
thanks for advice
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
The XP dependency would appear to be an error on our part. I'll have that escalated and resolved ASAP, so you can install the latest version. Only latest version licenses are available.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
R&D is about to release a new build that gets rid of the artificial XP limitation. Please check the download page later today - thanks for bringing this issue to our attention!
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/

