Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: OpenStore function cannot open the storage device that is loaded by AutoLoad registry of Storage Manager on a Windows Embedded Compact 7-based device

FIX: OpenStore function cannot open the storage device that is loaded by AutoLoad registry of Storage Manager on a Windows Embedded Compact 7-based device

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Embedded Compact 7-based device that has the following AutoLoad registry setting:
    [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\<devicename>]

    Note <device name> is a placeholder and it has more than 7 characters.
  • You run an application that calls FindFirstStore function to retrieve the name of the storage device that is loaded by AutoLoad registry of Storage Manager.
  • The application then calls OpenStore function and passes the STOREINFO.szDeviceName that is retrieved from FindFirstStore function to open the storage device.
In this scenario, the FindFirstStore function only returns the first 7 characters as STOREINFO.szDeviceName. For example, if the AutoLoad registry sub-key you specified resembles:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\FlashDisk]

FindFirstStore function only returns "FlashDi" as STOREINFO.szDeviceName, so OpenStore function fails because of incorrect device name passed.

Note This issue typically occurs when <device name> has more than 7 characters, and when Windows Embedded Compact 7 Monthly Update September 2013 is applied.

↑ Back to the top

More Information

Software update information

Download information

The Windows Embedded Compact 7 Monthly Update (December 2013) 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.

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

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.
File information
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 nameFile sizeDateTimePath
Storemain.cpp56,83620-Dec-201301:52Private\Winceos\Coreos\Storage\Fsdmgr
Fsdmgr_lib.lib2,972,85220-Dec-201301:42Public\Common\Oak\Lib\Armv5\Checked
Fsdmgr_lib.lib3,196,53020-Dec-201301:41Public\Common\Oak\Lib\Armv5\Debug
Fsdmgr_lib.lib2,789,05620-Dec-201301:41Public\Common\Oak\Lib\Armv5\Retail
Fsdmgr_lib.lib2,973,10420-Dec-201301:43Public\Common\Oak\Lib\Armv6\Checked
Fsdmgr_lib.lib3,196,76620-Dec-201301:43Public\Common\Oak\Lib\Armv6\Debug
Fsdmgr_lib.lib2,789,30820-Dec-201301:43Public\Common\Oak\Lib\Armv6\Retail
Fsdmgr_lib.lib2,969,56620-Dec-201301:45Public\Common\Oak\Lib\Armv7\Checked
Fsdmgr_lib.lib3,193,97020-Dec-201301:45Public\Common\Oak\Lib\Armv7\Debug
Fsdmgr_lib.lib2,786,59820-Dec-201301:45Public\Common\Oak\Lib\Armv7\Retail
Fsdmgr_lib.lib2,889,37820-Dec-201301:47Public\Common\Oak\Lib\Mipsii\Checked
Fsdmgr_lib.lib3,168,75620-Dec-201301:47Public\Common\Oak\Lib\Mipsii\Debug
Fsdmgr_lib.lib2,727,80420-Dec-201301:47Public\Common\Oak\Lib\Mipsii\Retail
Fsdmgr_lib.lib2,891,13820-Dec-201301:49Public\Common\Oak\Lib\Mipsii_fp\Checked
Fsdmgr_lib.lib3,170,51620-Dec-201301:49Public\Common\Oak\Lib\Mipsii_fp\Debug
Fsdmgr_lib.lib2,729,56420-Dec-201301:49Public\Common\Oak\Lib\Mipsii_fp\Retail
Fsdmgr_lib.lib2,704,30420-Dec-201301:51Public\Common\Oak\Lib\Sh4\Checked
Fsdmgr_lib.lib2,962,85820-Dec-201301:51Public\Common\Oak\Lib\Sh4\Debug
Fsdmgr_lib.lib2,575,58020-Dec-201301:51Public\Common\Oak\Lib\Sh4\Retail
Fsdmgr_lib.lib2,602,30220-Dec-201301:52Public\Common\Oak\Lib\X86\Checked
Fsdmgr_lib.lib2,711,35220-Dec-201301:52Public\Common\Oak\Lib\X86\Debug
Fsdmgr_lib.lib2,430,73420-Dec-201301:52Public\Common\Oak\Lib\X86\Retail

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbfix, kbsurveynew, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 2912406
Revision : 1
Created on : 1/7/2017
Published on : 1/14/2014
Exists online : False
Views : 205