faq.htm

evc WinCE+内存检测工具补丁evc WinCE+内存检测工具补丁evc WinCE+内存检测工具补丁

<ol>
<li>Use the fastest possible connectivity mechanism between you desktop and target device.  Ethernet, of course, yields best performace.  Serial is not practical in many situations.<br><br>
<li>Decrease the number of events reported.  On the Professional edition, there is a "Runtime Options" button on the Run dialog.  Use that to set the minimum level of error reporting you need to analyze the problem you are trying to solve.  Alternatively, the number of events you see CodeSnitch report may cause alarm and raise the question "Does my application really use the heap that much?".  You may determine better strategies for using the heap.<br><br>
<li>CodeSnitch on the target device sends events to CodeSnitch on the desktop in batches.  A batch is defined as 搘hen the event buffer fills?or 搘hen a timeout period?expires.  Then, on the desktop, events are processed in batches (a batch defined the same way).<br><br>
Both parameters can be set in the registry.<br><br>
The buffer size is controlled by a value called EventQueueSize.  On the target device, the default size is 20480 (20K) and the max size is 1048576 (1MB).  On the desktop, the default size is 1MB and the max is 10MB.<br><br>
The timeout period is controlled by a value called WaitCycle.  The default value is 1 second on both the target device and desktop.<br><br>
You should not have to adjust the desktop settings.<br><br>
On the device, first try setting the EventQueueSize to 51200 (bytes) and the WaitCycle to 10 (seconds).  If that looks like it抯 helping, try increasing both values.<br><br>
The registry path is HKEY_LOCAL_MACHINE\Software\Entrek\TOOLBOX\CodeSnitch.<br>
<br>
</ol>

				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="25"><b>Product: ProcMan</b></a><h4>How do I know which thread is which in the Threads view under a process?</h4>If you write a device driver or ActiveX control, or other module that runs in<br>
