/build/static/layout/Breadcrumb_cap_w.png

Target in shortcut not resolving fully

Hi all,

I am in the middle of what i thought was going to be a simple single shortcut msi.
The shortcut points to a file that is located on a network share (the Z:\ drive). The full path is z:\scunthorpe\grpdata\cc&i\data\rhythm\fmd\absolve\absolve.exe.

I have declared a property for this path and called it FMDPATH. I tried creating this property through the "Set Property" Custom Action and also in the Property table but neither seem to work.

Please see the details below -

Property table - >
FMDPATH = z:\scunthorpe\grpdata\cc&i\data\rhythm\fmd\

The 3 fields of the shortcut get populated, i.e. Target, Arguments and Working Dir.

Target -> [FMDPATH]absolve\absolve.exe
Arguments -> [FMDPATH]status.rvw
Working Dir - > [FMDPATH]

My problem is this -
When i install my application the shortcut gets installed, but the FMDPATH in the Target field doesn't resolve correctly. It doesn't seem to like the fact that there are more than 8 letters in "Scunthorpe". I would have thought it was a problem with the longfilename but the property seems to get resolved correctly in the "Start in" field.

The result in the shortcut properties is as follows.

Target : z:\scunthor\grpdata\cc&i\data\rhythm\fmd\absolve\absolve.exe z:\scunthorpe\grpdata\cc&i\data\rhythm\fmd\status.rvw
Start in: z:\scunthorpe\grpdata\cc&i\data\rhythm\fmd\

Any ideas?
I'm stumped! I've never even been to Scunthorpe!!!

Cheers,
Mark

0 Comments   [ + ] Show comments

Answers (8)

Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
What's the result if you change the property table as follows?

FMDPATH = z:\aberdeen\grpdata\cc&i\data\rhythm\fmd\
Posted by: mark_holland21 18 years ago
Fourth Degree Green Belt
0
It resolves ok when i do that.

I also tried with the path being z:\scunthorpe\scunthorpe\grpdata\cc&i\data\rhythm\fmd\

Just to see if it can resolve anything in that path over 8 characters.

The thing that baffles me is the way the path gets resolved ok in the Start in: field................
Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
ORIGINAL: mark_holland21

The thing that baffles me is the way the path gets resolved ok in the Start in: field................



That's why I suggested what I did... I expected you to get "aberdeen" in one, and "scunthorpe" in the other.
Posted by: mark_holland21 18 years ago
Fourth Degree Green Belt
0
No, i get z:\aberdeen\grpdata\cc&i\data\rhythm\fmd\ in both the Target field and the Start in field.
Posted by: Foleymon 18 years ago
Orange Senior Belt
0
How about changing

z:\scunthorpe\grpdata\cc&i\data\rhythm\fmd\

to

z:\scunth~1\grpdata\cc&i\data\rhythm\fmd\
Posted by: urban_diver 18 years ago
Orange Senior Belt
0
When populating the fields in the Shortcut tab, in WrkDir do not put [ ] instead of [FMDPATH] simply FMDPATH

Hope that works out for you.
Posted by: islander222 18 years ago
Senior Yellow Belt
0
Is the network location available?

I've seen the shortcut targets getting truncated when the actual location isn't available at install time....
Posted by: mark_holland21 13 years ago
Fourth Degree Green Belt
0
Hi all,

I asked this question a couple of years back and can't remember how i ever resolved this issue.
I am faced with it once again.

I have an msi that installs a shortcut only. And that shortcut points to G:\Automotive\Databases\Capwin1

However, we are using SCCM to deploy our msi's and the G:\ drive isn't mapped for the System account which is the account that is installing this msi.
Therefore, as a result of there not being a G:\ drive mapped windows truncates the Target of the shortcut from

G:\Automotive\Databases\Capwin1
to
G:\Automoti\Database\Capwin1

Note that the ve is missing from Automotice and the s is missing from Database.
Therefore it only allows 8 characters.

Anyone ever had this problem before?
Stupidly I didn't note on AppDeploy how I resolved my issue - if i ever did!

Is VBScript the only way to go?

Rgds,
Mark
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