Microsoft KB Archive/901065

Knowledge Base

Supplemental release notes for Windows Embedded for Point of Service

Article ID: 901065

Article Last Modified on 5/11/2007

---

APPLIES TO

• Microsoft Windows Embedded for Point of Service

---

INTRODUCTION

This document contains supplemental release notes for the original release of Microsoft Windows Embedded for Point of Service (WEPOS) version 1.0.

MORE INFORMATION

Setup-related issues

1. When you set up WEPOS in unattended mode, a random exception is reported. This is in contrast to an error being logged. The exact exception message can vary.

Reproducing environment
This can occur if Setup is running unattended and EncryptedPassword is set to yes, but the password is not encrypted.

Workaround
Set EncryptedPassword to No, or use a password that is encrypted.

2. You have a need to identify which components are optional during Setup.

Reproducing environment
Run WEPOS Setup.

Workaround
To identify which components are optional, inspect the following registry key:

HKLM\Software\Microsoft\WePOSOptionalComponents

If the value of a key is set to 1, the indicated optional component is installed; if it is set to 0, the optional component is not installed.

3. Your image does not boot because the partition number identified in the Boot.ini file is incorrect.

When you are running Setup, the partition number indicated in Boot.ini is generated using partition numbers assigned by the Virtual Disk Service. Partition numbers are reset after boot, and the number inserted into Boot.ini in some cases does not point at the partition number created by Setup. Error messages range between messages about corrupt Ntoskrnl.exe and messages about disk failure, depending on whether the partition that Boot.ini ends up pointing to points to an existing partition or not.

Reproducing environment
Reproduce this issue using the following setup procedure:

1. Boot from the CD.
2. Delete all partitions.
3. Run Setup.
4. Create four partitions, and then delete the second partition.
5. Exit Setup.
6. Set the last partition (partition 3 according to Diskpart) to active.
7. Do not reboot.
8. Run Setup.
9. From the WEPOS installation menu, click Install on Partition 4. (You will notice that drive letters associated with partition 2 are still missing within Setup.)
10. Reboot.

Boot.ini will now reference partition 4, but the system will not boot unless you modify Boot.ini to point at partition 3 since the numbers are shifted.

Workaround
Users should reboot the computer after any Diskpart changes have been made before running Setup.

4. Setup returns an error message after you select the installation drive.

When a USB key drive is connected, you receive the following error message:

There is no system drive

Reproducing environment

1. Attach a USB key drive.
2. Boot into the WEPOS operating system Setup.
3. On the Install Disk Configuration Settings page, select a partition for the operating system.
4. Click Next.
5. The following error message is presented:

   There is no system drive

6. Without the key drive, the dialog box lists the partitions.

Workaround
Before you run Setup, unplug any connected USB storage devices.

5. "Regional and Language Options" cannot add the installed services input language and keyboard. This results in the inability to load additional languages and keyboards other than English.

Reproducing environment

1. During WEPOS Setup, when you reach the Optional Software Component Settings page, click to select the following features in the Language Support subsettings:
   • Additional Font Support
   • Additional Code Page Support
2. In Control Panel, open Regional and Language Options.
3. Click the Languages tab, and then click Details.
4. Under Installed services, click Add.
5. Try to add any English input language with a corresponding keyboard or a US keyboard.
6. Click Apply.

Actual result
You are unable to add an input language and keyboard. You receive the following message:

Windows could not load the (language you selected) - (keyboard you selected) layout

Workaround
In order for Regional and Language Options to work, click to select the Additional Input Device Support optional Setup component.

6. Using a StandardsAndFormats value that is not present in the supported standards and formats list will cause an error during First Boot Agent (FBA).

Failed to load resources from file. Please check your setup

This error will not occur if you use the default StandardsAndFormats value or if you leave this value out in unattended mode.

Workaround
No workaround is available. The following standards and formats are not supported:

• 1082 Maltese
• 1131 Quechua - Bolivia
• 1093 Bengali - India
• 1100 Malayalam - India
• 1153 Maori - New Zealand
• 2155 Quechua - Ecuador
• 5146 Bosnian - Bosnia and Herzegovina
• 1132 Northern Sotho - South Africa
• 3179 Quechua - Peru
• 9275 Sami (Inari) - Finland
• 4155 Sami (Lule) - Norway
• 5179 Sami (Lule) - Sweden
• 4122 Croatian - Bosnia and Herzegovina
• 1074 Tswana - South Africa
• 3131 Sami (Northern) - Finland
• 1106 Welsh - United Kingdom
• 1083 Sami (Northern) - Norway
• 7194 Serbian (Cyrillic) - Bosnia and Herzegovina
• 1076 Xhosa - South Africa
• 1077 Zulu - South Africa
• 2107 Sami (Northern) - Sweden
• 8251 Sami (Skolt) - Finland
• 6170 Serbian (Latin) - Bosnia and Herzegovina
• 6203 Sami (Southern) - Norway
• 7227 Sami (Southern)- Sweden

