On Wed, 17 Nov 2010 22:41:21 +0000, ehs01 wrote: I am trying to connect a Symbol/Motorola MC3000 device running Windows CE 5.0 to Windows 7 using Windows Mobile Device Center and the PC is not recognizing the device. When I connect the device, nothing shows up in Device Manager indicating that there is an unrecognized device either. I have read in a few locations that MDC may not support windows CE 5.0. Is this true or is there a work-around for this issue?

When you find something you want to view later, put it in Pocket. What you can get today in Windows CE 5.0 in the 'Professional Plus' license is a range of document viewers (incl. Pocket pc free download - GoToAssist. Best backup apps for Windows and Mac Microsoft Office and top productivity alternatives.

I just connected a Windows Mobile 5 device to WMDC on Windows 7 without any problems. I also connected a Pocket PC 2003 SE device and a Pocket PC (original from 2001). One very common problem is to have the wrong setting for Start -> Settings -> Connections -> USB to PC -> Enable advanced network functionality On my WM 5 device that worked, it is unchecked (disabled). ActiveSync and WMDC can be fussy about ports and cables, so one of them could be a problem. Thanks for the replies. You are correct that the device is a not a phone, but a handheld mobile computer/scanner running Windows CE 5.0, not Windows Mobile.

The devices were able to connect to Windows XP perfectly fine out of the box with only ActiveSync 4.5 installed. The other issue we are having is the devices are actually Symbol devices and Symbol was bought-out by Motorola recently and I have not been able to locate any driver downloads. On my XP machine, the device shows up in Device Manager under 'Windows CE USB Devices'/'Symbol USB Sync'. When connected via USB to our Windows 7 (64bit) machine, nothing shows up in either Device Manager or My Computer/Windows Explorer. On this (and in other sources), I noticed that Windows Embedded CE 5.0 is not listed as being supported and I have been trying to confirm that I understand correctly that the O/S on the devices we have will not be compatible with Win 7/MDC.

I am developing a Smart Device Application in Microsoft Visual Studio 2005 that will run on a Symbol Handheld Device (Model: MC50). I was wondering if anybody knows the class or reference or toolbox control.NET uses to handle barcode scans. I am unable to determine the barcode scan event.

Gramota za uchastie v konkurse chtecov obrazec. Pandora _Ex: pandora's box yashik Pandory 2> istochnik vsyacheskih bedstvii pandora's box noun greek- myth.

I want to be able to scan a barcode capture the value, manipulate the value in the application, display the scanned value, and then write the value to a internal table. Any help or suggestions would be greatly appreciated.

For my applications, I have created a 'Proxy' control that will try to detect the device the application is installed on. This 'Proxy' control will fire its own event when a scan takes place. By using this proxy, you can code your application to one interface, then let the proxy worry about the device specifics.

As you add new hardware, you don't need to putz around with the business logic. Unity pro serial number generator number. If the users of your application are going to depend on having the scanner read a barcode, then I would try to avoid any 'Wedge' software simply because you can not be sure the device will always have the wedge loaded. In the case of the Symbol (now Motorola) 9090x, the wedge is a bit flakey. One thing to consider is device portability.

I also develop for Symbol devices but I try to support a variety of manufacturers. There are two main ways to do this: - Download all of the supported manufacturer's SDKs and use conditional compilation to enable the particular library. The downside to this is that some manufacturers may not be taken into account.

You will need to create a generic/no-SDK build also to support manufacturers for which you do not have the SDK, or for the case where they run the app on a device without a scanner. - Have the scanner enabled external to your application via a wedge. For example, there is a little program called scanwedge.exe for Symbol devices that simply enables the scanner. Then when your app runs, any scans are simply typed into the focused control. Scanning and keyboard entry would look the same from your app's point of view. There are also open source wedges out there.

For Symbol devices I generally use the second method because it is easier to develop. Then just use scanwedge. For my applications, I have created a 'Proxy' control that will try to detect the device the application is installed on.

This 'Proxy' control will fire its own event when a scan takes place. By using this proxy, you can code your application to one interface, then let the proxy worry about the device specifics. As you add new hardware, you don't need to putz around with the business logic.

If the users of your application are going to depend on having the scanner read a barcode, then I would try to avoid any 'Wedge' software simply because you can not be sure the device will always have the wedge loaded. In the case of the Symbol (now Motorola) 9090x, the wedge is a bit flakey.