Target Designer problem with shortcut resources

  • Thread starter Thomas Heinrich
  • Start date
T

Thomas Heinrich

Hi All,

I don't know if this was already discussed earlier.
I have a component with a Shortcut resource, the shortcut
should appear in the Startup folder of All Users.
My target should boot from partition D: and I build
it on my development system in a subdirectory.
Nothing happens on my client so I checked the lnk file
in my build. All the path and file names were in 8.3
format (truncated).
I do not know how TD creates the lnk file, reason for
this behaviour is my development system has no partition D:
After I created a partition D: and rebuild the target
the lnk file was OK.

Is this a known problem ???

Best Regards,
Thomas Heinrich
Wincor Nixdorf International GmbH
 
J

James Beau Cseri

Does your shortcut resource use hard-coded paths? If so, you should use
DIRIDs (i.e. use %10% to indicate the \Windows folder). I'm not sure if that
would be the cause of your problem, but maybe.
 
T

Thomas Heinrich

I am using DIRIDs like %11% for the command and %16408% for
the shortcut, its really the problem that they all point to
D: in my build and D: was not available on my development
system.

Thomas
 
K

KM

Thomas,

I have learnt that using environmental variables (%SystemDrive%, %SystemRoot%, etc.) instead of the INF vars may work better in some
situations. Mainly because of the fact when the vars get expanded: the environmental ones at run time, the INF ones - at the build
time. Therefore the latter have some dependencies on the dev. build machine configuration (TD script checks and expands these
variables).

It will definitely work for your shortcuts if you use %SystemRoot%\system32 and etc.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top