Connecting to a WinCe device from Vs2005 via Tcpip

G

Guest

Connecting to a WinCe device from Vs2005 via Tcpip

I am working with a WinCe device that does not have a Usb or Rs232. I used
the Vs2003 Tcpip connection. The only access to the device is a Tcpip
connection which did work from Vs2003. I did find the Msdn snippet below but
after transferring the files to the WinCe using the emVcp4 I tried to run the
"conmanclient2.exe" but it would not run.

Any suggestions would be appreciated.


Using whatever connection with the device you have, copy the following files
to the \Windows\ folder on the device. These files are located on the
development computer by default at \Program Files\Common Files\Microsoft
Shared\CoreCon\1.0\Target\wce400\<CPU>.
Clientshutdown.exe
ConmanClient2.exe
CMaccept.exe
eDbgTL.dll
TcpConnectionA.dll
From the command prompt on the device, run conmanclient2.exe.
Determine the IP address of the device.
 
G

Guest

I tried to run CMAccept.exe but got the same response "Cannot execute
CMAccept.exe".

Note that the WinCe device works with Vs2003 and Netcf1.0. By that I mean
that the privious procedure using SDAuthUtilDevice.exe to connect using just
the Tcpip worked.

It should be noted that there have been no changes to its OS . Does
CMAccept.exe or the support files use new functionality that might not have
been in the OS that worked with Vs2003 and Netcf1.0? Please note that I did
not create the OS for this device.

Any suggestions would be appreciated because at present I am unable to
continue.

Thanks.
--
John Olbert



Alex Feinman said:
John,

I think you need to run CMAccept, not ConmanClient2
 
P

Paul G. Tobey [eMVP]

Cannot execute CmAccept implies that a) there is a DLL that it depends on
that is not found (you copied the files to a place not in the path or
something like that. Did you put the items in \Windows?, or b) that the EXE
is not compiled for the right processor. Which CPU version of the files did
you copy to the device?

Paul T.

John Olbert said:
I tried to run CMAccept.exe but got the same response "Cannot execute
CMAccept.exe".

Note that the WinCe device works with Vs2003 and Netcf1.0. By that I mean
that the privious procedure using SDAuthUtilDevice.exe to connect using
just
the Tcpip worked.

It should be noted that there have been no changes to its OS . Does
CMAccept.exe or the support files use new functionality that might not
have
been in the OS that worked with Vs2003 and Netcf1.0? Please note that I
did
not create the OS for this device.

Any suggestions would be appreciated because at present I am unable to
continue.

Thanks.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top