7. Setup creates a new Boot.ini file on the active partition. The new Boot.ini contains only boot information for the WEPOS system volume.

Reproducing environment
Install WEPOS on a computer that has more than one partition and where one of the other partitions already contains a Windows operating system.

Expected result
Setup should not discard any information in Boot.ini relative to partitions other than the one where WEPOS is being installed.

Actual result
Setup overwrites the existing Boot.ini file without taking into account existing information.

Workaround
Before you run Setup, copy or rename the old Boot.ini. After Setup finishes, merge the two Boot.ini files to ensure that you have the multi-boot capability that you desire.

8. After Setup finishes and early in the reboot sequence before FBA, if the WEPOS operating system encounters a corrupt file, you receive a message that says "Select 'r' at the first screen to start repair."

The repair is not an available option at the first screen.

Reproducing environment

1. Use the CD-ROM with the corrupt file.
2. Boot and set up using the disc. After you reboot, the following message is presented:

   Windows could not start because the following file is missing or corrupt: \system32\drivers\isapnp.sys.
   You can attempt to repair this file by starting Windows Setup using the original Setup CD-ROM.
   Select 'r' at the first screen to start repair.

   This message should be disregarded.

Workaround
The only workaround is to completely reinstall WEPOS.

9. When you create an unattended Setup file, you should not specify a user name using one of the following built-in accounts.

• Administrator
• ASPNET
• Guest
• HelpAssistant
• IUSR_MACHINENAME
• IWAM_MACHINENAME

Currently, WEPOS Setup allows you to do this. However, using a built-in account is not supported.

Workaround
The workaround is actually a best-practice issue. Use one of your own accounts instead of a built-in account.

10. During Setup, you click to select the "Enable file and folder compression" check box, which may require more disk space than you have available during the installation phase.

This is because Setup compresses files after they are all installed, which requires additional disk space during installation.

Reproducing environment

1. Click to select the Enable file and folder compression check box during WEPOS Setup.
2. Let Setup run.

Workaround
Perform installation using a computer with a larger hard disk than you plan to use in the deployed point of service (POS) terminals. After the installation finishes, copy the compressed image to the smaller target disk device.

11. If you have installed a DigiPoS USB Flash drive, the drive may appear as a mass storage device, visible as Disk 0, during the initial setup.

Because of this, your hard disk drive may appear as Disk 1 on the Install Disk Configuration Settings page.

Workaround
Recognize that your hard disk drive in this case may appear as Disk 1, instead of the more common mapping as Disk 0, on the Install Disk Configuration Settings page. In this case, if you want to run Setup on your hard disk drive, specify Disk 1.

12. A Bugcheck may occur in Imkrinst.exe during FBA if you choose "Czech" or "Slovak" in "Standards and formats."

In a specific configuration, there is a crash during FBA in Imkrinst.exe that generates a Dr. Watson report. The error message given is in Chinese. This condition can have the following results:

• It may block a possible path in automated (unattended) Setup.
• Korean IME may not work correctly.

Reproducing environment
Set Standards and formats to Czech or Slovak. This problem also reproduces in Microsoft Windows XP Professional Service Pack 2 (SP2) when you follow these steps:

1. In Control Panel, open Regional and Language Options.
2. Click the Languages tab.
3. Make sure that the Install files for East Asian languages check box is cleared. If the Install files for East Asian languages check box is selected, click to clear the Install files for East Asian languages check box, and then reboot.
4. Click the Regional Options tab.
5. Under Standards and formats, click Czech or Slovak.
6. Click Apply.
7. Click the Languages tab.
8. Click to select the Install files for East Asian languages check box.
9. Click Apply.
10. Insert the Windows XP Professional installation CD if you are asked.

Workaround

1. After the installation finishes, change Standards and formats to something other than Czech or Slovak.
2. Run C:\Windows\ime\imkr6_1\Imkrinst.exe.
3. Change Standards and formats back to Czech or Slovak.

13. SetupLauncher returns an ERRORLEVEL of 1 when Setup finishes.

Reproducing environment

