XPE Shortcuts - is this a bug?

[Guest]

Hello all,

I have created an image that includes the standard shortcuts component. My
image is designed to run on drive D: of the destination PC, and this is
reflected in the settings of the image (location of windows/etc).

However, when I look at the shortcuts, they are all pointing to
"C:\WINDOWS...", i.e. the C drive, not the D drive. It does not change with
the settings of the destination in the target designer.

Is this a bug or do I manually have to change the settings of the shortcuts?
If I do, then change the destination drive to "C:", would I need to change it
back?

All help appreciated,

D

 

[KM]

Babbler,

Are you referring to some system shortcuts (this are supposed to work properly if you set up all the settings correctly in TD).

Or some custom shortcuts of yours?

 

[Guest]

Hello,

I am referring to the system ones (such as notepat, etc). Do I need to
remove the standard shortcut compnent and add it again to re-create the
shortcut mapping if I change the settings in TD? I manually went through and
changed all the "c:\..." to "D:\...". These shortcuts don't seem to appear
anyway, but FBA has no errors.

Is there a simpler way for custom shortcuts as well? Not sure if I am doing
things correctly.

I know its confusing, but hard to explain,

Thanks in advance,

Damian

 

[Guest]

Addednum:

I removed and added it again, but still no joy. Resources shows the
shortcust as "C:\...".

 

[KM]

Babbler,

No, you don't have to add/remove the component to re-apply settings. The shortcut paths will be calculated during build time if
dynamic.

Can you provide the following info:
- What you've got on the Configuration Settings page/Target Device Settings section?
- What component you are referring to that has those shortcuts?

If it is the "Standard Start Menu Shortcuts", then please note that all DstPath properties there set to "C:\". Basically hardcoded.
I don't know why such implementation has been chosen but it does seem like a bad design.
Microsoft folks may correct me if I am wrong but it doesn't seem that TD fixes up the destination paths for shortcuts.

Babbler,
If acceptable to you and without much work on every shortcut you can use this trick to work on with C:\ drive letter on your builds:
http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx

 

[Guest]

Thanks. You just told me what I suspected. The shortcuts were hardcoded .
Guess I will have to use the trick.

It does seem a bit of a strange choice by MS considering most the stuff is
dynamic. Will give it a go tomorrow when back in the office.

Damian

 

[KM]

Babbler,

Actually, I looked at the database and TD scripts and I found the script that is responsible for fixing up the Shortcut resource
destination paths.
Also, on my runtimes the problem is not exposed. All the shortcuts from the "Standard Start Menu Shortcuts" are set up correctly.

It must be something else in your config.

Can you show us what you've got under Target Device Settings section on Configuration Settings page?

 

[Guest]

Sure thing - if it helps

"Boot Drive: D: (although I have had this as C and it made no real
difference).
Windows Folder: D:\Windows
Prgram Files Folder: D:\Program Files
Documents and Settings: D:\Documents and Settings
Boot Arc Path: Multi(0)disk(0)rdisk(0)partition(2)
Boot Partition Size: 2048
Partition Cluster Size: 4096
"

Thanks again.

 

[KM]

Babbler,

Looks good to me. Except the boot drive.
Where do you have ntldr located? (which partition is primary active one?)

Also, how about checking out the shortcuts under All Users\Start Menu\Programs\Accessories in PRE-FBA image (just built image)?
If you test the properties of any LNK file there, the target of the shortcut should point to D: drive. Is this correct?

 

[Guest]

Hmmmm... very strange.

I think I must be missing something. Have set the boot back to C: (thanks).
Checked the pre-FBA image and found no system related LNK files, even
thought I have "Standard Start Menu Shortcuts" included.

The only LNK files are those that belong to my application - and they point
to "C:\..." when it should be D. Somehow these work though??

Very confused now. No wonder the shortcuts arent showing if they're not in
the image! What do I need to add or is there something else wrong? The
applications are there (for example, networking).

Thanks again.

 

[KM]

Babbler,

Are you sure you are checking the right pre-FBA image build folder?
What file you see there under <pre-FBA image build folder>\DriverD\Documents and Settings folder?

Do you have <pre-FBA image build folder>\DriverD\Documents and Settings\All Users\Start Menu\Programs folder there? Any file [LNK]
in that folder?

 

[Guest]

Ok, think I have found 2 problems...

1) I did a search in my second to last build (the one before I hardcoded the
shortcuts in target designer to "D" instead of "C"). It came up with the
system shortcuts BUT they were pointing to "C:\Windows\%homedrive%%homepath%"
I presume this is wrong! Not sure why it is doing this.

2) In my hardcoded build no shortcuts are in that folder. Guess it is
looking on the D drive of my development machine, not finding them and
ommitting them.

Guess 1 would be easier to fix? Any ideas why it is doing this?

Thanks again.

Babbler,

Are you sure you are checking the right pre-FBA image build folder?
What file you see there under <pre-FBA image build folder>\DriverD\Documents and Settings folder?

Do you have <pre-FBA image build folder>\DriverD\Documents and Settings\All Users\Start Menu\Programs folder there? Any file [LNK]
in that folder?

--
Regards,
KM

Hmmmm... very strange.

I think I must be missing something. Have set the boot back to C: (thanks).
Checked the pre-FBA image and found no system related LNK files, even
thought I have "Standard Start Menu Shortcuts" included.

The only LNK files are those that belong to my application - and they point
to "C:\..." when it should be D. Somehow these work though??

Very confused now. No wonder the shortcuts arent showing if they're not in
the image! What do I need to add or is there something else wrong? The
applications are there (for example, networking).

Thanks again.