startup program in xpe

[Guest]

hi.

i created a custom shell with my win32 program, i want my program (a windows
dialog win32 program) to start up in the beginning. so created a custom
shell according to http://msdn2.microsoft.com/en-us/library/ms940838.aspx

i.e. in the custom shell component:

In the Extended Property dialog box, provide the following information:
Name: cmiShellPath
Format: String
Value: %SystemRoot%\System32\VC1.exe

VC1.exe is the application which i want it start up.

but when i reboot the xpe image, it shows :

Unable to locate component
the application has failed to start because oledlg.dll was not found,
re-installing the application may fix the program

but the application vc1.exe works fine under windows xp professional

how can i fix this problem? I don't know what's the meaning of
"re-installing the application". which component contains the file
oledlg.dll?

also, i replaced the default wallpaper with my own bmp file: set
HKEY_USERS\.DEFAULT\Control Panel\Desktop\wallpaper with my own bmp file.
when i reboot the image, the default green background wallpaper still flash
shortly then replaced with my own wallpaper. why? how can i get rid of this
short display the default background wallpaper?

thank you very much!

yours sincerely, winston.

 

[Sean Liming \(eMVP\)]

You still need to make sure all the support DLLs and features to run the
application are part of the image.

OLEdlg.dll is part of the OLE Dialog Interfaces component. You might want to
run the application against DependencyWalker (www.dependencywalker.com) to
get a listing of the DLLs that are required to run the application.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[KM]

Winston,

but the application vc1.exe works fine under windows xp professional

If you create an image with Explorer or CMD as the shell, does the VC1.exe app starts fine? In other words, did you satisfy all the
dependencies of the app in your image?

how can i fix this problem? I don't know what's the meaning of
"re-installing the application". which component contains the file
oledlg.dll?

Software/System/System Services/Application Support/"OLE Dialog Interfaces". This component is often getting missed.

also, i replaced the default wallpaper with my own bmp file: set
HKEY_USERS\.DEFAULT\Control Panel\Desktop\wallpaper with my own bmp file.
when i reboot the image, the default green background wallpaper still flash
shortly then replaced with my own wallpaper. why? how can i get rid of this
short display the default background wallpaper?

Where does it show the default system background - *before* or *after* logon screen?

If after the logon, how exactly you set the reg value? In TD or at runtime?
If TD, where you added the key to?
If at runtime (sounded like this since you "reboot" the image), you had probably already had the image working and passed by FBA at
that moment, right? Then, the HKCU (current user branches) have been already created for the user accounts you've got there set up.
Making changes in .DEFAULT branch at this point is only going to be applied to new user accounts created at runtime. You would want
to change it in HKCU branch as well so that for the user that is logged in it also shows theright background.

 

[Guest]

please tell me where i can find this componet. you said that OleDlg.dll is
part of the ole dialog interface component. but i cannot find it in the TD,
why?

also, how do i know which component a peticular DLL belongs to?

thank you very much

 

[Guest]

Software/System/System Services/Application Support/"OLE Dialog Interfaces".
This component is often getting missed

I can not find this component in TD, why?


Where does it show the default system background - *before* or *after* logon
screen?

I hid the logon screen by add automatic logon, so I don't know it's *before*
or *after" logon, since there is no logon windows.

I set the reg value In TD under "extern reg value" of slx .

Thank you very much!

 

[Sean Liming \(eMVP\)]

From the menu in Target Design, tools-> options, change the visibiliy level
to 100 and you will see the component.

You can use a filter to perform a "find component containing a file".

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[KM]

winston,

Please lower your TD Min Visibility level as Sean mentioned.

For the wallpaper please check the reg.value at run time to see if it gets set properly. Please check out the value in HKCU branch.