The new version of the tool I sent to you should look up the right folder.
Can you copy the new SDAuthUtil.exe and CryptAPIWrapper.dll to the same
folder and run the exe there? That folder can be anywhere on your Visual
Studio machine.
Ximing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Smart Device Authentication Utility
| thread-index: AcOtoyOehG1WntnYQqO2mrvN4rxlyA==
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| From: "=?Utf-8?B?Smlhbmc=?=" <
[email protected]>
| References: <
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
| Subject: RE: Smart Device Authentication Utility
| Date: Mon, 17 Nov 2003 23:11:08 -0800
| Lines: 22
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: TK2MSFTCMTY1 10.40.1.180
| Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:38908
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| Hi Ximing,
I've got your program. I moved it into "E:\Program Files\Microsoft Visual
Studio.NET 2003\CompactFrameworkSDK\ConnectionManager\Target\wce400\armv4\"
folder and renamed the orginal one as a .bak file. Now here is what
happening:
1. There is an Icon called .Net Link on my SBC which I am supposed to run
before I run the Utility. So I run it first and then run the Utility. I
tried running the Utility from VS.NET 2003 and running it directly from
Windows Explorer. It makes no difference and I got the following error
message:
"Unknown error occured while prepping deviceSystem.DllNotFoundException:
Unable to load Dll (cryptoAPIWrapper.dll).
at Microsoft.SDAuthUtil.Form1.Wrap-CryptAcquiteContext()
at Microsofta.SDAuthUtil.Form1.DoPrepDevice()"
I did searching on my PC, the "crytoAPIWrapper.dll" is located in
"...\Microsoft Visual Studio.NET 2003\..." folder. It seems I still have
the orignal problem that is my VS.NET somehow has messed up the folders. It
must be looking wrongly at "...\Microsoft.NET\..." for the file. So, I'm
afraid that even if I can solve this "cryptoAPIWrapper.dll" problem, I may
still have other problems later. It seems I need to reset some HKEY or
alike to make my program look for CF related files in the "...\Microsoft
Visual Studio.NET 2003\..." forder, not the "...\Microsoft.NET\..." folder.
2. After read other posts on this board, I tried copying
"sdauthutildevice.exe" to my SBC and run it. It shows an exactly interface
look as my original .NET Link (its file name is DOT_NET_DEBUG.exe), and
gives the same error messages.
3. I tried not running the .NET Link program on my SBC. Then if the SBC is
off, I got a error message saying "Device IP address not found. ... A
connection attempt failed because the connected party did not properly
response after a period of time, or established connected host has failed
to respond. ...". If the SBC is on, I got the error message saying "Device
IP address not found. ... No connection could be made because the target
machine actively refused it. ..." So, it seems the physical connection is
there. The main problem is still that my PC looks into wrong folders for
the needed files.
Any suggestion?
Thanks.
Jiang
SofTA Corporation
|