develop on WindowsCE terminal?

  • Thread starter Thread starter Zanna
  • Start date Start date
Z

Zanna

Hi all,

I have an out-of-the-box WindowsCE.net terminal (640*240 screen).

Now, I have no idea on how to start developping for it with VS.net.
What do I need?

Also when I ask it for the processor type it say PXA250... what the f**k
of CF supported processortype is it?

Now it is linked to my lan by a lan-cable, and from it I can reach
others pc, but why from PC I cannot reach it?

Thanks!
 
You need Visual Studio.NET 2003. The device needs to run Windows CE.NET 4.1
or higher.
Click to expand...


In System Properties I see Windows CE.NET 4.2, so thi s can be ok.
To connect to it you need the Visual Studio.NET 2003 add-on pack:
http://www.microsoft.com/downloads/...A6-2095-4086-B0CC-7C6C39B28762&displaylang=en.
Click to expand...

I already installed it, but It tell me always that the device is not
reachable :(
The PXA250 is an XScale processor.
Click to expand...

And from the list under Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\wce400, what is the XScale?

armv4
armv4t
mips16
mipsii
mipsii_fp
mipsiv
mipsiv_fp
sh3
sh4
x86

???

Thanks again
 
Zanna said:
I already installed it, but It tell me always that the device is not
reachable :(
Click to expand...

The right message is:

"
Device IP Address not found.
Run the device component of this utility to find the IP address of the
device.
"

What is the "device component" I have to run?

Thanks
 
It's an armv4.
Click to expand...

mmm... the only package I can install on it is the armv4t :P

Also I tryied to do a Smart app ot type WinCE (but I have a form too
large!) and a PocketPC app, but when I start them on the terminal it
says that these aren't a WinCE app :(
 
How about telling us *what device* it is? We can't give specific and
accurate answers if you won't give us any real information. Any of the
"ARM" processor types might be right, depending on how the OS was compiled
for installation on the device. It also seems kind of silly not to ask the
device manufacturer how to connect to it...

Paul T.
 
Back
Top