1. Run SetupLauncher.exe in a scenario where Setup finishes without an error.
2. Check the current error level.

Workaround
This is the normal behavior of SetupLauncher. It returns a nonzero value that does not indicate an error.

14. You encounter a font exception during Setup.exe on a Shuttle XPC computer.

Reproducing environment

1. Copy the WEPOS Setup CD to a read/write share on a Shuttle XPC computer.
2. Using the share that you just created, run Setup.

Workaround
Run WEPOS Setup only from the CD or from a read-only share. If the directory is not read-only, the framework creates a font cache file that contains paths to fonts with a hard-coded CD drive letter. If another Setup runs from the same share and its CD drive letter is different (because of a different set of partitions on the hard drive), the exception is thrown.

15. You are unable to boot the system after installation.

Reproducing environment

1. From a command prompt, run Diskpart. Enter the following Diskpart command:

   create partition primary size=1000

2. Format the new partition NTFS.
3. Reboot into Setup.
4. Run Setup, and create a second partition with the rest of the disk.
5. On the Install Disk Configuration Settings page, select Partition 2, and then click Next to proceed to the Format Partition page.
6. Click Perform a quick format.
7. Finish the installation by using the default settings.

When the computer reboots, it cannot find NTLDR, and so it does not run FBA.

Workaround
After you complete disk partitioning but before you run Setup, ensure that the partition that is to serve as the system partition is marked as Active, using tools such as Disk Management (Diskmgmt.msc). You also can mark the partition as Active after Setup has finished.

16. Unattended Setup allows Account elements with duplicate Username attributes.

Even though unattended Setup allows this, it is not supported. You cannot use this technique to add a user to multiple groups.

Workaround
Identical account Username elements are not supported. If you wish to add a user to more than one group, a different mechanism is required, such as creating a RunOnce command to add the user to an additional group.

17. A potentially confusing exception is thrown during Setup as a result of misconfiguring your computer with a Static IP Address that does not have the same network ID as the Default Gateway, as specified in the SubnetMask.

Fatal Error occurred - Source: mscorlib \r\n
Message: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. \r\n
Stack Trace: at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)

Reproducing environment
The following elements in the answer file are an example of an incorrectly configured network.

<Networking>
<IPAddress DynamicIPAddress="No" StaticIPAddress="100.100.100.201" SubnetMask="255.255.255.0" DefaultGateway="100.100.101.202" /> 
<DNSServer DNSAuto="No" PreferredDNSServer="100.100.100.200" AlternateDNSServer="100.100.100.200" /> 
</Networking>

Workaround
Ensure that you properly configure the Static IP Address, the Default Gateway, and the subnet mask.

18. During Setup, DefaultInputLanguage values are not being set correctly in the WEPOS operating system.

If you choose a DefaultInputLanguage (DIL) of Arabic (Egypt), the DIL value in Control Panel will be set to the default DIL for the selected UserInterface value. For German, it will be "German (Germany)." For English, it will be "English (United States)." This will also happen for a number of other DILs. The following list of DILs will produce the same behavior, setting the Keyboard Preload registry value to "00000409":

• Afrikaans
• Arabic (Bahrain)
• Arabic (Egypt)
• Arabic (Iraq)
• Arabic (Jordan)
• Arabic (Kuwait)
• Arabic (Lebanon)
• Arabic (Oman)
• Arabic (Qatar)
• Arabic (Saudi Arabia)
• Arabic (Syria)
• Arabic (U.A.E.)
• Arabic (Yemen)
• Chinese - Macau S.A.R.
• Chinese - Singapore
• Divehi
• Farsi
• Greek
• Gujarati
• Hebrew
• Hindi
• Indonesian
• Kannada
• Konkani
• Malay (Brunei Darussalam)
• Malay (Malaysia)
• Marathi
• Northern Sotho
• Punjabi
• Sanskrit
• Swahili
• Syriac
• Tamil
• Telugu
• Thai
• Tswana
• Uzbek (Latin)
• Vietnamese
• Xhosa
• Zulu

Reproducing environment

1. Run Setup.
2. Choose any UserInterface language (for example, German).
3. Choose a DefaultInputLanguage of Arabic (Egypt).
4. Boot into the installed operating system.
5. In Control Panel, open Regional and Language Options, click the Languages tab, and then click Details. Under Default input language, you will see "German (Germany)."

Workaround
After Setup finishes, boot the WEPOS operating system. Then, correct the DefaultInputLanguage using Regional and Language Options in Control Panel.

