Re: XPE Shortcuts - is this a bug?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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?

--
Regards,
KM


> 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" wrote:
>
>> 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?
>>
>> --
>> Regards,
>> KM
>>
>>
>> > 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" wrote:
>> >
>> >> 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
>> >>
>> >> --
>> >> Regards,
>> >> KM
>> >>
>> >>
>> >> > 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
>> >> >
>> >> > "KM" wrote:
>> >> >
>> >> >> 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?
>> >> >>
>> >> >> --
>> >> >> Regards,
>> >> >> KM
>> >> >>
>> >> >>
>> >> >> > 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
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


.

Relevant Pages

  • Re: Cant set pagefile WinXP Home SP2
    ... I ghosted the boot NTFS partition of this machine and upon exploring the ghost file discovered that pagefile.sys does indeed exist and hasn't been modified in 5 days despite my MANY reboots and setting changes. ... I need to delete this file by using a third party disk editor or disk tool set or I need to backup the partition, delete the file from the backup, then restore the backup over a freshly formatted partition. ... machine would boot but hang at the loading personal settings phase. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Target Designer, Target Device Settings
    ... Have you made sure that the partition you are instaling the image to, ... if you have a FAT partition, try and run bootprep on the target device. ... the Target Device settings are just like they are ... Boot ARC Path ...
    (microsoft.public.windowsxp.embedded)
  • Re: BootIt NG high level steps - best approach??
    ... backup boot strategy. ... As far as BING, I should tell you I've been using this software ... make managing your bootable options and partition management so much easier. ... drives) and the DATA partition on a mirrored array. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Dual booting
    ... of Microsoft's dual boot scenario. ... The extended partition is not assigned a drive letter, ... BIOS reserves letters A and B for floppy drives, ... If WinXP Setup ...
    (microsoft.public.windowsxp.general)
  • Re: Dual Boot Instructions
    ... I ended up reinstalling Vista, ... The boot SECTOR is not the bootLOADER. ... finds the partition table for that HDD and sees that the first partition is ... violated, we no longer can simply install WinXP, install Vista and ...
    (microsoft.public.windows.vista.hardware_devices)