Shortcuts strange behavior
A network application is copied manualy on our v: drive.
Then we install a package on the workstation
(shortcuts, ini, a few regkeys...).
3 non-advertized "command-style" shortcuts are
installed pointing to the same exe but with different arguments.
SEE IMAGE :
http://img.photobucket.com/albums/v180/zulumika/Installer/virtuoInstaller.jpg
Once installed, the shortcut's command lines are
different : the target line is missing a letter.
Originaly I point to "[path]\runvirtuo.exe" but
once installed, the target is "[path]\runvirtu.exe".
The "o" is missing!!!
SEE IMAGE :
http://img.photobucket.com/albums/v180/zulumika/Installer/virtuoShortcut.jpg
It smells 8.3 do you think?!
I searched through all tables for a "runvirtu" (without the "o") ; nothing.
Recompiled the package 4 times, redid the entire msi on
another freshly imaged workstation ; same results.
Did another snapshot of the shortcuts in a new msi ; same results.
Any thought is muchas appreciated.
Thanks.
Then we install a package on the workstation
(shortcuts, ini, a few regkeys...).
3 non-advertized "command-style" shortcuts are
installed pointing to the same exe but with different arguments.
SEE IMAGE :
http://img.photobucket.com/albums/v180/zulumika/Installer/virtuoInstaller.jpg
Once installed, the shortcut's command lines are
different : the target line is missing a letter.
Originaly I point to "[path]\runvirtuo.exe" but
once installed, the target is "[path]\runvirtu.exe".
The "o" is missing!!!
SEE IMAGE :
http://img.photobucket.com/albums/v180/zulumika/Installer/virtuoShortcut.jpg
It smells 8.3 do you think?!
I searched through all tables for a "runvirtu" (without the "o") ; nothing.
Recompiled the package 4 times, redid the entire msi on
another freshly imaged workstation ; same results.
Did another snapshot of the shortcuts in a new msi ; same results.
Any thought is muchas appreciated.
Thanks.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
sean_c_roberts
19 years ago
Hmmnn...
A few ideas:
1) Are you sure you are not exceeding the 255 character command-line limit of your shortcut?
2) Are you SURE you're not advertising these shortcuts?
3) Make your own shortcuts manually, confirm that they work properly, and then just copy the .lnk files onto your target machine.
Good luck!
- Sean Roberts
A few ideas:
1) Are you sure you are not exceeding the 255 character command-line limit of your shortcut?
2) Are you SURE you're not advertising these shortcuts?
3) Make your own shortcuts manually, confirm that they work properly, and then just copy the .lnk files onto your target machine.
Good luck!
- Sean Roberts
Posted by:
Zulumika
19 years ago
1) I'm sure (see image)
2) I'm sure (see image again)
3) my last resort ... but ok, I'll have to do that.
Thanks.
2) I'm sure (see image again)
3) my last resort ... but ok, I'll have to do that.
Thanks.
Posted by:
Fisa
19 years ago
I think Sean was pointing in the right direction about this problem. I encountered similar problem whereas the arguement/s in the commandline doesnt take the toal path.
Probable soln:
If the argument is pointing to a directory in the msi, then use its property from the directory table. eg- [runvirtuo] instead of [path]runvirtuo
Probable soln:
If the argument is pointing to a directory in the msi, then use its property from the directory table. eg- [runvirtuo] instead of [path]runvirtuo
Posted by:
Zulumika
19 years ago
ok, my bad : I used the expression [path]\runvirtuo as an example to explain what`s going on. As suggested, I have a property for pretty much all my paths. (actualy, wise did it for me)
Posted by:
mfl
19 years ago
Sure you have resolved this by now but in case anybody else needs a solution.
It looks like a symptom of
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b263324
ie due to either the network drive not being available when yuo install or the drive not supporting lfn.
It looks like a symptom of
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b263324
ie due to either the network drive not being available when yuo install or the drive not supporting lfn.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.