This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Laaw_parameters
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 23, 2017
04:14 PM
Laaw_parameters
The code is attached to the text file. I could not post it here.
Can anyone tell me why LAAW_PARAMETERS.nLaunchResult does not return a 0.
Can anyone tell me why LAAW_PARAMETERS.nLaunchResult does not return a 0.
(11) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 23, 2017
06:06 PM
if you are running on a system with UAC, you might need this:
if (SYSINFO.WINNT.bWinXP != TRUE) then
LAAW_SHELLEXECUTEVERB = "runas";
endif;
if (SYSINFO.WINNT.bWinXP != TRUE) then
LAAW_SHELLEXECUTEVERB = "runas";
endif;
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 24, 2017
08:54 AM
If reply from TurboFisch does not solve problem, you could remove the /q and the SW_HIDE so that you can see any error messages.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 24, 2017
10:01 AM
TurboFisch wrote:
if you are running on a system with UAC, you might need this:
if (SYSINFO.WINNT.bWinXP != TRUE) then
LAAW_SHELLEXECUTEVERB = "runas";
endif;
Where do I put this? Do I put it right before sCommand? Thank You
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 24, 2017
10:40 AM
vbp0001 wrote:
Where do I put this? Do I put it right before sCommand? Thank You
Put it some place before using LaunchApplication.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2017
03:08 PM
rguggisberg wrote:
Put it some place before using LaunchApplication.
Tried what you suggested and it did not work. This is what I got in the log file.
---- Enter Function : ClearIconCache ----
++++ WARNING: The IE Per-User Initialization Utility failed to run successfully (0X00000001).
++++ WARNING: Incorrect function.
---- Leave Function : ClearIconCache ----
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2017
03:09 PM
rguggisberg wrote:
If reply from TurboFisch does not solve problem, you could remove the /q and the SW_HIDE so that you can see any error messages.
Tried what you suggested and it did not work. This is what I got in the log file.
---- Enter Function : ClearIconCache ----
++++ WARNING: The IE Per-User Initialization Utility failed to run successfully (0X00000001).
++++ WARNING: Incorrect function.
---- Leave Function : ClearIconCache ----
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2017
03:45 PM
Looking at your original post (f the code is still that way) you have defined sInitUtilityFile .. but did not include it in sCommand.
I tried to post corrected code but got whacked by the security policy of this site 😞
You should also remove the quotes from the definition of sInitUtilityFile so that they don't get doubled up.
I find that it is often a good idea to display a message box or sprintf of the command line... at least temporarily for test.
I tried to post corrected code but got whacked by the security policy of this site 😞
You should also remove the quotes from the definition of sInitUtilityFile so that they don't get doubled up.
I find that it is often a good idea to display a message box or sprintf of the command line... at least temporarily for test.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2017
04:36 PM
rguggisberg wrote:
Looking at your original post (f the code is still that way) you have defined sInitUtilityFile .. but did not include it in sCommand.
I tried to post corrected code but got whacked by the security policy of this site 😞
You should also remove the quotes from the definition of sInitUtilityFile so that they don't get doubled up.
I find that it is often a good idea to display a message box or sprintf of the command line... at least temporarily for test.
sInitUtilityFile is included with sInitUtilityPath. I will try to remove the quotes and see what happens.
I did try to remove the quotes and I got a error #6879: 'ie4uinit': undefined identifier.
I printed out the sCommand and it is in the text file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2017
08:35 PM
There will always be things that just don't quite work the way you intended.
Get in the habit of displaying a message box or sprintf of the command line... at least temporarily for test when you have this kind of trouble.
If you display the value for sInitUtilityPath the solution will probably become obvious.
Get in the habit of displaying a message box or sprintf of the command line... at least temporarily for test when you have this kind of trouble.
If you display the value for sInitUtilityPath the solution will probably become obvious.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 15, 2018
04:47 PM
rguggisberg wrote:
There will always be things that just don't quite work the way you intended.
Get in the habit of displaying a message box or sprintf of the command line... at least temporarily for test when you have this kind of trouble.
If you display the value for sInitUtilityPath the solution will probably become obvious.
I have attached the command to the text file.
If I run the ie4unint by itself it refreshes the icon.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2018
02:22 PM
Note that this sites security policy does not let me answer exactly as I wanted to....
What OS is the target machine?
32 bit or 64 bit OS?
C:\windows\system32 will get redirected to C:\Windows\SysWOW64 on a 64 bit OS.
YES! There are 2 versions of cmd.
Try running ie4uinit from a 32 bit CMD and from a 64 bit CMD.
If you find that the 64 bit CMD is required, then play around with Sysnative.
You may have to change your command line in 1 or both places from C:\windows\system32 to %windir%\sysnative
BUT BEFORE YOU DO THAT....
I think you may be over complicating things by running via CMD at all.
You probably don't need the path for ie4uinit either. So your command line may be able to be simplified to
What OS is the target machine?
32 bit or 64 bit OS?
C:\windows\system32 will get redirected to C:\Windows\SysWOW64 on a 64 bit OS.
YES! There are 2 versions of cmd.
Try running ie4uinit from a 32 bit CMD and from a 64 bit CMD.
If you find that the 64 bit CMD is required, then play around with Sysnative.
You may have to change your command line in 1 or both places from C:\windows\system32 to %windir%\sysnative
BUT BEFORE YOU DO THAT....
I think you may be over complicating things by running via CMD at all.
You probably don't need the path for ie4uinit either. So your command line may be able to be simplified to
ie4uinit.exe -ClearIconCache