19. Unattended Setup fails when you use a non-English StandardsAndFormats value.

If you select a non-English StandardsAndFormats value other than the same user interface (UI) that you have selected (e.g., you choose German as the UI but French for StandardsAndFormats), unattended Setup will fail with an error. However, attended UI Setup will proceed normally.

Reproducing environment
Create and run an unattended file with an English UserInterface and a French (France) StandardsAndFormats.

Workaround
Choose one of these two possible workarounds:

• Run Setup using attended mode instead of unattended mode.
• Run Setup using unattended mode, and then change the StandardsAndFormats value using Regional and Language Options in Control Panel.

20. Certain computers contain OEM hidden partitions that cannot be deleted using the Setup user interface.

An example of a computer with such a partition is a Dell 8400. Setup does not report an error or warning when this is encountered.

Reproducing environment
Run unattended Setup on a Dell XPS that has an existing OEM installation.

Expected result
The OEM partition is deleted.

Actual result
Setup fails with an uninformative error.

Workaround
Before running Setup, manually delete the hidden partition using partition management software such as the Diskpart tool.

21. Specifying a small PageFile size may cause an exception during Setup.

For example, this can occur if you specify a PageFile with InitialSize=2 and MaximumSize=2 (MB).

Reproducing environment
Configure a test computer with 512 MB of system memory. Run WEPOS Setup, and select all optional components. Specify a PageFile with InitialSize=2 and MaximumSize=2.

Actual result
FBA pops up a message box with the following error:

CallEntryPointThread
Exception: C:\Windows\system32\iasrecst

Workaround
Configure the system page file size to be at least 32 MB. This will prevent running out of PageFile resource. The recommended minimum page file size is 1.5 times the amount of system memory, and the recommended maximum is 2 times the amount of system memory.

22. You observe unexpected error messages when your unattended file is being processed.

If you specify an invalid or nonexisting path to your unattended file, you will observe the following nonintuitive error messages:

[3/21/2005 1:23:06 PM 3808 Error ImportThread] Fatal Error occurred - Source: mscorlib \r\nMessage: The network path was not found.


[3/21/2005 1:23:06 PM 3808 Error Logger] Attempt to persist log file %TARGETDRIVE%\Windows\WINePOSSetup.log failed. Error Message: Target drive letter not known.


[3/21/2005 1:23:06 PM 3808 Error Wizard] Attempt to persist log failed.

Workaround
When you see these error messages, review and correct the path used to point to your unattended file.

23. You may observe an error when Setup attempts to create a partition during unattended Setup.

This issue may occur because there is a potential timing issue between the deletion of the disk contents and the creation of a new partition.

Reproducing environment
A typical symptomatic error message is the following:

Result: Error Dialog: 1204 Error ActionThread] Fatal Error occurred - Source: Microsoft.Embedded.Setup.CommonScreens \r\nMessage: Failed to create partition. \r\nStack Trace: at Microsoft.Windows.Embedded.Setup.VdsHelper.CreatePartition(IPartitionInfo freeSpace, UInt64 size)

Workaround
The workaround is to run unattended Setup again.

24. During Setup, you may be asked to insert one of the following CDs: Windows Server 2003, Standard Edition CD-ROM or Windows XP.

When you see either message, it should be interpreted as a request that you insert the WEPOS CD.

Workaround
The workaround is to install the WEPOS CD instead. This issue occurs because of incorrect text in the following files:

• Netfxocm.inf
• Layout.inf

25. During Setup, Event Viewer contains the following message: "The description for Event ID (1010) in Source (Windows Product Activation) cannot be found."

The full text of the message is the following:

The description for Event ID (1010) in Source (Windows Product Activation) cannot be found. The local computer may not have the necessary registry information or message DLL file to display messages from a remote computer. You may be able to use the /AUXSOURCE=flag to retrieve this description; see Help and Support for details. The following information is part of the event: The event log file is corrupt.

Workaround
This message is benign and can be ignored.

26. During unattended Setup, badly formed XML in your configuration file will cause Management.Explorer to log an error and ignore the global configuration file.

This occurs because an illegal XML schema in your configuration file causes a PosLibrary exception.

Workaround
You can use this information to help debug your XML configuration file. There are currently no means of automatically determining whether the XML is well formed and whether it contains a valid schema.

27. During Setup, you observe this Message Box error: "Exception: Index was out of range."

The full text of the message is the following:

Windows Embedded for Point of Service Exception: Index was out of range. Must be non-negative and less than the size of collection. Parameter name: index.