the process space of an application you did not write, your threads will be one<br>
of many in the threads list. To identify your particular thread, try<br>
inserting an API call in your thread when it is created that will give the<br>
thread some distinguishing feature or characteristic visible from ProcMan.<br>
<br>
For example, the default thread Quantum is 25 ms for versions before 3.0, and 100 ms<br>
for versions after 3.0. You can call CeSetThreadQuantum(GetCurrentThread(), 99) from<br>
each thread in your code, which would help distinguish from the other threads<br>
in the system<br>
<br>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="15"><b>Product: ProcMan</b></a><h4>Can ProcMan connect to a device without RAM file system support.</h4>Yes. You must have the CESH server component available, and have the Platform Builder 3.00 Add-on Pack installed. You must be running Platform Builder with an active connection to a development device.<br>
<br>
In order to connect to a device, you must configure Platform Manager for that device. Here's how:<br>
<br>
<ol>
<li>Run ProcMan.
<li>Select Device | Configure Platform Manager
<li>Select your device in the tree under your platform, then click Properties.
<li>Select your transport method, for instance EDBG or TCP/IP, then click Advanced.
<li>Select CESH from the list of components, then click Configure.
<li>Specify the path to your flat release directory in the edit box provided.
<li>Check the box labelled "Use this server for all file operations." This will cause all remote tool components to be copied to the flat release directory and downloaded only when needed.
<li>Close the Platform Manager configuration and return to ProcMan. You should now be able to connect to the device and view your system.
</ol>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="23"><b>Product: Toolbox General</b></a><h4>Does TOOLBOX support Windows CE.NET</h4>Entrek TOOLBOX version 1.1 has been enabled to work with Windows CE.NET but at this time, we are unable to support this configuration. We have done preliminary testing against Windows CE.NET and are confident that you will not experience any problems. However since our testing is not yet complete, we are unable to offer support. If you are running Entrek TOOLBOX against a Windows CE.NET device, we are interested in hearing from you. Please email your experience to <a href="mailto:[e-mail]">Support at Entrek</a>.<br>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="19"><b>Product: Toolbox General</b></a><h4>Does TOOLBOX support PowerPC (PPC)?</h4>TOOLBOX does not currently support PowerPC.  We will have support for PowerPC in a future release.<br>
<br>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="20"><b>Product: Toolbox General</b></a><h4>Does TOOLBOX support X86 emulation (x86em)?</h4>TOOLBOX does not currently support the x86 emulators (x86em) for PocketPC or Handheld PC.  We will have support for the x86 emulators in a future release.<br>
<br>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="21"><b>Product: Toolbox General</b></a><h4>What will be included in the upcoming service release?</h4>The service release on February 1, 2002, will include the following new features:<br>
<br>
<ol>
<li>In CodeSnitch, settings per application will be saved so that they can be recalled if you stop and then restart CodeSnitch.
<li>In CodeSnitch, tracking of new APIs will be introduced.  Namely, they are CeReadRecordProps, CeReadRecordPropsEx, GetClipboardDataAlloc, and SetClipboardData.
<li>The Run Program dialog now has a Most Recently Used list of programs (MRU). Just click on the drop-down list to select from previously run applications.
<li>Command-line exporting to text is now supported. View the online help for 'exporting to text' for details.
<li>The Sequence column now appears by default in an installation.
<li>Added support for Windows CE 4.0
<li>Downgraded the error 'Attempt to free NULL' to a warning.
</ol>
The service release will also include fixes for the following issues:<br>
<br>
<ol>
<li>Procman hangs in certain situations
<li>In CodeSnitch, false memory leaks or heap corruptions are reported.  The addition of the APIs mentioned above will fix this problem.
<li>In some cases, VirtualAlloc events in CodeSnitch do not have all event data reported.
<li>In certain situations, the symbolic information reported by CodeSnitch is not correct.
<li>Running multiple applications at once cause a 'critical memory error' message in CodeSnitch.
</ol>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="31"><b>Product: Toolbox General</b></a><h4>Does Entrek TOOLBOX support Windows Mobile 5.0 with Visual Studio 2005?</h4>Yes, Entrek TOOLBOX does support Windows Mobile 5.0.  However, there are a few important things you must do to enable it.<br>
<br>
<ol>
<li>Entrek tools use an older connectivity mechanism (Platform Manager) than what is available in VS 2005. VS 2005 uses Core Connectivity, a new technology introduced in VS 2005. To use Entrek tools, you still need Platform Manager. The best way to get that is to install eMbedded Visual C++ 4.0 (eVC 4.0) from http://msdn.microsoft.com/mobility/othertech/eVisualc/howtoget/default.aspx.  Also install eVC 4.0 Service Pack 4.
<li>Entrek ships a redistributable DLL from Microsoft (called dbghelp.dll) used for resolving addresses in your program to source code. That DLL is not compatible with VS 2005 symbols. So you have to rename or delete the file shipped by Entrek, and then set a path to the version installed by VS 2005 (or copy it to the Entrek directory).  The version shipped with Entrek TOOLBOX is typically located in C:\Program Files\Entrek\TOOLBOX\Bin.  The version shipped with Visual Studio 2005 is typically located in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE.
<li>Create a new Platform Manager Connection and configure it to use ActiveSync.  To create a new connection, start either Entrek ProcMan or CodeSnitch, and click the "Configure Platform Manager..." item on the Device menu.  Click the "Add Device" button on the "Windows CE Platform Manager Configuration" dialog that appears.  Enter a name for the device, such as "Windows Mobile 5.0 device".  Then click the "Properties" button.  A "Device Properties" dialog will appear.  Select ActiveSync for both the "Transport" and "Startup Server" properties.
<li>Now establish an ActiveSync connection with your target device.  Once you have an ActiveSync connection, you can connect the Entrek tools to the target.  Note that if you are targetting a Windows Mobile 5.0 emulator, you must first configure ActiveSync to allow DMA connections (right-click the ActiveSync icon in the taskbar tray and select the "Connection Settings..." item to configure this).  You will then need to "cradle" the device emulator using the Device Emulator Manager in VS 2005 (on the Tools menu).  In the Device Emulator Manager, right-click on your target emulator and select the "Connect" item that appears in the context menu.  Then right-click again and select the "Cradle" item.  ActiveSync will then automatically connect to the emulator device.  You cannot have a physical device already connected to ActiveSync.  If you do, first disconnect it before cradling the emulator device.
</ol>
<br>
<br>

				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="32"><b>Product: Toolbox General</b></a><h4>Entrek tools hang when connecting to the target device.  How can I resolve this issue?</h4><ul><br>
