Im development an vb.net application to a Windows Ce 5.0 build 1400 device, but it doesnt work in this device, it only works on Windows Ce 5.0.
What is the "Build 1400"? How can i remove it?
Thanks,
It's simply a build number generated with the OS. You can't "remove" it.
If you have two devices, one on which the app work and one on which it doesn't, both running the same OS (CE 5.0 in this case), then it's likely that it's a component issue in the OS. It could be a driver difference, a P/Invoke library difference, a core OS feature difference, or even an OAL difference.
Without you defining "doesn't work" in more detail, that's as detailed as I can get. You'll have to use debugging and determine where the app is failing, and then determine what is missing from the OS to cause that failure.
Related
I'm trying to create windows CE OS that will run in my industrial CPU using Microsoft Studio 2005. All my tried was failed.
Im trying to build a Windows CE that have
Catalog items view
Storage
Primary disk/storage/master/slave
Secondary
CAB
CF card
Device Manager
Registry flush
Pci 1710
Internet explorer
.netframework
C++
Usb
Uno3072l
Display
Audio
And other basic utilities
I hope that someone will build the windows for me without any error. And share the link here so i can download.
Or, someone who can teach me how to solve the error. I am really stuck.
The Advantech 3072L is a simple x86-basd machine. You can likely use the x86 BSP that ships with Platform Builder, though Advantech may also have a platform specific BSP for any peripherals. Without more info on the version of Platform Builder you're using, what you've tried and the errors you're seeing we can't provide much more help than that.
I have built an smart device app in VS 2008. I could deployed and debugged in Windows Mobile OS devices successfully.
But, I must have to deploy and debug the same app usign Windows CE 4.1 device as well. The problem is compact framework version that indicates the app is higher version of compact framework so i can not run the app in CE 4.1 device.
So I have tried to debug the app using emulator.
I would like to ask that I have failed to debug the app in any emulator which is listed in VS 2008 devices list.
I'd be glad if there is a workaround to solve the issue!
thanks!
Check out this topic: Minimal system requirements for .NET Compact Framework 3.5
It may help you. Deploying maybe possible but debugging will be very slow if it is working. I tried this with a PPC2003-device and this was horribly slow.
You have too keep in mind that CF3.5 needs much more CPU and Memory.
I am developing Qt application for Windows CE 5.0 device.
My setup is:
Qt 4.7.3 compiled with Visual Studio 2005 using Windows CE 5.0 Standard SDK.
Everything works OK on real device, though I would like to test software "locally" in an emulator.
Visual Studio 2005 provides Pocket PC 2003, Windows Mobile 6 emulator images but no Windows CE 5.0.
Windows Microsoft CE 5.0 Emulator does that, but its sample device is based on i486, so this doesn't work for me...
I found some kind "Plaftorm Builder" and "ARMV4i BSP for Windows CE 5.0", but I am not building device or it's SDK, and I am not interested in specific device at all. All i need is "generic" AMRv4 WinCE 5 image for basic testing...
So what is possible outcomes for me?
Microssoft stopped providing Windows CE OS images for the emulator after the x86 emulator was abandoned, and for good reason. Windows CE is a modular OS so it's not possible to create an Emulator OS image that matches what all devices are and my guess is that there were too many support calls and complaints about how the emulator either contained something unwanted or didn't contain something that was wanted. The point being that there is no "generic Windows CE device" so there's no way to create an emulator of one.
The response from Microsoft was to provide the ARM-based Device Emulator 3.0 (available as a Standalone Release) and a BSP for the emulator so developers can create their own OS images that match their actual target hardware OSes.
So your options are to either create an OS yourself or find an OEM that provides an emulator image for their device (I'm not aware of one offhand, but I very, very rarely use the emulators so I've never bothered to look).
I have taken over a Windows-CE 6.0 application that I would like to port to other platforms. It is a relatively straightforward, self-contained GUI application, written in Embedded C++ Version 4.0
The very first target I am interested in would be a regular Windows desktop (i.e. XP, Vista, Windows-7).
I understand that porting a desktop application to CE is nontrivial; but what about the reverse, which is what I am interested in? Is going from Windows-CE to Windows Desktop (somewhat) upward-compatible? I sure would love to hear "buy this $1000 Microsoft XYZ C++ development environment and just compile and go!"
(FYI I have no experience with GUI applications nor with programming in the Windows environment; pretend I am but a simple linux/unix guy with decades of C/C++ experience but absolutely no Windows-Fu... ;-)
Porting up should, actually, be pretty straightforward. CE is mostly a subset of Win32, with heavy emphasis on Unicode.
You can probably make sure UNICODE is defined, build and, with a little luck, most of it will "just work". Places that are going to be hangups are:
The UI is likely to be set for a resolution that doesn't match your PC - often CE apps are targeted to a specific device and resolution and this doesn't necessarily come out very aesthetic on a PC.
Anything dynamically loaded (GetProcAddress) from coredll will have to be re-mapped to kernel32/user32/etc
If the device uses the SIP (software input panel - i.e. on-screen keyboard) then all of that has to get stripped out.
If the app uses any Notifications (icons, etc) that has to get replaced
If the app uses any power management, that has to get ripped out
If the app uses any device-specific stuff - especially direct calls to drivers, all of that has to be replaced
If the app is using point to point queues, that has to get replaced
If the app is using the device manager (e.g. to get notifications of copnnected devices) that has to get replaced
Any calls into aygshell.dll are likely to be problematic as well.
As i just need the hard RT capabilities, can I install and run Windows Embedded CE 6.0 on a regular PC ? (dell or so ?), and UDP out some data ?
You can install Windows CE in a PC, but you would need to create your own image. See this tutorial in MSDN. Also google for CEPC.
Finally visit Mike Hall's blog. I remember reading a related article there, but I can't find it now. Anyhow, this blog is a great resource for Windows Embedded.
(From working with Windows CE 5.0, so there may be some differences, YMMV.)
You should be able to run Windows CE both in an emulator and installed on the device itself as the host operating system.
In the first case all you need is an emulator, which is provided with the development kit and in a more expensive version of Visual Studio. This will run the OS fine, albeit a bit slow depending on the architecture you choose to build the Guest OS for.
In the second case you will actually need to find or write drivers for the hardware that you want to run on and use. This will require the Platform Builder application (I believe it's a plugin to Visual Studio now) and knowledge of the hardware that you are running on. Windows CE itself does support x86 processors, although I don't remember if it supports all x86 processors (instruction sets) or just 486's.
If you want to go down the second route you also may be able to get an Intel Atom or AMD Geode board support package (BSP) which will help you develop the drivers.