Workaround
This error occurs when the operating system cannot find fixed Disk 0, which is required in order to access the master boot record. This issue is computer BIOS dependent. The workaround is to unplug the USB drive or to change the BIOS settings to accommodate hardware changes.

28. A missing PID causes unexpected error messages during unattended Setup.

You may observe the following error messages during unattended Setup:

[4/8/2005 9:04:36 AM 2624 Error ActionThread] Fatal Error occurred - Source: mscorlib \r\nMessage: Index was out of range. Must be non-negative and less than the size of the collection.


[4/8/2005 9:04:36 AM 2624 Error Logger] Attempt to persist log file %TARGETDRIVE%\Windows\WINePOSSetup.log failed. Error Message: Target drive letter not known.


[4/8/2005 9:04:36 AM 2624 Error Wizard] Attempt to persist log failed.

Workaround
Your unattended file contains a missing PID. You must supply a complete and valid PID.

29. You are unable to run WEPOS Setup on a partition that had been a dynamic disk at some time in the past.

You observe this message:

There is no active partition on the system drive

Also, you cannot delete the partition. The error message is the following:

Operation failed

Workaround
Before running Setup, you must run Diskpart from a command prompt in order to clean the disk and create a new, active partition.

30. WEPOS does not support extending the system partition size after the system image has been built and deployed.

Workaround
WEPOS does not currently support post-build system partition extension.

31. The Optional Software Component Settings page is not automatically updated based on changes you have made to the target drive letter.

Reproducing environment

1. Run Setup.
2. Select drive C as your target drive.
3. Follow the steps in the Setup Wizard until you reach the Optional Software Component Settings page.
4. The Optional Software Component Settings page refers to the target drive as C.
5. Go back to the Format Partition page, and change the target drive to drive D.
6. Return to the Optional Software Component Settings page. Drive C is still indicated as the target drive.

Expected results
The change should have been reflected on the Optional Software Component Settings page.

Workaround
This does not affect functionality. The changes you made to the target drive will persist.

32. When you use Fbreseal.exe, the WEPOS computer settings, network settings, and user settings are not completely prepared, and mounted devices are not removed.

Reproducing environment
Run Fbreseal.exe on WEPOS. Then, reboot the system to allow System Cloning to finish.

Workaround
Set the following registry keys before you run Fbreseal.exe:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\WindowsEmbedded\FBReseal]

"GenerateComputerName"=dword:00000001
"RemoveNetworkSettings"=dword:00000001
"RemoveUserSettings"=dword:00000001
"RemoveMountedDevices"=dword:00000001

WEPOS operating system runtime-related issues

1. You are unable to make changes in the "Driver Signing Options" found on the "Hardware" tab of "System Properties" in Control Panel.

As a result, it is possible to install an unsigned driver.

Reproducing environment
Perform the following steps:

1. In Control Panel, open System.
2. Click the Hardware tab.
3. Click Driver Signing.
4. Click to select one action option, and then click OK.
5. Click Driver Signing again to see the selection that you made in step 4.
6. Verify whether the selection is saved correctly.

Workaround
No workaround is available. The only implication is that an unsigned driver may be installed. However, the user is first warned that an unsigned driver is being installed.

2. The "Time to display recovery options when needed" check box is cleared in the "Startup and Recovery" dialog box in Control Panel.

As a consequence, if Startup and Recovery is invoked, there is no option to choose from recovery options.

Reproducing environment

1. In Control Panel, open System.
2. Click the Advanced tab.
3. Under Startup and Recovery, click Settings.
4. In the Startup and Recovery dialog box, the Time to display recovery options when needed check box is cleared.

Workaround
This feature was intentionally cleared because local management tools are not installed to support the recovery options.

3. The Remote Assistance feature is unavailable.

Reproducing environment

1. To open Computer Management, right-click My Computer, and then click Manage.
2. Expand Local Users and Groups, and then click Groups. All groups should be displayed in the right pane.

Expected result
Offer Remote Assistance Helpers is displayed when Local Management is installed.

Actual result
Offer Remote Assistance Helpers is missing.

Workaround
Remote Assistance is not supported in WEPOS version 1.0.

4. You are unable to access "Performance Logs and Alerts" remotely.

Reproducing environment

1. On the Optional Software Component Settings page, click to select the Local Management Support check box. Then, proceed to build WEPOS.
2. Click Start, right-click My Computer, and then click Manage.
3. Right-click Computer Management (Local).
4. Click Connect to another computer.
5. Connect to another WEPOS computer on the network.
6. Expand System Tools, and then expand Performance Logs and Alerts.
7. Right-click Trace Logs, and then click New Log Settings.
8. Type a name, and then click OK.