<li>You most likely need to install a required patch over the original installation.  See www.entrek.com/products/readme.htm for information about installing this patch.  Please note that the patch does not contain new versions of each file shipped in the original product, so do not delete the original files.  Simply replace the installed files with the new version.<br>
<li>Entrek tools may select the wrong binaries to install on your target device.  For example, it may select ARMV4T, when actually your target device is ARMV4 or ARMV4I.  You can workaround this issue using the /targetcpu command line switch.  See the Known Issues section of the following page for more information: www.entrek.com/products/readme.htm.<br>
</ul><br>
<br>

				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="29"><b>Product: Toolbox General</b></a><h4>Cannot connect to Pocket PC 2002 (or SmartPhone 2002) emulator</h4>Note: The Pocket PC 2002 emulator does not use x86em, and the solutions listed here will not work for x86em.<br>
<br>
There are a few reasons why you may not be able to connect:<br>
<ul>
<li>TOOLBOX, or one of the Microsoft remote tools, crashed or was forced to terminate, and it left CEMGR.EXE or the remote tool in an invalid state. Simply kill the CEMGR.EXE process, close all apps, including the emulator, and try again. If it's really bad, reboot your machine.
<li>The connection was lost somewhere in the middle of communication after connecting previously. This also can leave CEMGR.EXE or the remote tool in an invalid state. Close everything, kill cemgr.exe, reboot if necessary, and try again.
<li>The transport being used is TCP/IP, but you do not have an active network connection on the system. The usual symptoms: The emulator starts up, it appears to download a few files, then it gets stuck when trying to connect with the server. What you need is the Microsoft Loopback Adapter. Follow these steps to install and configure it.
</ul>
Windows XP:<br>
<ol>
<li>Run the Add Hardware wizard from the Control Panel.
<li>Click Next, and let the wizard search for hardware.
<li>When it comes back, select 'Yes I have already connected the hardware', then Next.
<li>In the installed hardware box, select 'Add a new hardware device', then Next.
<li>Select 'Install the hardware that I manually select from a list', then Next.
<li>Double-click 'Network adapters'
<li>From the Manufacturer list, select Microsoft, then select Microsoft Loopback Adapter, then click Next.
<li>click Next, then let it install.
<li>When it is finished, go to Control Panel | Network Connections (in Classic View) and verify a new Local Area Connection is present.
<li>IMPORTANT! You must now right-click on the new connection, select Properties, TCP/IP, then change the default IP address to be fixed instead of automatic. If you allow Windows XP to assign a private IP address, it won't work. I usually use 10.0.0.1, with a Net mask of 255.255.255.0, and NO gateway or DNS.
</ol>
For Windows 2000, the install works essentially the same as above, except the wizard has somewhat different wording.<br>
<br>
<ul>
<li>Now, make sure all remote tools are closed and CEMGR.EXE is not hanging around, then, run CodeSnitch or ProcMan and select Device | Configure Platform Manager.
<li>Select Pocket PC 2002 | Pocket PC 2002 Emulation (or smartphone 2002) and click Properties. Depending on which version of platform manager is installed, you'll see Transport Components with one selected, and Server Components with one selected.
<li>Make sure the Transport is TCP/IP and the Server is Emulator Startup Server. Then, click on TCP/IP and select 'Configure'. Make sure the transport is using a fixed host whose IP address is the same as your Microsoft Loopback Adapter (e.g. 10.0.0.1).
<li>You should be ready to go. Click 'Test' to test the connection.
</ul>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>
<hr><a name="27"><b>Product: Toolbox General</b></a><h4>I want to uninstall Entrek TOOLBOX files from my target device.  What files can I delete?</h4>Both CodeSnitch and Procman automatically install several files on your target device.  We recommend that you leave these files installed while using these tools.  If you remove them, then the files will need to be re-installed the next time you run either CodeSnitch or Procman.  This isn't a problem.  It just increases the initial start time of the tools.<br>
<br>
Here is a list of files installed by CodeSnitch:<br>
<br>
toolbox.exe, tbhelp.dll, onlinemanager.dll, apicore.dll, storemance.dll<br>
<br>
Here is a list of files installed by Procman:<br>
<br>
toolbox.exe, tbhelp.dll, procmance.dll, storemance.dll<br>
<br>
Additionally, files necessary to use Microsoft Platform Manager are installed.  These files are also used by tools installed by both Microsoft Platform Builder and Microsoft eMbeddeded Visual Tools.  Again, if you remove these files, then they will need to be re-installed by the tools that use them.<br>
<br>
				<h5><a href="#top">Back to Top</a></h5>
				<P>&nbsp;</P>

<!--  Content End-->
    </td>
  </tr>
</table>
<!-- Footer -->
<script src="footer.js" language="JavaScript" type="text/javascript"></script>
</body>
</html>