Still having probs w/ Windows Accessories

[Kent Petersen]

Got my full XPe development system today (been using the eval version up to
now). After installing it and going through the QFEs, I'm back to trying to
get the "Windows Accessories" component working. My previous post was
getting to hard to drill down to and I thought I'd start over.

I'm trying to build a pretty full XPe installation. Here's a list of (I
believe) major/pertinant components included:

-Administration Support Tools
-Control Panels (From XPeFiles.com...thanks Brad Combs) (All items enabled)
-Domain Participation
-Friendly Logon User Support
-Internet Explorer
-User Interface Core (All but prohibit access to control panel & prohibit
access to hot keys enabled)
-Windows Accessories
-Windows Logon (Standard)
-Windows XP Visual Style

The help for "Windows Accessories" says that it adds Calculator, MSPaint,
Notepad & Wordpad. Sure enough, the exe's for these apps are in the image.
When I add the "Standard Start Menu Shortcuts" component I get 51 errors
during the build process. Apparantly there's an "Invalid resource:
shortcut" error for each of the shortcuts included in the "Standard Start
Menu Shortcuts" component. What seems strange to be is that this includes
errors for notepad, wordpad & paint for which I've verified that the
executables are present (there's a bunch for the games like freecell and
solitaire that aren't there in exe form.

The "Standard Start Menu Shortcuts" component does add the "Games" folder to
the Start|All Programs menu but its empty. I can, for instance, run Notepad
or Wordpad by using Start|Run.

Any help is appreciated.

Kent Petersen

 

[Sean Liming \(eMVP\)]

Kent,

I just sent you my 85XPpro.sld that has a majority of the components.
Shortcuts are included. There is also a full XPe configuration (Vampire) on
www.xpefiles.com that Heidi created.

Regards,

Sean Liming
www.a7eng.com
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step

 

[Andy Bridge]

Got my full XPe development system today (been using the eval version up to
..
..
The help for "Windows Accessories" says that it adds Calculator, MSPaint,
Notepad & Wordpad. Sure enough, the exe's for these apps are in the image.
When I add the "Standard Start Menu Shortcuts" component I get 51 errors
during the build process. Apparantly there's an "Invalid resource:
shortcut" error for each of the shortcuts included in the "Standard Start
Menu Shortcuts" component.

Kent,

Could it be that your target Drive is something other than 'C'. The
"Standard Start Menu Shortcuts" component seems to have DstPath "hard coded"
C:\Documents and Settings....

Andy

 

[Kent Petersen]

Andy:

Indeed it is...my target is is partitioned and the c-drive is XPPro and the
d-drive is XPe. I'll have a look at the components this morning. Is there
anywhere I can change the "hard coding" of c? Otherwise I guess I'll have
to re-letter the drives on the target (and deal with whatever falls out from
that .

Thanks,

Kent

 

[Slobodan Brcin]

In few days I'll post to this NG how to change XPE drive letter to C: even
if you have XP on fist partition.

Indeed it is...my target is is partitioned and the c-drive is XPPro and the
d-drive is XPe. I'll have a look at the components this morning. Is there
anywhere I can change the "hard coding" of c? Otherwise I guess I'll have
to re-letter the drives on the target (and deal with whatever falls out from
that .

For now you can try to use following, until I write more explanations to
this.


Using Extra Registry Data from TD it is possible to assign drive letters for
every volume on target device.

We need to assign drive letter to unique volume id in TD for all volumes
that we are interested to have fixed letters. ID value can be read from
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\\??\Volume{... for every volume on
target device.

In TD we need to enter following values for every volume we need to have
assigned letter:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\\DosDevices\C: REG_BINARY xx xx xx
xx xx xx xx xx

C: - Can be any letter and represent drive letter that will be used during
and after FBA on target device.

xx - Is unique volume id that identify volume on target device.

To all volumes that are not assigned drive letters from TD, FBA will assign
available letters in increasing order.



This can be used as work around during the development process where we have
some OS on boot volume C: than prevent us from using drive letter C: for
XPE.

Using this method we can have many XPE builds in different partitions and
all of them can use drive letter C: or some other that we want.





Regards,

Slobodan Brcin