Expected result
A properties dialog box opens that has the same name as the log file name that you chose.

Actual result
You receive the following error message:

Unable to access registered trace providers on <computer name>. The <file name> property will not be opened. The RPC server is unavailable.

Workaround
Remote management of Performance Logs and Alerts is not supported in WEPOS version 1.0.

5. Some Windows Management Instrumentation (WMI) performance counters are missing.

WMI performance counters do not exist for the following categories:

• Memory
• Processor
• Objects

Reproducing environment
Use WMI APIs to access performance counters. The aforementioned categories will not be listed.

Workaround
A system PageFile is required in order to have access to these performance counters. Use the PageFile option in unattended Setup in order to enable these features.

6. Using Windows Explorer, attempting to search for files in subfolders from C:\ does not work.

Reproducing environment
Use Windows Explorer to search for files starting in the root of the C drive.

Workaround
There is currently no workaround for WEPOS version 1.0.

7. The Remote Desktop shortcut is missing.

When you run Remote Desktop in Windows XP Professional, a shortcut is automatically created in the directory named My Documents. Under WEPOS, no such shortcut is created.

Workaround
There is no workaround. This has no adverse behavior on the functionality of Remote Desktop.

8. The system may crash after you change the language to Chinese if you do not have "Additional Font Support" included during Setup.

Reproducing environment

1. Install WEPOS with no optional components.
2. In Control Panel, open Regional and Language Options, and then click the Regional Options tab.
3. Under Standards and formats, click Chinese (PRC).
4. In Regional and Language Options, click the Advanced tab.
5. Under Language for non-Unicode programs, click Chinese (PRC).
6. Click Apply, and then restart the computer.

Actual result
The system crashes.

Workaround
You must click to select the Additional Font Support check box during Setup.

Note This problem may also occur in Windows XP Professional if the East Asian fonts are not installed.

9. You have the option to install full Windows XP Professional MUI packs on top of WEPOS. This may be useful in order to obtain the same MUI functionality that is configured in Windows XP Professional.

Workaround
Here are the steps you follow to install Windows XP Professional MUI packs:

1. Uninstall any preexisting WEPOS-installed MUI pack by clearing the language you want to uninstall. Let MUI Setup finish in order to complete the uninstallation.
2. Run MUISetup.exe from the MUI pack CD.
3. Read the license agreement, and click Accept if you want to proceed.
4. Choose the languages you want to install and the other options the installer provides.
5. Start the installation.
6. The first error you get is the following:

   This application has failed to start because OCManage.dll was not found. Re-installing the application may fix this problem

   Click OK to continue.
7. The second error you get is the following:

   Error creating process <C:\Windows\PCHealth\HelpCTR\Binaries\HelpSVC /MUI_install LCID_Value C:\Windows\PCHealth\MUI\LCID_Value\pchdt_w3.cab>. Reason: The system cannot find the file specified.

   Click OK to continue.
8. The third error you get is the following:

   Setup was unable to install Multilingual Files for the HSS Component.

   Click OK to continue.
9. Next, the following message appears:

   Setup was canceled or encountered unexpected errors, do you want to continue current MUI installation?

   Click YES.
10. After this, Setup continues.
11. You will see an indication that Multilingual File Installation completed successfully. Click OK, and the MUI pack is installed successfully.

Note In some cases, the language may not install correctly the first time. To validate the installation, inspect the following folder:

%SystemRoot%\ mui\fallback\<LangID>

If the installation was successful, the folder contains approximately 1500 files. If the installation did not succeed, the folder contains approximately 50 files. In case of a failed installation, run MUISetup.exe again to uninstall the language. Then, reinstall the language, and the installation will succeed.

10. A Microsoft .NET Framework 1.1 Service Pack 1 security update does not appear as being installed.

When you use Windows Update, .NET Framework 1.1 Service Pack 1 Security Update (KB886903) is reported as not being installed and always appears in the high-priority updates list, even after the update has been successfully installed.

Reproducing environment

1. Install WEPOS with only Windows Media Player 9.0 selected.
2. In Control Panel, click Windows Update under See Also, and then click Custom.
3. Choose and install all high-priority updates.

Actual result
Security Update for Microsoft .NET Framework 1.1 Service Pack 1 (KB886903) appears in the high-priority updates list, even though it has been successfully installed.

