January 2010 Optional Updates are now available on the ECE site for POSReady 2009 and WEPOS. Included are the following:
-
GB18030 is a Chinese character encoding standard. Products sold in China must conform to this standard. The GB18030 Support package contains a font, system libraries, and an applet for installation on XP based systems, with the optional East Asian Language support installed, to meet these conformance requirements.
-
A File Based Write Filter update that addresses the following issues:
-
Resolves issues caused by the FbwfProcessWriteThroughList path buffer not being cleared. This issue may present symptoms including the following:
-
In the current session, FBWFMGR /display may not return accurate write through lists reflecting the fbwfmgr /addexclusion configuration. A correct write through list may not be returned until the following session.
-
A newly created file, even though listed in the exclusion list, may not persist after reboot, in particular files named tmp.
-
You may be able to rename a file to the same file name as a file listed in the exclusion list, in particular files named tmp. Expected behavior would return an error that the file cannot be renamed and the request is not supported.
-
Resolves a potential memory leak caused by the FBWF's failure to call the FreeCallback function, required to allow memory filters above FBWF to free their per-stream context.
-
Resolves a potential file deadlock, resulting from a FBWF incompatibility with a WMI API.
-
Microsoft YaHei Regular and Bold Version 5.00 for Windows XP to improve rendering of Simplified Chinese text in Windows Presentation Foundation.
If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
Thanks,
- Lynda
Previously the ECE team announced upcoming maintenance to the ECE site.
This date has now changed- it will now occur on Friday, February 5, 2010 at 5:00p.m. Pacific Standard Time (PST) and will last until Monday, February 8, 2010 at 8:00 a.m (PST).
The ECE site will not be accessible during this timeframe and the ECE team apologize for any inconvenience this may cause.
- Lynda
A number of new updates are now available on the ECE for Windows® Embedded Point of Service and\or Windows Embedded POSReady 2009.
These include:
If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
Thanks,
- Lynda
Technorati Tags:
WEPOS,
POSReady
You can help shape the next generation of Windows Embedded Business’s POSReady product. The POSReady team would like your feedback about how we improve and build the next version of POSReady that exceeds our customer’s needs. Click here to get started:
<http://support.microsoft.com/common/survey.aspx?scid=sw;en;1688&sd=msft&altStyle=narrow&renderOption=OverrideDefault
Microsoft is committed to protecting your privacy. This survey does not request or collect any personal information.
You should be able to complete this survey within 15-20 minutes or less.
We appreciate your willingness to participate and value your feedback. This process will help us meet and refine your expectations and improve our services.
If you have any questions, please contact the POSReady team at posready@microsoft.com
A problem was discovered that causes the “Add Additional Drivers” page to not install a specific set of RAID drivers. Through some investigation we determined that the logic behind this wizard screen wasn’t copying all the necessary files needed to properly install the RAID drivers. This caused the Setup to fail.
Luckily we were able to help using a Setup feature used to install 3rd party drivers. Here’s how it worked.
InfImporter
This little tool is used by both WEPOS and POSReady 2009 to convert a driver INF file to XML, a format readable by Setup. To create this XML:
1. Download and install InfImporter at: http://www.microsoft.com/downloads/details.aspx?familyid=3BE48D23-BA90-4D5A-9AB0-93D9311ED520&displaylang=en. This can be run at any computer, as long as it has .NET 1.1 or greater installed. A floppy drive will also come in handy, external USB is okay.
2. Insert the RAID/SATA driver’s floppy disk in the drive. If you don’t have a driver disk, look to the manufacturer’s download page for the download matching the hardware.
3. From the command prompt (As Administrator is not necessary) do these commands:
a. Go to the floppy drive and change to the directory where the driver’s INF files are. These are probably in the root, but could be in a sub directory. (A: )
b. Run the InfImporter (C:\Program Files\WEPOS\InfImporter\InfImporter.exe raiddriver.inf raiddriver.xml). Substitute names to match the driver’s files.
c. Check to see if the XML file was created.
Setup
With the driver floppy and XML made, Setup is ready to try installation one more time.
1. The target system must have a floppy drive installed, so install a temporary floppy or plug in a USB floppy drive before booting. Also, be sure the POSReady 2009 DVD is inserted in the DVD drive.
2. When the system boots and shows the message to “Press F6 to install SCSI/RAID drivers”, do this and install them through the menu that appears.
3. Setup should continue to boot, but before the Wizard loads, a small popup window should appear that says “Press any key for the Command Prompt”. Press the Any key right away because this message won’t be there long.
4. From the command prompt that appears enter the command:
a. Setup /devicefile:a:\raiddriver.xml
Typing “Setup /?” will reveal more options. The most common are /unattended and /guionly, used to automate installs through XML data files.
5. Run Setup normally, except on the Add Additional Drivers page, use the default option to say there are no additional drivers required. The next page should show the RAID drive because of the drivers loaded in step 2 above.
Installation
Setup should run through formatting the RAID drive, coping files, and the most important phase, Plug-n-Play.
Optionally, installing from USB thumb drives is also possible, just not through the usual method. Creating the USB Setup drive is the same, however pressing F6 will still be necessary. Watch out, the F6 message will only be there for less than a second so be prepared to hit that key. Same as above, you’ll need to use the command line instead of the wizard to install the drivers.
We would like to hear about your experiences installing POSReady. Regardless this helps or you encounter problems, feel free to send us your comments below.
- Brendan
Just wanted to let folks who access WEPOS and POSReady 2009 updates and information from the Mobile and Embedded Communications Extranet, better known as the ECE, that we have a scheduled maintenance coming up and the site may be temporarily unavailable during the timeframe.
Currently we are on track for the maintenance to begin Friday, January 8, 2010 at 5:00 p.m. Pacific Standard Time (PST) and it supposed to last until Monday, January 11, 2010 at 8:00 a.m PST. If there are any changes to this date they will be featured on the ECE homepage.
We apologize for any inconvenience this may cause.
Thanks,
- Patrick
Technorati Tags:
WEPOS,
POSReady
I'd like to send good wishes from the whole team to all POSReady and WEPOS customers, partners and MVPs for a wonderful holiday season, and a successful 2010! We thank you for your support in 2009. Your willingness to give feedback, as well as your continued participation in community forums and newsgroups, chat sessions, face-to-face or virtual meetings are greatly appreciated by our team. We hope we can continue to partner with you to bring you prosperity in the new year.
FYI-The Redmond offices of Microsoft will be closed tomorrow and Friday (PST) for the Christmas weekend, so responses to mail and forum posts may be delayed.
- Lynda
The December 2009 Security Updates - Product Download is now available for Original Equipment Manufacturers (OEMs) on the ECE for Windows Embedded POSReady 2009 and Windows Embedded for Point of Service. These updates are also individually available directly from the Microsoft Download center as well as Windows Update, however end-customers should refer to their OEM servicing agreement prior to obtaining these updates from any source other than directly from their OEM to ensure uninterrupted support.
The December Security updates include:
- 973904 Vulnerabilities in WordPad and Office Text Converters Could Allow Remote Code Execution
- 976098 Install this update to resolve issues caused by revised daylight saving time and time zone laws in several countries
- 976092 Install this update to resolve a possible data loss issue involving controllers that support ADMA
- 973688 Install this update to prevent applications from sending too many HTTP requests while a well-known Document Type Definition (DTD) is included
- 969084 The Remote Desktop Connection 7.0 client update enables you to use the new Remote Desktop Services features
- 973917 Install this update to help strengthen authentication credentials in specific scenarios
- 951748 Vulnerability in DNS Could Allow Spoofing
- 972270 Vulnerability in the Embedded OpenType Font Engine Could Allow Remote Code Execution
- 976138 An issue has been identified that could allow an authenticated remote attacker to compromise your system and gain control over it
- 973686 Install this update to prevent applications from sending too many HTTP requests while a well-known Document Type Definition (DTD) is included
- 976470 Install this update to resolve an issue in which the "Date and Time" window of Control Panel will incorrectly display an error message
- 973685 Install this update to prevent applications from sending too many HTTP requests while a well-known Document Type Definition (DTD) is included
- 974392 Vulnerability in Local Security Subsystem Authority Service Could Allow Denial of Service
- 970430 Install this update to help strengthen authentication credentials in specific scenarios
- 973687 Install this update to prevent applications from sending too many HTTP requests while a well-known Document Type Definition (DTD) is included
- 976325 Cumulative Security Update for Internet Explorer
- 974318 Vulnerability on Internet Authentication Service Could Allow Remote Code Execution
- 972187 Vulnerabilities in Windows Media Components Could Allow Remote Code Execution
- 971737 Install this update to help strengthen authentication credentials in specific scenarios
- 971726 Vulnerabilities in Active Directory Federation Services Could Allow Remote Code Execution
- 955759 An issue has been identified that could allow an authenticated remote attacker to compromise your system and gain control over it
If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
- Lynda
Technorati Tags: POS
The Windows XP Support Tools, previously available on the ECE for OEM customers for Windows XP Embedded, are now available for Windows Embedded POSReady 2009 and Windows Embedded Point of Service as well.
These Support Tools are intended for use by Microsoft support personnel and experienced users to assist in diagnosing and resolving problems with their embedded systems. They include things like netdom.exe, filever.exe, extract.exe, tracelog.exe etc.
OEMs can download this .img file from the ECE site. If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
Thanks,
- Lynda
When installing .NET 3.0 or .NET 3.0 SP1 from the Download Center onto a Windows Embedded Point of Service 1.1 SP3 system setup fails with the following errors:
SETUP.EXE
Microsoft .NET Framework 3.0 has encountered a problem during setup. Setup did not complete correctly
MICROSOFT .NET FRAMEWORK 3.0 SETUP
An error occurred during setup. Installed files have been removed from your computer. For known issues and troubleshooting information, see the online Readme. For error information, see Error Log.
ERROR LOG (dd_dotnetfx3error.txt)
[Date, Time] WIC Installer: [2] Setup Failed on component WIC Installer
[Date, Time] WapUI: [2] DepCheck indicates WIC Installer is not installed.
[Date, Time] WAPUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
ERROR LOG (dd_WIC.txt)
0.141: 2009/11/03 12:42:32.068 (local)
0.141: c:\72b6b5c6e15e2d3f28e7ae\update\update.exe (version 6.3.4.0)
0.141: Hotfix started with following command line: /quiet /norestart /log:C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dd_WIC.txt
0.151: In Function GetBuildType, line 1170, RegOpenKeyEx failed with error 0x2
0.181: C:\Windows\system32\WindowsCodecs.dll is Not Present
0.181: First Condition in Test.WindowsCodecsVer.Section Succeeded
0.181: Condition succeeded for section Test.WindowsCodecsVer.Section in Line 1 of PreRequisite
0.181: C:\Windows\system32\WindowsCodecsExt.dll is Not Present
0.181: First Condition in Test.WindowsCodecsExtVer.Section Succeeded
0.181: Condition succeeded for section Test.WindowsCodecsExtVer.Section in Line 2 of PreRequisite
0.181: C:\Windows\system32\WMPhoto.dll is Present
0.181: FileVersion of C:\Windows\system32\WMPhoto.dll is Greater Than 6.0.5840.16388
0.181: Condition Check for Line 3 of PreRequisite returned FALSE
0.221: WIC Setup encountered an error: Newer version of update is already on the system.
0.251: Newer version of update is already on the system.
0.251: Update.exe extended error code = 0xf0f4
0.251: Update.exe return code was masked to 0x643 for MSI custom action compliance.
This issue is caused by Windows Embedded Point of Service SP3 systems having a newer version of WMPHOTO.DLL than the .NET 3.0 installer is carrying and which causes the .NET 3.0 installer to fail.
A successful install of .NET 3.0 can be accomplished after completing the following steps:
- Launch a Command Shell
- CD %windir%\system32
- regsvr32 /u wmphoto.dll
- ren wmphoto.dll wmphoto.dll.old
Now you can install .NET 3.0 with no errors!
- Lynda
When I go to a monthly update download page for POSReady 2009 on the ECE from April, 2009 or earlier, why isn’t POSReady 2009 listed in the title?
The monthly Security updates for Windows Embedded POSReady 2009, from code freeze through April-2009, do not list POSReady 2009 on the download page Titles themselves. This is because the downloads weren’t mapped for POSReady 2009 applicability until April. Updates since April-2009 do list Windows Embedded POSReady 2009 in the page Title. All of the POSReady 2009 Monthly Updates are linked from here:
https://ece.partners.extranet.microsoft.com/ece/Embedded/Products/ProductSupplements/Embedded/POSReady/POSReady2009Updates.htm
What updates should I install from the monthly supplemental DVD I download from the ECE?
POSReady 2009 consumes the same updates as Windows XP. Windows XP updates are delivered on the Desktop Operating System (DTOS) update IMG, along with all other DTOS updates, including Vista, Windows 7, etc.
Use the Security Bulletin announcements (http://www.microsoft.com/technet/security/bulletin/summary.mspx), particularly the Affected Software, Windows Operating System section, to indicate which of the updates are intended for installation on Windows XP. The only updates that are potentially applicable to POSReady 2009 are those updates targeting Windows XP, x86, ENU.
Even some of the Windows XP updates may not be applicable to a POSReady 2009 environment, since it is a subset of Windows XP technologies. If an update is not applicable, it will not install even if executed on the system. This is also how updating Windows XP works, you may not have everything installed that could be installed on the system, therefore the update technology checks to see if the update is required and only installs when it is.
I’m an OEM, how do I ensure my POSReady 2009 image is up to date with Security updates?
End users depend on OEM guidance and a defined servicing plan with their OEM to ensure they install compatible and necessary Security updates. With this plan in place, their systems stay secure, and maintain industry standard compliance if required.
If your servicing plan for your customers includes Windows Update usage, one choice to bring a system current with security updates is to enable Windows Update on the device, and update the device with all required Windows Security Updates.
Another way to ship up-to-date POSReady 2009 devices is to download the monthly security supplemental update DVDs from the ECE, beginning with October, 2008. Apply each Windows XP, x86, ENU Security Update (see the previous question for information about applicable updates) through the current month prior to deploying your devices. Ensure that you have a servicing plan in place with your end users to maintain the security and integrity of the devices.
-Gina
* Updated 11/5/09
Installing the .Net 1.1 SP1 Security Update, KB953297, on Windows Embedded for Point of Service
The MS09-061, Vulnerabilities in the Microsoft .NET Common Language Runtime Could Allow Remote Code Execution update may fail to install on a Windows Embedded Point Of Service Minimum configuration. Extracting the package, and then running the .msp manually will successfully install this update.
Installing the GDI+ Security Update, KB958869, on Windows Embedded for Point of Service and certain installations of Windows Embedded POSReady 2009
Due to an issue with settings to minimize the footprint of Windows Embedded Point Of Service, the MS09-062, Vulnerabilities in GDI+ Could Allow Remote Code Execution update is not getting installed. This has been an ongoing problem with the GDI+ updates and we are working with WinSE to correct this issue for future updates. Please follow these instructions to install this important update. If you have already installed the SP3 update for Windows Embedded Point Of Service, you should use the files from the SP3QFE directory when instructed to move the QFE folder.
- Start a command prompt, this can be done by Clicking on Run from the Start menu, typing ‘cmd’ and pressing Enter.
- Extract the files from the package by changing directories to the directory where you have copied the update and typing the following at the command prompt:
WindowsXP-KB958869-x86-ENU.exe /x:<dir name>
The remainder of these steps can be done from within Windows Explorer or from the Command Prompt as shown by the examples.
- Move the SP2QFE\ASMS folder (or the SP3QFE\ASMS folder if you have installed the SP3 update for WEPOS) to the root of your extracted folder.
move <dir name>\SP2QFE\ASMS . (Note: space and period are required)
- Execute the update.
<dir name>\update\update.exe
- You will be guided through installation wizard to install the package. After installation is complete, the system will reboot.
- You can now delete the temporary folder:
rmdir /s <dir name>
Example: (from a command prompt)
WindowsXP-KB958869-x86-ENU.exe /x:c:\temp\KB958869
cd /d c:\temp\KB958869
move SP2QFE\ASMS . (Note: space and period are required)
cd update
update.exe
Note: This issue may also be evident in Windows Embedded POSReady 2009 systems that are installed to a USB Storage device (not to a standard hard drive). The same workaround can be applied.
-Gina
Technorati Tags:
WEPOS,
Point of Sale
Support for Biometric devices (such as fingerprint readers) was added to the Unified POS specification and incorporated into Microsoft’s POS for .NET in version 1.10. This device category allows applications to interface with such devices and is helpful in capturing and verifying biometric data (such as a finger print). This blog will attempt to describe one possible way to interface with this device using POS for .NET. As always, the developer should first carefully read and understand the Unified POS specification for this device category before attempting to interface with the device (See chapter 5 of Unified POS specification v1.13). Also, before you interface with a physical device, you must install a .NET Service Object for the device (contact the hardware vendor to get the .NET service object). Note that legacy OPOS based service objects are not supported for this device category, one must have a .NET Service Object for this device.
First, an application will want to know what biometric devices are available. This can be done using the PosExplorer class. For example, to get an ArrayList of all Biometric devices, one would do the following:
// Create an instance of an explorer synchronizes events to the main form's thread.
explorer = new PosExplorer(this);
// Create a list of all available biometric devices and bind them to the list box
biometricList = new ArrayList(explorer.GetDevices(DeviceType.Biometrics));
Next, an application may want to register for the DeviceAddedEvent and the DeviceRemovedEvent. Doing so will allow the application to respond to plug-n-play events for the device. Once the application has a device, it will need to do the normal open, claim, and enable as well as subscribe to the required events. This can be done as follows:
// Create an instance of the device, open and claim it.
activeBiometricDevice = (Biometrics)explorer.CreateInstance(selectedDevice);
activeBiometricDevice.Open();
activeBiometricDevice.Claim(1000);
// Enable the device, subscribe to date events, and enable data events
activeBiometricDevice.DeviceEnabled = true;
activeBiometricDevice.DataEvent += new DataEventHandler(activeDevice_DataEvent);
activeBiometricDevice.ErrorEvent += new DeviceErrorEventHandler(activeBiometric_ErrorEvent);
activeBiometricDevice.DataEventEnabled = true;
activeBiometricDevice.StatusUpdateEvent += new StatusUpdateEventHandler(BiometricsStatusUpdateEvent);
The above snippet will open, claim, and enable the device. It will then subscribe to desired events and will enable data events. Once this is done one can use the device as desired. Typically, one will use the beginEnrollCapture() method in order to capture biometric data for a given user. This method customarily results in a series of biometric data captures aggregated together returned in the final form of a BIR (see “beginEnrollCapture” method in the UPOS specification for more detail). Status update events may be provided to instruct the user what actions are required during this process. Status information may include indications such as:
· StatusSensorReady – typically indicates that the device is ready for the user to swipe their finger or provide other biometric data
· StatusSensorComplete – indicates that the biometric data has been captured
· StatusMoveSlower – Indicates that the user needs to move slower
· Etc.
After issuing a beginEnrollCapture method one will wish to save the data in the BiometricsInformationRecord property that is available after a data event. This data is associated with the user providing the biometric input and will be used to identify the person when attempting to verify the user. In order to identify a person, one needs to issue a BeginVerifyCapture command to the device. Again Status update events may be provided as well as a data event (if desired, one can end the operation by issuing an EndCapture command). In response to the data event, the application can then pass a list of BiometricsInformationRecord data to the service object via the IdentifyMatch() method to determine if the biometric data provided by the user matches any contained within the list. This can be done as follows:
List<BiometricsInformationRecord> birs = /* Your list of BIR data */
int[] order =
activeBiometricDevice.IdentifyMatch(50, 0, true,
activeBiometricDevice.BiometricsInformationRecord /* current biometric data to match */,
birs /* list of biometric data to check for match*/ );
Where order[] is a list that identifies all users where the biometric data provided matches within the criteria range specified. Well, that is pretty much all that is needed in order to get biometric data from a user (in the form of a BIR) and then to later verify that the biometric data matches a previously provided BIR.
Microsoft’s POS for .NET supports both native .NET service objects and legacy OPOS service objects which are based upon OLE technology. Normally, POS for .NET interfaces with the legacy devices without any issues and this is done without any interaction or knowledge required by the application. However, there are some rare instances where an application may need to know if the service object is based upon OPOS or .NET. For example, in the rare cases where the OPOS service object requires that the BinaryConversion property be set to a value other than the default the application would need to know the type of service object that it is working with.
Because the BinaryConversion property is specific only to OPOS devices within the standard, it is not exposed by .NET service objects. However, one can still access this property when working with legacy OPOS service objects when this is required by the service object. This can be done by casting the service object returned by the POSExplorer to: ILegacyControlObject. Using the cast type, one can then get and set the BinaryConversion property and other OPOS specific properties.
The default value for the BinaryConversion property is None. However some devices, such as the Ingenico Signature Capture (SigCap) device, may require that the value be set to Nibble or Decimal. In such cases, the application would need to cast the device returned by the POSExplorer to ILegacyControlObject and then set the BinaryConversion property to the desired value (such as Nibble).
To learn more about the BinaryConversion property or any other variations of the standard that are specific to OPOS based service object, see page A-24 of Appendix A of the UnifiedPOS standard specification which is freely available at: http://www.nrf-arts.org/UnifiedPOS/default.htm. The help documentation included with the POS for .NET SDK also has some helpful information.
Developing the USB Boot feature into POSReady was both challenging and rewarding, and certainly loaded with unusual and often unexpected secrets. The biggest gain is that for the first time, the POSReady could easily be installed onto system without an IDE bus. That’s right, no floppy, no CDROM, no hard drive. This was a huge improvement over Windows Embedded for Point of Service which not only required a CDROM for installation, but required a floppy drive if installing to a SATA drive, besides the destination hard drive.
Installing to SATA
In the olden days, users had to store SATA drivers on a floppy drive supplied by the OEM or the motherboard’s manufacturer. Knowing that this was inconvenient for users, many motherboard manufacturers added a “Legacy” mode to allow SATA drives to be accessed as IDE. This may come at a price as some systems must disable some of SATA’s features.
With USB media, this has all changed. POSReady can now load and install drivers real-time, no floppy required.
To do this:
- Find the driver floppy and find a workstation that has a floppy drive installed (this is probably the hardest part).
- Insert the floppy drive and the POSReady USB Setup media into the workstation. Close the Autorun if it comes up, we won’t need it.
- Create a “Drivers” directory on the root of the USB drive.
- If you are deploying POSReady to a number of different systems with different drivers, you may optionally create a sub directory within Drivers. For example, you might have a \Drivers\Sata612 and \Drivers\Sata324 named after the hardware’s name or ID. Setup will look here and any sub directories for driver that match the detected hardware.
- Copy the entire contents of the floppy to this new directory.
- Disconnect the USB drive from Windows
- Insert into the new system and boot from the USB drive.
- You may notice the “Press F6” option will still pop up. Let it go, this will only look for floppy drives.
- One the command prompt appears, type Install to start Setup.
- If you go to fast (like I often do), you might get to the Partition screen and skip the Storage Drivers screen. This will produce a warning if no disks found. This is okay, click the Back button to go to the Storage Drivers screen.
- Click the second radio button to install additional drivers, and click Next. The Partition screen should show your new SATA drive.
Setup should continue normally, hopefully with slightly better performance.
USB to USB
Okay, there are some problems to overcome. It takes a long time to install POSReady to a USB drive. Unfortunately there’s little we could do to make Setup run faster, but the good news is that USB drives read fast. In fact, installation from a USB drive is noticeably faster than a CDROM or DVD. Also, usage of POSReady once it’s installed is surprisingly fast. Depending on your application, you might not even notice the difference compared to a hard drive.
The biggest challenge you will run into is determining boot order. If you’re lucky, your system’s BIOS will allow you to choose this during the boot sequence or in the BIOS configuration. While slightly inconvenient, it’s generally reliable and consistent.
If your BIOS doesn’t allow this, there is a way to determine boot order of USB drives. Strangely, the physical USB ports are always enumerated in a consistent manner by the BIOS which will always boot from the first bootable device if finds.
So, to determine the boot order of USB ports, insert the two devices into ports and boot. If the system fails to boot from them, swap the two drives and try again. You will have a 50/50 chance of getting it right the first time and almost always works the next (with only strange exceptions).
After the first stage of Setup completes, it will then expect the system to boot from the destination drive. As soon as the system is shut down, swap the two drives to update the boot order. Note that USB drive enumeration happens early on in the boot process, so it’s often best to do this with the system turned off.
With this done, Setup should continue to progress and you can remove the Setup media when you see the POSReady logon screen.
Unattended Installs
Windows Embedded for Point of Service and POSReady both support unattended installation through an XML that can be easily generated during Setup (using the /guionly switch). On CDROM installs, this can be tricky forcing users to find a writable location for the XML.
USB drives eliminate this problem. Not only is it easier to store unattended scripts, it also allows other common tasks such as:
1. Adding your own applications to the runtime. This can be done by copying the files to the media and adding the Setup command lines to the Unattend’s RunOnce list.
2. Develop and test more complex scripts, such as updating configuration and registry settings.
Catches
The biggest downside to installing to USB drives (or any solid state media) is that too many writes will eventually damage it. Technology is improving this, but POSReady contains a couple features to help.
- File Based Write Filter (FBWF): This service is installed, but not enabled, by default. Typically this is used more for security, allowing users to update and delete files but have them restored once rebooted. For USB devices, preventing updates to the media means a considerably longer life span.
- Hibernation and Page File. Unfortunately these features are known to make a lot of updates to the hard disk and would be too much for these drives. These features are disabled by default.
More Help
For more help with installing to USB drives, see the MSDN documentation at:
http://technet.microsoft.com/en-us/library/dd458834(WinEmbedded.20).aspx
- Brendan
Technorati Tags:
POS,
WEPOS
