This article describes two issues that occur when you insert an SD card into a USB multi-card reader and then remove the card from the reader on a Windows Embedded Compact 7-based device. Before you install the update, all previously issued updates for this product must be installed.
Symptoms
When you insert an SD card into a USB multi-card reader on a Windows Embedded Compact 7-based device and then remove the card from the reader, you may encounter the following issues.
-
Assert issue in File System Disk Manager (FSDMGR) functionsConsider the following scenario:
-
You create an OS design that sets BSP=CEPC, Template=Enterprise Device Handheld. The other OS design UI dialog boxes use the default settings.
-
You set sysgens as provided by the SysgenSettings.out file, and then you build a debug image (with debugger + KITL support) by calling Build Solution.
-
You start the image on a virtual machine until the Windows Embedded Compact 7 shell or desktop is visible.
-
You attach a USB multi-card reader without an SD card to the device.
-
You insert an SD card into the USB multi-card reader.
-
You remove the SD card from the USB multi-card reader.
In this scenario, an assert issue occurs in the File System Disk Manager (FSDMGR) functions.
-
-
Certain function behavior of CeResyncFilesys API changesConsider the following scenario:
-
You have a NK.BIN file, and you start the Windows Embedded Compact 7-based device in a debug build environment.
-
You attach a USB multi-card reader without an SD card to the device.
-
You insert an SD card into the USB multi-card reader.
-
You remove the SD card from the USB multi-card reader.
In this scenario, the behavior of certain function in the CeResyncFilesys API changes.
-
Resolution
Download information
The Windows Embedded Compact 7 Monthly Update (October 2014) is now available from Microsoft. To download this Windows Embedded Compact 7 monthly update, go to the following Microsoft Download Center website:
Windows Embedded Compact 7 updates The kind of processor that each file applies to is visible in the name of each file in the "File information" section.
More Information
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
|
File name |
File size |
Date |
Time |
Path |
|---|---|---|---|---|
|
Fsdmgr_lib.lib |
2,411,526 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\X86\Retail |
|
Fsdmgr_lib.lib |
2,696,670 |
20-Oct-2014 |
17:13 |
Public\Common\Oak\Lib\X86\Debug |
|
Fsdmgr_lib.lib |
2,582,674 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\X86\Checked |
|
Fsdmgr_lib.lib |
2,771,058 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\Armv5\Retail |
|
Fsdmgr_lib.lib |
3,184,176 |
20-Oct-2014 |
17:04 |
Public\Common\Oak\Lib\Armv5\Debug |
|
Fsdmgr_lib.lib |
2,954,414 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Armv5\Checked |
|
Fsdmgr_lib.lib |
2,771,310 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Armv6\Retail |
|
Fsdmgr_lib.lib |
3,184,396 |
20-Oct-2014 |
17:06 |
Public\Common\Oak\Lib\Armv6\Debug |
|
Fsdmgr_lib.lib |
2,954,660 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Armv6\Checked |
|
Fsdmgr_lib.lib |
2,768,596 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Armv7\Retail |
|
Fsdmgr_lib.lib |
3,181,612 |
20-Oct-2014 |
17:07 |
Public\Common\Oak\Lib\Armv7\Debug |
|
Fsdmgr_lib.lib |
2,951,132 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Armv7\Checked |
|
Fsdmgr_lib.lib |
2,710,114 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\Mipsii\Retail |
|
Fsdmgr_lib.lib |
3,156,696 |
20-Oct-2014 |
17:09 |
Public\Common\Oak\Lib\Mipsii\Debug |
|
Fsdmgr_lib.lib |
2,871,404 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Mipsii\Checked |
|
Fsdmgr_lib.lib |
2,711,874 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\Mipsii_fp\Retail |
|
Fsdmgr_lib.lib |
3,158,334 |
20-Oct-2014 |
17:10 |
Public\Common\Oak\Lib\Mipsii_fp\Debug |
|
Fsdmgr_lib.lib |
2,873,160 |
20-Oct-2014 |
15:12 |
Public\Common\Oak\Lib\Mipsii_fp\Checked |
|
Fsdmgr_lib.lib |
2,557,534 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\Sh4\Retail |
|
Fsdmgr_lib.lib |
2,950,166 |
20-Oct-2014 |
17:10 |
Public\Common\Oak\Lib\Sh4\Debug |
|
Fsdmgr_lib.lib |
2,685,896 |
20-Oct-2014 |
15:11 |
Public\Common\Oak\Lib\Sh4\Checked |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.
