Casio IT500 and Authentication Util

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

Hi,
Has anyone successfully deployed to one of these beasties?
I am totally confused.
The device blurb talks of a processor type of a Intel PXA250. The System
properties on the device shows 'ARM-X'
The WINCE Config lists neither.

I have tried putting the x86 and armv4 versions of SDAuthUtilDevice.exe on
the device but when I double click them I get a message that it is not a
proper CE program.

Any help on this would be appreciated.
regards
Bob
 
The PXA250 *is* an ARM device. For the purposes of the VS.NET 2003 device
types, it's an ARMV4 device (or ARMV4i, maybe).

Paul T.
 
Thanks Paul,
V4t worked.
regards
Bob
Paul G. Tobey said:
The PXA250 *is* an ARM device. For the purposes of the VS.NET 2003 device
types, it's an ARMV4 device (or ARMV4i, maybe).

Paul T.
Click to expand...
 
Hi Paul,
After my initial euporia, I am still in trouble.
Although the device side starts and reveals the IP addresss.
The IDE side says it can't make the connection as 'the target actively
refused it.'
I have been into the tools options in the IDE and set the device IP address
to the one displayed by the device but this made no difference.
Any ideas.
Thanks
Bob
 
Have you looked up past history of that sort of problem in the newsgroup
archives? Google archives everything...

http://groups.google.com/groups?hl=...soft.public.dotnet.framework.compactframework

