Component troubleshooting - Microsoft Windows Embedded Standard 2009 Developer Resource Kit Componentizing Windows...

Component troubleshooting
This section contains component-specific tips and tricks, as well as information about error messages and exceptions.
Apply the tips listed below, only if your device experiences the symptoms indicated, because a subsequent Service Pack or update may have already remedied the problem.
Review the Release Notes.htm file on the CD-ROM first. In particular, review the Components section for possible components issues. If you are building SP2 images, use the Release Notes on the SP2 CD.
What to do if you are having trouble finding components
If you know the name or partial display name of the component, you can search Target Designer for this component. Do not forget that if the visibility of the component is less than your current setting (default is 1000), some components will be hidden from you. Simply reduce your visibility (for instance to 200), and you will see additional components.
Use the companion Excel spreadsheet (Windows Embedded Standard 2009 Components.xls), to assist in choosing and picking components.
If you do not know the name of the component but you do know a file name that is part of a feature that you want, you can use Filter Manager in Target Designer to locate the component that owns that binary.
Application Compatibility Core
Event Viewer reports "Error Application Popup EventID 877: Description: Database open failed".
This is a bug where Drvmain.sdb is not owned by any component, it should be owned by the App Compat Core component and the file should be copied to %systemroot%\AppPatch folder.
The Drvmain.sdb file is the "bad driver database" so when a driver is loaded, Plug-and-Play checks this database, and blocks any drivers flagged as such. Even though the error appears to be harmless, to resolve this problem, manually copy this file to the AppPatch folder.
Application Verifier
The Application Verifier component file resource, Verifier.dll, has an undeclared raw dependency on Dbghelp.dll. Dbghelp.dll is owned by the Primitive: Dbghelp component. Manually add Primitive:Dbghelp to your configuration, which will ensure that Dbghelp.dll is included in your configuration.
ATI Rage Mobility
If you are using an ATI Rage Mobility Pro or RADEON 9000 video adapter in a configuration, you will find that the ATI Hotkey Poller Service entry that accompanies the ATI Rage Mobility Pro drivers may not start properly in the run-time image. This causes the video adapter to be incorrectly installed after the run-time image is complete. To properly use the service that is supplied in the .inf files for this video adapter, you must first disable the ATI Hotkey Poller service entry in the component resources. During the initial boot of the run-time image, the ATI Hotkey Poller is then installed and started correctly. This allows you to use the full functionality of the ATI Rage Mobility Driver in the run-time image.
Automatic Logon The Automatic Logon component does not properly log on to the domain after the runtime starts
This behavior occurs because the Automatic Logon component does not bring in the Domain Participation support component after you set the option to have the runtime log on to the domain. Include Domain Participation in your design.
Automatic logon fails when the System Cloning Tool component is included
By default, the System Cloning Tool overwrites the following information:
AutoLogonUser
AutoLogonPassword
AutoLogonDomain
If you use the System Cloning Tool component, make sure that you apply the following hotfix for it to your database first:
Windows XP Embedded - Auto-Logon Information Not Retained When Using System Cloning (Q322200)
To retain the settings in the Automatic Logon component, set the cmiRemoveAutoLogon extended property in the System Cloning Tool to FALSE.
Background Intelligent Transfer Service
The Background Intelligent Transfer Service (BITS) may not start because of some incorrect settings. To resolve this problem:
Change the service log on setting to Log on As Local System Account.
In the registry, change the BITS service ImagePath key to:
%SystemRoot%\system32\svchost.exe -k netsvcs
Client for Microsoft Networks
In the "Client for Microsoft Networks Properties" UI, under the RPC Service tab, you'll find that the "Name service provider" field is initially empty. Closing this UI using the OK button will cause Explorer to AV (access violation) or the UI might just hang.
Include the "RPC Named Service" component in your Standard 2009 build and deploy a new image.
See this article (KB 883104) for details:
The Name service provider field is empty on the RPC Service tab in the Client for Microsoft Networks Properties dialog box
Client Services for NetWare
If you experience difficulties installing and configuring Client Services for NetWare on Standard 2009 images, you may need to copy .inf files before booting your run-time image or running First Boot Agent (FBA). Copy the files to DIRID %17%. By default, DIRID %17% is the Windows\Inf folder. The following list shows the .inf files you can copy from the repository:
Netnwcli.inf
Netnwlnk.inf
Netnovel.inf
Netmgr.inf
Netnm.inf
CMD – Windows Command Processor
If the Null device (NUL) in Cmd.exe does not work, add the Null Device Driver component.
Command Shell Command shell runtimes may not be able to use the Image Viewer toolbar in Internet Explorer
Run-time images that include the command shell in Internet Explorer may generate the following error message when you try to use the Image Viewer toolbar to view images.
Windows cannot find "/idlist, :2712:1964,D:\Documents"
To resolve this issue, add the Explorer Shell component.
Explorer Shell Disabling the taskbar "always on top" feature
Start Regedit.
Find the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2
Double-click the Settings property, and then change the value after the four FFs to 00 (disable) or 02 (enable), as shown in the following example:
(Disable) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2
"Settings"=hex:28,00,00,00,ff,ff,ff,ff,00,00,00,00,03,00,00,00,3e,00,00,00,1e,00,00,00,fe,ff,ff,ff,e4,02,00,00,02,04,00,00,02,03,00,00
(Enable)
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2
"Settings"=hex:28,00,00,00,ff,ff,ff,ff,02,00,00,00,03,00,00,00,3e,00,00,00,1e,00,00,00,fe,ff,ff,ff,e4,02,00,00,02,04,00,00,02,03,00,00
Restart the computer by running the Down.exe utility with the /R /Q /F options. You can obtain Down.exe from the following Web site:
http://www.losoft.de/download/ls-tools.zip
The right hand nibble (four bits) of the 02 contains two other Taskbar and Start menu properties as shown below:
0010
| | | |
| | | +----- Auto hide (0 = disable, 1 = enable)
| | +------- Always on top (0 = disable, 1 = enable)
| +--------- Unknown
+----------- Show clock (0 = enable, 1 = disable)
Device Manager
When you open the COM port properties in Device Manager, and then click Advanced on the Port Settings tab, you may receive the following error message:
You must have write privileges in the registry for this device in order to modify the devices advanced settings.
This behavior occurs because there are three missing registry subkeys from the following registry key:
HKEY_LOCAL_MACHINE\system\currentcontrolset\enum\acpi\pnp0501\2
The missing keys are:
RxFIFO
TxFIFO
ForceFifoEnable
Disk Management Services
The Disk Management Services component has an undeclared dependency on the PnP (User Mode) component.
Display Control Panel Common problems The default Windows XP Visual Style does not work in Standard 2009
If you add the Windows XP Visual Style component to a configuration, also add the Display Control Panel component.
You cannot select or configure screen savers
If you add the Screen Savers component, you must also add the Display Control Panel component or the Screen Saver selection dialog box is not available in the runtime.
Screen saver does not start after the timeout period has elapsed
To resolve this problem, add the following registry key:
HKEY_CURRENT_USER\Control Panel\Desktop
Name: SCRNSAVE.EXE
Type: REG_SZ
Data: %windir%\System32\xxxxxxxx.scr
Where xxxxxxxxx.scr is the name of your chosen screen saver. By default, screen saver files are stored in the Windows\System32 folder.
Deploying this onto a finished runtime image should be easy: just create a .reg file to do so. Here is what to put into the file:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Control Panel\Desktop] "SCRNSAVE.EXE"="%windir%\\system32\\"
The above registry configuration is owned by the DOS Windows on Windows Support component.
If the footprint of the DOS Windows on Windows component is not too high for you, you can simply include it. Note that this component has a visibility of 200, so you need to set your minimum visibility to a value of 200 or less. To do so, in Target Designer, click Tools->Options, click the Advanced tab, and then set your minimum visibility to a value of 200 or less.
Otherwise, you can create a new component that declares the registry entry as its own.
How to disable Control Panel icons (while in the runtime and from Target Designer)
There is a registry key that performs this function if the control panel icon is created from a .cpl file. Simply add the name of the .cpl file to a REG_SZ value name (the actual value name is the .cpl file name), and this value name has no value information located within it. Add this key at the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\don’t load
If you need to do this offline in Target Designer, just add the value name or names to the "Extra Registry Data" at the top of the configuration.
DOS Windows on Windows Support
When you try to run a 16-bit application, you may receive the following error message:
16 bit Windows Subsystem
An installable Virtual Device Driver failed Dll initialization. Choose "Close" to terminate the application.
This behavior occurs because earlier applications, such as 16-bit applications, require the DOS Windows on Windows Support component. To resolve this problem, include the DOS Windows on Windows Support component. You must reduce your visibility in Target Designer to 200 or less to see the component.
Error Reporting
If you add the Error Reporting component to a configuration, add the Terminal Services macro component.
Event Logging
In Standard 2009 the errors in the Event log may not be detailed. To get more detailed Event log information, you can use one of two approaches:
Option 1. Log onto the Secure OEM web site and download the February 2009 optional update. Excerpted from the site:
The Supplement contains the following:
Boot.ini macro component licensed for use with Windows® Embedded Standard 2009. This functionality allows Windows® Embedded Standard 2009 customers to configure boot settings from within Target Designer.
The supplement also contains Registry key additions to the Event Log component licensed for use with Windows® Embedded Standard 2009 and Windows XP Embedded.
Option 2. For testing and debugging purposes only, copy the following registry keys and their subkeys and values from the registry on a Windows XP Professional computer, to the registry in your embedded runtime, and then restart the runtime:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application
You can accomplish the registry copy using the export and import features of Registry Editor.
Message resource DLLs referenced in the above key paths may also be missing from the Standard 2009 image. You may need to manually copy those across as well.
Hardware Abstraction Layer
When you start your runtime, if your screen appears black with an underline non-blinking cursor in the upper left corner, it is possible that you chose the wrong Hardware Abstraction Layer (HAL).
One component that contains Hal.dll is included in your runtime. It can manifest as any of the following components. The file name in parentheses is the source name. In all cases, the file is renamed Hal.dll in the runtime image. You must know these source names if you intend to use the kernel debugger and replace Hal.dll with its checked build equivalent source name.
Standard PC (Hal.dll)
ACPI Multiprocessor PC (Halmacpi.dll)
ACPI Uniprocessor PC (Halaacpi.dll)
Advanced Configuration and Power Interface (ACPI) PC (Halacpi.dll)
Compaq SystemPro Multiprocessor or 100% Compatible (Halsp.dll)
MPS Multiprocessor PC (Halmps.dll)
MPS Uniprocessor PC (Halapic.dll)
If you are not sure which component to select, start with Standard PC.
If you are using a multiprocessor system, Standard 2009 has the same processor support as Windows XP Professional, which is a maximum physical processor limit of two and a maximum logical processor limit of four (two physical processors, each supporting two logical processors).
You can modify the following settings in the advanced properties of the HAL component:
Paging file enabling, initial size, and maximum size
Registered owner (OEM)
Registered organization (OEM)
Computer name
Workgroup
Hibernation enabling
Help and Support Services
Some .chm files require the Help and Support Services component. If you use one of these files and do not add the Help and Support Services component to your configuration, you may receive script error messages.
Home Gateway
The Home Gateway macro component contains a Config UI option for the IIS Technologies component. However, IIS is not used for the scenario. This is a known issue. To work around this problem, click to clear the Config UI check box.
HyperTerminal
HyperTerminal requires additional components. If you add the HyperTerminal component to a configuration, you must add the TAPI 2.2 Client component. You may also add the Phone and Modem Control Panel component.
Images and Media
If User Account pictures are not visible in the Friendly Logon User Interface, add the Images and Media component. This component allows the pictures to show up for the users instead of the default chess piece.
IMAPI – CD Burning
To burn a CD, add the IMAPI - CD Burning component. This component enables you to burn CDs in the Windows Explorer window as well as in Windows Media Player.
Internet Explorer Kiosk Mode
A useful “kiosk mode” is built into Internet Explorer. This feature makes Internet Explorer fill the entire screen, and removes the URL field, if you want a turnkey kiosk with tighter control over where the user is allowed to browse. See these links for details:
How to use Kiosk Mode in Microsoft Internet Explorer (KB154780)
IE as the shell (in Kiosk Mode)
IME Prototype
The keyboard input locale is not saved when you log on and off the runtime or restart the runtime.
To resolve this problem, ensure that the IME Prototype component is in the runtime. The IME Prototype component owns the registry keys that are needed for this process.
Internet Explorer The My Pictures folder does not load properly in the Command Shell
Internet Explorer supports an Image toolbar with four buttons, one of which opens the My Pictures folder. If you click the button that opens the My Pictures folder when Internet Explorer is not running, an error occurs, and Internet Explorer is started. To avoid this issue, disable the Internet Explorer component property called Enable Picture Toolbar while you are using Command Shell components.
The custom home page does not load properly in the runtime
To enable the custom home page to load properly in your runtime, you must specify the protocol in the cmiIEHomePage field of the Internet Explorer component Advanced settings. Alternatively, you can use the component’s Settings user interface, and set the Home Page URL field to your homepage. Here is an example of the format that you need in order to specify a working URL:
http://www.microsoft.com
The custom online support page does not load properly in the runtime
To enable the custom online support page to load properly in your runtime, you must specify the protocol in the cmiIEHelpPage field of Internet Explorer Advanced settings. Alternatively, you can use the component’s Settings user interface, and set the Online Support URL field to your homepage. When you set the value, specify the complete URL, here is an example::
http://www.microsoft.com
The custom search page does not load properly in the runtime
To enable the custom search page to load properly in your runtime, you must specify the protocol in the cmiIESearchPage field of Internet Explorer Advanced settings. Alternatively, you can use the Config UI and set the Search Page URL field to your homepage. When you set the value, specify the complete URL, here is an example::
http://www.microsoft.com
Map Network Drives/Network Places Wizard
It may appear that Map Network Drive/Network Places Wizard component has missing dependencies. However, this is not the case. Some components require the selection of other components that have a visibility as low as 100. To view these additional components, you must lower the visibility in Target Designer to 100, and keep the visibility set to 100 throughout the life of the configuration. This is also true for any other development system that will host these configurations.
The Map Network Drive/Network Places Wizard component requires you to manually add these components:
Primitive: MPRUI
Msxml Libraries
Message Queueing (MSMQ)
You need to register a DLL for the Message Queuing (MSMQ) COM Library component and the Message Queueing (MSMQ) DCOM Library component after you install the runtime.
To enable full functionality support of both components, register the Mqoa.dll file by creating a First Boot Agent COM/DLL Registration resource or by running the following command at a command prompt:
regsvr32.exe mqoa.dll
Failure to register Mqoa.dll will result in failure of applications using IDispatch, such as Microsoft Visual Basic® Scripting Edition (VBScript) programming language and Active Server Pages (ASP).
Microsoft Management Console (MMC)
If you add the Microsoft Management Console (MMC) component to a configuration, you must also add the MSXML 3.1 component.
MIDI
MIDI may not work in your runtime. The progress bar may show that MIDI is playing, but there is no audio.
To resolve this problem, add the Roland Sound Canvas Sound Set component. The visibility for this component is 200.
The file resource that enables MIDI is Gm.dls, which is licensed by Microsoft from Roland Corporation. Additionally, the component is a part of the DirectMusic Core dependency chain.
Minlogon
For an introduction to Minlogon, visit the following Microsoft Web site:
Introduction to MinLogon
If you cannot create a static connection to a share using the MinLogon component coupled with the Command Shell in your runtime, include the following component, which is missing from the Net.exe Utility component:
Network Command Shell Interface Context
.NET Framework
The .NET Framework development tools, Regasm and Gacutil, may not work or may stop responding when your runtime uses the Minlogon component instead of Windows Logon.
The .NET Framework has an undeclared dependency on some components that are normally included with WinLogon.
Regasm.exe and Gacutil.exe throw exception errors when they are run from within the runtime. To resolve this problem, use Windows Logon instead of Minlogon.
Problem Installing .NET Framework 1.1 update from the Embedded OEM secure web site
When trying to install the Desktop run-time (non-componentized) version of .NET framework update, MS05-004 (887219) that you obtain from the Embedded OEM secure site (which incidentally are exactly the same as the XP Pro updates) on a Standard 2009 runtime, the installation fails with ERROR_PATCH_TARGET_NOT_FOUND. This error indicates that the patch is inapplicable to the product. This problem is applicable to all versions and service packs of the .NET framework.
This occurs because the .NET Framework component is installed on Standard 2009 as an optional component using the Optional Component Manager (OCM). This is equivalent to the one installed by default on Windows Server 2003 for .NET 1.1 framework and "Tablet PC / Media Center" for .NET 1.0 framework. However the version of .NET framework updates that you install onto XP Pro (and which we post on the OEM secure site for Standard 2009 customers) is the MSI version and that expects the .NET framework to have been installed as an MSI package (as is the case for .NET framework on XP Pro) and not as an optional component.
Use the following workaround to enable installation of the "Tablet PC / Media Center" or Windows Server 2003 .NET framework security updates onto Standard 2009 runtimes:
1. Figure out the exact version of the .NET Framework you have (major and minor version plus service pack). If you are using the .NET 1.0 component we shipped, it will be 1.0 SP2. If you are using the .NET 1.1 component we shipped, it will be 1.1. If you are using the .NET 1.1 component in the value-add folder of XPe SP2, it will be 1.1 SP1
2. Click on this search result:
http://www.microsoft.com/downloads/results.aspx?freetext=security_patch&productID=C9C8FCFB-BFF3-40CA-B59D-216F6850000A&DisplayLang=en
and locate the hotfix that matches the version of the .NET Framework you have. You will need to choose the version that is specifically marked for "Tablet PC / Media Center" (for 1.0 hotfixes) or "Windows Server 2003" (for 1.1 hotfixes)
3. Download the exe for the hotfix from the download center
4. Extract the exe to a local folder by running /x:
5. If you have a service pack of 1.0 or 1.1 installed you will need to add an additional registry value that the update package is checking for as a prerequisite (so if you only have the 1.1 component we shipped you can skip this). You need to add HKLM\Software\Microsoft\Updates\.NETFramework\1.1\SP1, DWORD Installed=1. Note that this key name should be changed as needed to 1.0 or to a different service pack level if there is a higher .NET Framework SP installed.
6. Go to the folder that you extracted the .NET Framework hotfix to in step 4 above and open each of the update*.inf files in the update folder. There is a [Version] section at the top that you will need to update the following values for:
NtBuildToUpdate=2600
NtMinorVersionToUpdate=1
MinNtServicePackVersion=###
MaxNtServicePackVersion=###
ThisServicePackVersion=###
The values of Min, Max and This for service pack should match the CSDVersion value in your registry at HKLM\System\CurrentControlSet\Control\Windows. For XP Embedded SP2 this value should be 512 for example.
7. Now you can run update.exe from the update folder on your embedded device, assuming your embedded device has desktop update installer support, or includes the dependencies update.exe needs to run correctly; see the following section for details:
Updating Standard 2009 runtime images after they have been deployed
.NET Framework 2.0
Please refer to the document, Installing_DotNet_Framework.doc, found here:
Microsoft Windows XP Embedded SP2 Resource Kit
Net.exe Utility
To obtain the net use command functionality, install the Net.exe Utility component.
When you use the net use command to connect to a network share that uses a drive letter, for example: net use f: \\servername\sharename, you may receive the following error message:
System error 126 has occurred.
To resolve this problem, add the Network Command Shell Interface Context component.
NetBIOS Driver
To make sure that the NetBIOS Driver component works properly in a configuration, also add the PnP (User-mode) component.
NetMeeting Common problems NetMeeting does not receive or transmit audio or video
NetMeeting® has an undeclared dependency on the Quality of Service RSVP component. For NetMeeting to function properly, you must add the Quality of Service RSVP component.
After you install the 331042 hotfix for Headless Support, the NetMeeting Shared Files icon is unavailable
If you require NetMeeting and you install the 331042 hotfix for Headless Support, you must remove the following registry keys from the SYSTEM.SAV hive file after you create the run-time image but before you run First Boot Agent (FBA). To do so:
Run Regedit on a Windows XP Professional-based computer.
Load SYSTEM.SAV as a hive (name it "myhive" if you want).
Edit the corresponding myhive branch, and then unload it.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\mnmdd\Enum\0 - REG_SZ - "Root\\LEGACY_MNMDD\\0000"
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\mnmdd\Enum\Count - REG_DWORD - 1
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\mnmdd\Enum\NextInstance - REG_DWORD - 1
Some functions of Netsh.exe may not work
The Netsh.exe application has some undeclared dependencies. To gain all functionality of Netsh.exe, you may need to add the following components:
Network Command Shell
Network Command Shell Interface Context
IP Router Monitor Library
Network Configuration
To see your network connections, make sure that the Network Configuration component is included in the runtime. Also make sure that the hardware for connectivity is in the runtime.
The IPX/SPX protocol on Standard 2009 does not start automatically on start up
There are three ways to resolve this problem.
Method 1
In Target Designer, add a First Boot Agent (FBA) generic command with the following parameters under the resources of the root component. Leave the other parameters set to their default.
Arguments: -v -l %17%\netnwlnk.inf -c p -I MS_NWIPX
FilePath: %11%\snetcfg.exe
Phase: 5600
Method 2
At a command prompt on your runtime, run the following command:
snetcfg -v -l %windir%\inf\netnwlnk.inf -c p -I MS_NWIPX
Method 3
Manually add the NWLink IPX/SPX/NetBios Compatible Transport Protocol to your Local Area Connection properties in the network properties of your runtime.
Oledb Provider for Internet Publishing
If you add the Oledb Provider for Internet Publishing component in a configuration, you must run regsvr32 from Program Files\Common Files\System\OLE DB\Msdaipp.dll at run time.
Performance Monitor Microsoft SQL Server Desktop Engine (MSDE) SQL counters are not available
By default, the SQL counters are not available in Performance Monitor in the runtime. To add and monitor SQL counters:
Add the following components to the runtime:
Performance Monitor
Performance Counter Configuration
CMD - Windows Command Processor
Net.exe Utility
In Target Designer, view the registry keys for the Performance Counter Configuration component, and disable the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009
After you start the runtime, run the following commands from a command prompt:
unlodctr mssqlserver
lodctr sqlctr.ini
net stop mssqlserver
net start mssqlserver
Performance Monitor does not show some counters without a paging file
Performance Monitor has a dependency on the presence of a paging file. Without the paging file, you will be missing counters for the following:
Cache
Memory
Objects
Processor
System
To work around this problem, add paging file support for a paging file of at least 2 MB. Set the minimum to 2 MB and set the maximum to 2 MB.
Performance Counter objects are not all visible
You may need to edit the registry in order to enable performance counters. Click on this link for more information:
Disable Performance Counters
Remote Access (RAS)
RAS depends on Jet Database.
Remote Assistance Channel
Remote assistance is not enabled by default. The following registry value enables Remote Assistance.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Remote Desktop\Policies\fAllowToGetHelp
This value is overwritten by the Terminal Services core component while First Boot Agent (FBA) is running. To enable Remote Assistance, you must use Target Designer to manually set the Remote Assistance registry value to 1 before you build your run-time image.
Remote Registry Service
The Remote Registry component has the following dependency issues:
If you add the Remote Registry component to a configuration, you must also add the RPC Remote over Named Pipes component.
Desktop Wallpaper preview does not function unless you add the Windows Picture and Fax Viewer component.
Search Assistant User Interface
The Search Assistant User Interface component requires additional components. If you add the Search Assistant components, make sure that the Msxml3.1 component and the Internet Explorer component and its dependencies are included in the runtime.
Serial Input Support
The Serial Input Support component requires an additional component. If you add the Serial Input Support component to a configuration, you must also add the Accessibility Control Panel component.
Security Shell Extension
You may not see all the security policies in Local Security Settings. This behavior occurs because the Sceregvl.inf resource file is not associated with a Standard 2009 component (this issue has since been corrected and it is part of the Security Shell Extension component).
To resolve this problem, recreate the owning component. Basically, it contains three resources: a file resource, an FBA DLL Registration, and some dependencies.
The file resource is Sceregvl.inf. Place it in the %17% folder (\Windows\Inf). It is already in the Standard 2009 repository, but is not owned by any component.
The FBA DLL Registration goes as follows:
FilePath
|
%11%\rshx32.dll
|
DLLInstall
|
FALSE
|
DLLRegister
|
TRUE
|
Flags
|
0
|
Phase
|
4500
|
Reboot
|
FALSE
|
Start
|
1
|
Timeout
|
0
|
Type
|
2
|
Leave everything else as is.
The dependencies are two components: the Security Shell Extension component, and the Windows Security Configuration Editor Client Engine component.
Import the new component that you create to your database, include it in your configuration, check the dependencies, and then rebuild your runtime.
Software Installation Group Policy MMC Snap-in
The Software Installation Group Policy MMC snap-in component has a missing dependency. If you add the Software Installation Group Policy MMC snap-in component to a configuration, you must also add the NLS: Time Zones component.
TCP/IP Netstat Command
The netstat -r command does not work properly unless you manually add the Route.exe file to your configuration (found in TCP/IP Utilities component). Netstat has been subsequently componentized into TCP/IP Netstat Command.
Telnet Server
A telnet server on a Standard 2009 runtime fails when users connect to it, with the following error message:
Failure in initializing the telnet session. Shell process may not have been launched.
The Telnet Server component has an undeclared dependency on the Windows Logon component. This error occurs when you are using the MinLogon component.
To resolve this problem, replace the MinLogon component with the Windows Logon component.
Terminal Services
By design, you cannot automatically log the local user of a Standard 2009 runtime back on after a Terminal Service connection has ended.
This is because of security reasons. To work around this behavior:
Add the Automatic Logon component, and then add the local user account information for the user account that you want to log on automatically each time that you restart the computer.
After the Terminal Services session has ended, restart the computer.
The computer should log back on to the terminal server after you restart it because of the Automatic Logon component.
Terminal Services Web Control Extension
The Terminal Services Web Control Extension component requires you to manually add the Terminal Services Web Control Core component.
Some components require the selection of other components that have a visibility as low as 100. To view these additional components, you must lower the visibility in Target Designer to 100, and keep the visibility set to 100 throughout the life of the configuration. This is also true for any other development system that will host these configurations.
Volume Shadow Copy service
The Volume Shadow Copy service does not require the Indexing Service component, even though it expresses a dependency on it. If desired you can disable Indexing Service.
Windows Movie Maker Common problems Movie Maker does not record video properly
If you add the Windows Movie Maker component to a configuration and want to use video recording features, add the DirectX 8 (or newer) Macro component.
You get a "File not found" error message when you try to use the Movie Maker Help
When you try to use the Movie Maker Help, you receive an error message that states that the Help file cannot be found. This behavior occurs because the Help file is located in the MUI\1033 folder instead of the MUI\0409 folder. To resolve this problem, move the Help file to the MUI\0409 folder.
Windows Picture and Fax Viewer
User account pictures in the Users program in Control Panel will not appear unless you add the Windows Picture and Fax Viewer component.
Windows Security Configuration Editor Client Engine
See the "Security Shell Extension" component section.
Windows XP Explorer User Interface
When you add the Windows XP Explorer User Interface component to a configuration, a dependency check may reveal that it contains a dependency on at least one format utility. You can disregard this dependency.
Video resolution problems
In Target Designer, you can preset the desktop display settings for your runtime. To configure the display settings offline:
In Target Designer, locate your particular display adapter component in your configuration, for this example, "NVIDIA GeForce4 MX 440."
Expand the component, and then click the Settings node under it.
The following configurable settings are displayed in the right pane of Target Designer:
Resolution
Refresh Rate
Color Depth
Select the settings you want the runtime to be in. FBA will use these settings to configure the runtime as you want. Rerun the check dependency process, and then build the runtime.
The default settings in the Config UI are general settings; they may not be appropriate for your particular adapter. If your adapter requires an uncommon setting (such as a refresh rate of 47Hz), it may not be offered in the list.
However, you can still force the Config UI to take your uncommon settings. So if your adapter supports a value that is not offered in the list, click the video adapter component name in the Config UI, and then click Advanced. Type the value that your adapter requires.
Note If you return to the Config UI for the display adapter, the unsupported setting will still not appear in the list. In fact, the list will be blank. This is normal. However, do not click that list. Doing so generates a VB script error from Target Designer. This is a known bug.
A common problem is booting into the runtime and seeing that the default resolution settings are not configured as you had set them offline. You may notice near the end of your FBA log (located in the runtime in the Windows\Fba\Fbalog.txt file) entries similar to the following example:
12:43:43 PM - [FBAChangeDisplaySettings] Settings: [640, 480, 16, 60]
12:43:43 PM - [FBAChangeDisplaySettings] Settings not found!
This "settings not found" is a generic warning that FBA was unable to automatically configure the video adapter for the settings specified in the configurable UI of your video adapter. This issue may be caused by any of the following reasons:
You are missing the PNP (User-mode) component in your configuration. The PNP (User-mode) component is required for FBA to configure the video adapter. Also be careful that you did not inadvertently disable the FBA: PnP component or the PNP (Kernel-mode) component. Both of these components have a visibility of 200, so you must reduce your visibility level to see them.
You may have specified a setting that is not supported by the adapter (could be refresh rate, color depth, or resolution). If the driver for your adapter does not accept the setting as being valid, it will fail at this point as well.
In rare cases, a monitor may require its specific component driver to be added to the configuration instead of using the generic Default Monitor component that appears to work with a majority of monitors.
If you created the video driver components yourself, it is possible that there is a missing dependency in your driver package. This condition forces the operating system to use the VGASave driver in place of your driver. You can verify if this is the case by several methods:
If you have the Device Manager component in your configuration, you can check to see if your display adapter is installed correctly or not.
If you have the Display Control Panel component in your configuration, you can click the Advanced button on the Settings tab. This will show you whether the system is using VGASave or using your driver. VGASave simply indicates there was a bigger problem with your component and that the inability to reconfigure the settings is just a symptom of that failure.
If you created the video driver components yourself and you are not sure if the driver was set up correctly in FBA, check your Fbalog file, and browse the entries in the PNP phase near the top quarter of the log. Locate the Ven/Dev ID for your video adapter, and see if there are any errors related to it when FBA-PnP is attempting to set it up. If there are errors, these may indicate a missing dependency in your driver package. There are other tip articles on the Standard 2009 Web site that explain how to troubleshoot issues like this.
|