Workaround
Until Windows Update is corrected, the workaround is to manually confirm that this update has been applied. One method is to use Regedit to inspect the list of installed updates:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Hotfix

11. You experience problems using the Add Printer Wizard.

When you add a printer using the Add Printer Wizard, the wizard reports the following message in a dialog box:

Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server. For more information, click Help.

Reproducing environment

1. Install WEPOS with all components installed.
2. Click Start, and then click Printers and Faxes.
3. Under Printer Tasks, click Add a printer.
4. In the Add Printer Wizard, click Next. Click A network printer, or a printer attached to another computer, and then click Next.
5. Click Connect to a printer on the Internet or on a home or office network, type the shared printer name, and then click Next.

Actual result
The aforementioned dialog box appears.

Workaround
Required registry keys are missing. Add the following registry keys to the registry:

[HKEY_CLASSES_ROOT\CLSID\{77597368-7b15-11d0-a0c2-080036af3f03}] @="Web Printer Shell Extension"

[HKEY_CLASSES_ROOT\CLSID\{77597368-7b15-11d0-a0c2-080036af3f03}\InProcServer32] @="printui.dll" "ThreadingModel"="Apartment

12. The .NET Framework 1.1 does not appear in "Add or Remove Programs" in Control Panel.

Reproducing environment
Install the .NET Framework 1.1.

Expected result
Microsoft .NET Framework 1.1 appears in Add or Remove Programs.

Actual result
After installation, Microsoft .NET Framework 1.1 does not appear in Add or Remove Programs.

Workaround
You can still update the .NET Framework 1.1 by directly running the desired updates. As of this writing, WEPOS supports the .NET Framework 1.1 and the .NET Framework 1.1 Service Pack 1.

13. The NTRESTORE tool is not supported in WEPOS.

Reproducing environment
At a command prompt, type NTRESTORE. The following message appears:

’NTRESTORE’ is not recognized as an internal or external command, operable program or batch file

Workaround
The NTRESTORE feature is not supported in WEPOS.

14. Universal Plug and Play is enabled by default.

The Universal Plug and Play (UPNP) feature is enabled by default in your WEPOS image. This note identifies how you can disable or enable the UPNP feature.

Workaround
To disable the UPNP feature, unregister it by typing the following command at a command prompt:

regsvr32 /u upnpui.dll

To reregister it, type the following command at a command prompt:

regsvr32 upnpui.dll

These commands may also be invoked automatically through the RunOnce branch of the registry.

15. Event Viewer is not reporting message text associated with Service Control Manager.

Reproducing environment
Inspect the event logs. Confirm that the message text is not available.

Workaround
Add the following registry keys to correct this Event Viewer problem:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\Service Control Manager] "EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\ 00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\ 5c,00,6e,00,65,00,74,00,65,00,76,00,65,00,6e,00,74,00,2e,00,64,00,6c,00,6c,\ 00,00,00 "ParameterMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,\ 6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\ 00,5c,00,6b,00,65,00,72,00,6e,00,65,00,6c,00,2e,00,64,00,6c,00,6c,00,00,00 "TypesSupported"=dword:00000007

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\HTTP] "EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\ 00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\ 5c,00,78,00,70,00,73,00,70,00,32,00,72,00,65,00,73,00,2e,00,64,00,6c,00,6c,\ 00,00,00 "TypesSupported"=dword:00000007

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\USER32] "EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\ 00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\ 5c,00,75,00,73,00,65,00,72,00,33,00,32,00,2e,00,64,00,6c,00,6c,00,00,00 "TypesSupported"=dword:00000007

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\EventLog] "EventMessageFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\ 00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\ 5c,00,6e,00,65,00,74,00,65,00,76,00,65,00,6e,00,74,00,2e,00,64,00,6c,00,6c,\ 00,00,00 "TypesSupported"=dword:00000007

16. A workaround is available to enable WEPOS to open certain documents, such as Word documents (.doc), within WEPOS.

WEPOS does not include all the graphics filters required for full WordPad.exe functionality.

Workaround
You can open these documents in Windows XP Professional, and then save them as Rich Text Format (RTF) files, which WordPad can view without the need for the additional text converters.

17. If WEPOS is configured for the Korean language, "Automatic Updates" in Control Panel may appear in Korean.

Reproducing environment

1. Install WEPOS in Korean.
2. Add all functions.
3. Boot WEPOS.
4. Click Start.
5. Click Control Panel.
6. Double-click Automatic Updates.
7. Click Automatic.
8. Click OK.
9. Double-click System.
10. Close System.
11. Double-click Automatic Updates.