If it were me, I'd use a network sniffer to verify that your desktop machine
is sending packets to the device and, based on what you got back, that the
device is rejecting the attempted connection. If so, you might verify that
the network interface (which you didn't tell us anything about), has the IP
address that is shown in the device-side authentication program. Check the
subnet mask, etc.

Paul T.
 
Hi Paul,
Checked the archives,
No Joy.
Re:Network Sniffer. I have never used one. If we have to, could you advise
what to get and some general gulelines. The activesync link to the CE device
is on the USB port (see below) is a sniffer still relevant?
Re Network:
The development platform is a Win2k Server that is a domain controller. The
connection to the LAN is a standard ethernet card running at 100mhz over
UTP.
The connection to the CE device is via a USB port which has a InfraRed
adaptor plugged into it.
The address displayed by the device Authentication utility is 192.168.55.101
I don't seem to have any control over this.
I tried making a new network connection on the device but this comes up with
a 'disconnected' msgbox when I double click it.

The IDE machine is 192.168.0.37
Subnet mask on the IDE machine 255.255.255.0

Thanks for your continued assistance.

Regards
Bob
 
Have you actually tried any of the items in the archives (there are many
threads that started with 'make sure the device is connected'-like
question)? If you have network connectivity on the device, try using that
instead of the USB connection. I don't think that I have any other
productive suggestions...

Paul T.

Bob said:
Hi Paul,
Checked the archives,
No Joy.
Re:Network Sniffer. I have never used one. If we have to, could you advise
what to get and some general gulelines. The activesync link to the CE
device
is on the USB port (see below) is a sniffer still relevant?
Re Network:
The development platform is a Win2k Server that is a domain controller.
The
connection to the LAN is a standard ethernet card running at 100mhz over
UTP.
The connection to the CE device is via a USB port which has a InfraRed
adaptor plugged into it.
The address displayed by the device Authentication utility is
192.168.55.101
I don't seem to have any control over this.
I tried making a new network connection on the device but this comes up
with
a 'disconnected' msgbox when I double click it.

The IDE machine is 192.168.0.37
Subnet mask on the IDE machine 255.255.255.0

Thanks for your continued assistance.

Regards
Bob



Paul G. Tobey said:
Have you looked up past history of that sort of problem in the newsgroup
archives? Google archives everything...

http://groups.google.com/groups?hl=...soft.public.dotnet.framework.compactframework

If it were me, I'd use a network sniffer to verify that your desktop machine
is sending packets to the device and, based on what you got back, that
the
device is rejecting the attempted connection. If so, you might verify that
the network interface (which you didn't tell us anything about), has the IP
address that is shown in the device-side authentication program. Check the
subnet mask, etc.

Paul T.

Bob said:
Hi Paul,
After my initial euporia, I am still in trouble.
Although the device side starts and reveals the IP addresss.
The IDE side says it can't make the connection as 'the target actively
refused it.'
I have been into the tools options in the IDE and set the device IP
address
to the one displayed by the device but this made no difference.
Any ideas.
Thanks
Bob

"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message The PXA250 *is* an ARM device. For the purposes of the VS.NET 2003
device
types, it's an ARMV4 device (or ARMV4i, maybe).

Paul T.

Hi,
Has anyone successfully deployed to one of these beasties?
I am totally confused.
The device blurb talks of a processor type of a Intel PXA250. The
System
properties on the device shows 'ARM-X'
The WINCE Config lists neither.

I have tried putting the x86 and armv4 versions of SDAuthUtilDevice.exe
on
the device but when I double click them I get a message that it is not
a
proper CE program.

Any help on this would be appreciated.
regards
Bob
Click to expand...
Click to expand...
Click to expand...
 
Hi Paul,
Problem solved.
I moved on from the authentication utility and with a bit of playing around
was able to get application deployment and debug working.
Thanks again for your efforts.
regards
Bob

Paul G. Tobey said:
Have you actually tried any of the items in the archives (there are many
threads that started with 'make sure the device is connected'-like
question)? If you have network connectivity on the device, try using that
instead of the USB connection. I don't think that I have any other
productive suggestions...

Paul T.

Bob said:
Hi Paul,
Checked the archives,
No Joy.
Re:Network Sniffer. I have never used one. If we have to, could you advise
what to get and some general gulelines. The activesync link to the CE
device
is on the USB port (see below) is a sniffer still relevant?
Re Network:
The development platform is a Win2k Server that is a domain controller.
The
connection to the LAN is a standard ethernet card running at 100mhz over
UTP.
The connection to the CE device is via a USB port which has a InfraRed
adaptor plugged into it.
The address displayed by the device Authentication utility is
192.168.55.101
I don't seem to have any control over this.
I tried making a new network connection on the device but this comes up
with
a 'disconnected' msgbox when I double click it.

The IDE machine is 192.168.0.37
Subnet mask on the IDE machine 255.255.255.0

Thanks for your continued assistance.

Regards
Bob



Paul G. Tobey said:
Have you looked up past history of that sort of problem in the newsgroup
archives? Google archives everything...
Click to expand...
http://groups.google.com/groups?hl=...soft.public.dotnet.framework.compactframework
If it were me, I'd use a network sniffer to verify that your desktop machine
is sending packets to the device and, based on what you got back, that
the
device is rejecting the attempted connection. If so, you might verify that
the network interface (which you didn't tell us anything about), has
Click to expand...
the
IP
address that is shown in the device-side authentication program. Check the
subnet mask, etc.

Paul T.

Hi Paul,
After my initial euporia, I am still in trouble.
Although the device side starts and reveals the IP addresss.
The IDE side says it can't make the connection as 'the target actively
refused it.'
I have been into the tools options in the IDE and set the device IP
address
to the one displayed by the device but this made no difference.
Any ideas.
Thanks
Bob

"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message The PXA250 *is* an ARM device. For the purposes of the VS.NET 2003
device
types, it's an ARMV4 device (or ARMV4i, maybe).

Paul T.

Hi,
Has anyone successfully deployed to one of these beasties?
I am totally confused.
The device blurb talks of a processor type of a Intel PXA250. The
System
properties on the device shows 'ARM-X'
The WINCE Config lists neither.

I have tried putting the x86 and armv4 versions of SDAuthUtilDevice.exe
on
the device but when I double click them I get a message that it is not
a
proper CE program.

Any help on this would be appreciated.
regards
Bob
Click to expand...
Click to expand...
Click to expand...
 
Back
Top