Re: problem of connection to remote kernel tracker
- From: "Zhiqiang Li" <zhiqiang.li@xxxxxxxxxx>
- Date: Wed, 24 Jan 2007 10:46:14 +0100
Hi Sue,
another difference is that under the directory(I am using a german version
windows xp) C:\Programme(Program Files)\Gemeinsame Dateien(Shared
Data)\Microsoft Shared\Windows CE Tools\Platman, there is no subdirectory
"target"as on the another machine.
regards
Zhiqiang
"Zhiqiang Li" <zhiqiang.li@xxxxxxxxxx> schrieb im Newsbeitrag
news:%23dqa%23n5PHHA.4104@xxxxxxxxxxxxxxxxxxxxxxx
Hi Sue,
now after adding SYSGEN_SHELL, SYSGEN_CPP_EH_AND_RTTI and
SYSGEN_STDIOA(my friend who works at microsoft europe innovation
center(Aachen, Germany) send me an email to do that), and locating the
rtsce.dll, I can work with remote kernel tracker on another machine. I
think now it might be a good idea of just installing ce 6.0 again on my
laptop.
thanks a lot!
zhiqiang
"Zhiqiang Li" <zhiqiang.li@xxxxxxxxxx> schrieb im Newsbeitrag
news:Ox0b294PHHA.4424@xxxxxxxxxxxxxxxxxxxxxxx
Hi Sue,
I opened the target control window, and type gi proc, there is no
response. Yesterday I said that I have used dos command "attrib" to
modify these attributes, and each file has an "A" attribute. But "Write
Protected" attribute in the general tab of the property dialog of the
directory is always checked. Each time I clear it, it will restore to a
checked condition when right click on the directory to open the property
dialog. I don't know if this is relevant to the problem.
I have backuped c:\Documents and Settings\<your_username>\Local
Settings\Application
Data\Microsoft\CoreCon\1.0\, and new one is generated, and it still does
not work.
I will done the same the thing on another machine, on which only ce 6.0
is installed, and I will tell you the result.
thanks a lot.
Zhiqiang
"Sue Loh [MS]" <sloh@xxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag
news:%230wili0PHHA.2312@xxxxxxxxxxxxxxxxxxxxxxx
Okay, does the target control window work? Try typing "gi proc" to see
if it's alive. If that works, try using "s foo.exe" (or whatever) to
execute an exe from your release directory, to check that the release
directory connection is working.
After that, hmm. Try deleting or renaming this directory:
c:\Documents and Settings\<your_username>\Local Settings\Application
Data\Microsoft\CoreCon\1.0\
You'll end up having to recreate your device settings in Platform
Builder by going to target->connectivity options and creating a new
target device.
If those don't work I'll have to keep brainstorming.
Sue
sloh@xxxxxxxxxxxxx (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no
rights.
_____________________________________________________________
.
- References:
- problem of connection to remote kernel tracker
- From: Zhiqiang Li
- Re: problem of connection to remote kernel tracker
- From: Sue Loh [MS]
- Re: problem of connection to remote kernel tracker
- From: Zhiqiang Li
- Re: problem of connection to remote kernel tracker
- From: Sue Loh [MS]
- Re: problem of connection to remote kernel tracker
- From: Zhiqiang Li
- Re: problem of connection to remote kernel tracker
- From: Zhiqiang Li
- problem of connection to remote kernel tracker
- Prev by Date: Re: USB host controller and client driver
- Next by Date: Re: KITL enabled in RTM 6 BSP for MX21, however debug didn't work
- Previous by thread: Re: problem of connection to remote kernel tracker
- Next by thread: Re: How to create a new PSL?
- Index(es):
Relevant Pages
|
Loading