Expected result
All Control Panel items should be displayed in English.

Actual result
Occasionally, Automatic Updates appears in Korean.

Workaround
This is an intermittent issue that does not affect functionality. There is no workaround for this release.

POS for .NET issues

1. In BasicClasses, a service object (SO) writer may set the SO state to Closed and then discover that the SO does not clean up event queues.

This later results in exceptions being thrown when the SO tries to process events in its queue.

Reproducing environment
A service object (SO) writer deriving from the Basic Class has the ability to change the SO state to Closed.

Workaround
There is no workaround, as this is not a supported use of the State property by the SO. Please note that the normal resource reclamation and related cleanup will not occur automatically in this scenario. If the SO writer must modify its own state by setting it to Closed, the following must be true:

• It must not try to process any events in its own queue.
• It must perform its own cleanup.

2. Legacy COM-based OLE for Point Of Sales (OPOS) logic devices may enumerate incorrectly if they are configured both in the registry and in Config.xml.

Reproducing environment
To reproduce this problem, configure a COM-based OPOS device both in the registry and in Config.xml.

Workaround
To prevent this problem, do not configure both the registry and Config.xml for legacy service objects/control objects. Delete the configuration information (including logical device name) from either Config.xml or the registry, but not both.

3. The devices that support legacy interoperability in the CCL are identified.

Workaround
The devices supported for legacy interoperability are the same ones that the base classes were written for. Here is the list:

• cash drawer
• check scanner
• line display
• MSR
• PinPad
• POS Keyboard
• receipt printer
• scanner

WEPOS version 1.0 only provides interoperability for the same classes for which we provide base classes.

4. A possible CCL log file naming contention issue may prevent log files from being created.

Two log files are created when logging is enabled: one for the assembly loading and another for the POS explorer.

The naming scheme for the log files is based on the current date and time. For example, consider a CCL(2005-03-16 13-19-34Z).txt file created at 1:19.34 and a CCL(2005-03-16 13-19-35Z).txt file created at 1:19.35. Note that the file creation time is separated by 1/100 sec. Sometimes both log files are created with the same file name: CCL(2005-03-16 13-19-34Z).txt. The result is that the logging for the assembly loading sequence is not created, and an exception is posted to Event Viewer. The probability of failure increases as the speed of the processor increases.

Reproducing environment

1. Enable logging.
2. Launch the AsynchronousMode.exe test application.
3. Close the test application.
   

Note You may need to repeat these steps many times to reproduce the problem.

1. Open Event Viewer, and view the Application log. To open Event Viewer, click Start, click Run, type Eventvwr.exe, and then click OK. The event log will contain an exception event that the log file is already open.

Workaround
Logging is typically used only when the developer is debugging an SO or an application. The workaround is to disable the logging feature.

5. The CCL log file may appear in two different places.

CCL writes its log file according to a path specified in the registry entries. The WMIProvider process, which uses CCL, writes the log to C:\Windows\Temp.

Workaround
Inspect both locations. When you try to find the CCL log, the location of the log file may be nonintuitive. This is because the POS Device Manager Command Line Tool (POSDM) or other WMIProvider-based applications may have been used, which may change the environment path (%TEMP%) used to specify the location of the log. The value of %TEMP% varies depending on the account.

6. An exception may be thrown while the WEPOS operating system attempts to use service objects that are not compliant with OPOS 1.3 or later.

Workaround
There is no workaround. An SO must be compliant with OPOS 1.8 or greater. For SOs that are based on pre-OPOS 1.5, the user should be aware there may be inconsistencies or breaking API differences. The user should contact the SO provider for that device to request an SO based on the current version of OPOS (preferably OPOS 1.7 or later).

7. In POSDM, configuring a service object device fails, and an error message reports that a duplicate exists.

If a configured service object within POSDM is deleted without first being unconfigured, the corresponding configuration XML file will contain stale information.

If, at some point in the future, a new service object of the same type is then configured, it may clash with the stale entry in the configuration XML file and produce an error message indicating that a duplicate exists.

Furthermore, the duplicate does not show up in the device list because its service object has been deleted.

Workaround
There is currently no approved workaround. You can consider editing the configuration XML file in order to remove the stale service object information, but this technique is not supported.

REFERENCES

For more information about Windows Embedded for Point of Service, visit the following Microsoft Web site:

http://www.microsoft.com/windows/embedded/eval/wepos/default.mspx

Keywords: kbtshoot kbhowto kbqfe kbinfo KB901065

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.