Can't deploy from Visual Studio

[MC]

I am running Win CE 4.1 device, Active Sync 3.5 which is
recommended for 4.1 and never had any previous versions
installed.

Device connected no problem, can browse.

Have followed procedure for copying toolhelp and used the
Runtime Redistributable to get CF installed on device and
CE Utilities to configure Device Processor type.

But deploying gives error Cannot establish a
connection....be sure the device is physically connected.

Thanks,
MC

 

[Chris Tacke, eMVP]

I have the best luck using the Smart Device Authentication utility (under
Tools).

 

[Guest]

Ok, I tried that but SDAuth can't connect says device
refused. I copy SDAuth client over and it won't run saying
it is not a windows ce app.

If you have any more suggestions, please let me know.

 

[Paul G. Tobey [eMVP]]

The device-side program is called sdauthutildevice.exe and needs to be built
in via Platform Builder when the OS is constructed.

Paul T.

 

[Chris Tacke, eMVP]

You can manually copy sdauthutil to the device and run it manually too.
Make sure you have the right processor version.

 

[MC]

Yes I did that but when I run it, it says not a valid
Windows CE App, tried arm4i and arm4T.

Thanks,
Mary

-----Original Message-----
You can manually copy sdauthutil to the device and run it manually too.
Make sure you have the right processor version.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

"Paul G. Tobey [eMVP]"

 

[Paul G. Tobey [eMVP]]

Seems like ARMV4 is more likely to be right...

Paul T.

Yes I did that but when I run it, it says not a valid
Windows CE App, tried arm4i and arm4T.

Thanks,
Mary

-----Original Message-----
You can manually copy sdauthutil to the device and run it manually too.
Make sure you have the right processor version.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

"Paul G. Tobey [eMVP]"

message news:Os8F8E%[email protected]... and needs to be
built


.

 

[MC]

That was exactly it, THANK YOU.

I only had to update the TCPIP Transport settings in
Visual Studio to make that work.

Although I don't quite understand as everything I
installed prior, CF and small test app was arm4T and works.

Processor Type says ARM7TDMI-SA-1110.

Wish there was more docs on doing this by hand to
understand what is really going on.

Thanks again.
MC

-----Original Message-----
Seems like ARMV4 is more likely to be right...

Paul T.

Yes I did that but when I run it, it says not a valid
Windows CE App, tried arm4i and arm4T.

Thanks,
Mary

-----Original Message-----
You can manually copy sdauthutil to the device and run

it
manually too.

Make sure you have the right processor version.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

"Paul G. Tobey [eMVP]"

message The device-side program is called

sdauthutildevice.exe
and needs to be

built
in via Platform Builder when the OS is constructed.

Paul T.

Ok, I tried that but SDAuth can't connect says device
refused. I copy SDAuth client over and it won't run saying
it is not a windows ce app.

If you have any more suggestions, please let me know.

-----Original Message-----
I have the best luck using the Smart Device
Authentication utility (under
Tools).

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

message
I am running Win CE 4.1 device, Active Sync 3.5 which is
recommended for 4.1 and never had any previous versions
installed.

Device connected no problem, can browse.

Have followed procedure for copying toolhelp and used
the
Runtime Redistributable to get CF installed on device
and
CE Utilities to configure Device Processor type.

But deploying gives error Cannot establish a
connection....be sure the device is physically
connected.

Thanks,
MC






.





.

.

 

[Paul G. Tobey [eMVP]]

ARM4T, 4I, and 4 have nothing to do with that processor type. They have to
do with the way in which the OS code is compiled and what types of code it
will support.

Paul T.

That was exactly it, THANK YOU.

I only had to update the TCPIP Transport settings in
Visual Studio to make that work.

Although I don't quite understand as everything I
installed prior, CF and small test app was arm4T and works.

Processor Type says ARM7TDMI-SA-1110.

Wish there was more docs on doing this by hand to
understand what is really going on.

Thanks again.
MC

-----Original Message-----
Seems like ARMV4 is more likely to be right...

Paul T.

Yes I did that but when I run it, it says not a valid
Windows CE App, tried arm4i and arm4T.

Thanks,
Mary


-----Original Message-----
You can manually copy sdauthutil to the device and run it
manually too.
Make sure you have the right processor version.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

"Paul G. Tobey [eMVP]"
message The device-side program is called sdauthutildevice.exe
and needs to be
built
in via Platform Builder when the OS is constructed.

Paul T.

Ok, I tried that but SDAuth can't connect says device
refused. I copy SDAuth client over and it won't run
saying
it is not a windows ce app.

If you have any more suggestions, please let me know.

-----Original Message-----
I have the best luck using the Smart Device
Authentication utility (under
Tools).

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

message
I am running Win CE 4.1 device, Active Sync 3.5
which is
recommended for 4.1 and never had any previous
versions
installed.

Device connected no problem, can browse.

Have followed procedure for copying toolhelp and
used
the
Runtime Redistributable to get CF installed on
device
and
CE Utilities to configure Device Processor type.

But deploying gives error Cannot establish a
connection....be sure the device is physically
connected.

Thanks,
MC






.





.

.