Why Can not I connect the WM5.0 device by the remote process viewer and remote heap walker?

Why Can not I connect the WM5.0 device by the remote process viewer and remote heap walker?

• elgor

  In my exeprience the entire OS needed to be reinstalled
  
  

• wpf michelle

  Remote tools deply a small client application onto the device for communication and info collection. If you didn't have enough memory than the installation might be failing. Looks like everything is working for you now.

  Manav

  
  
  

• Jeff Blake

  You should repair a) Standard SDK for Windows CE 5.0 and b) Windows Mobile 5.0 Pocket PC SDK

  When you install VS first and than install SDK - SDK detects the presence of VS and makes certain entries in the registry so as SDK is available in the VS. If you install SDK first followed by VS than no such entries are made. Doing SDK repair will make those entries and than you should be able to connect via VS.

  Manav

  
  
  

• Clemson

  Astonish!!!

  By the same condition I recorded above, I find I can connect the remote tools with the newest W-zero3 (es).

  Do the remote tools select the target devices or the remote tools require that the target device must have enough memory (Memory of W-zero3 (es) > W-zero3)

  
  
  

• Santiagon

  I moved this message over here from the Aftermarket Solutions forum, I think it will have a much better chance of getting answered over here. Any suggestions

  -Jeremy Kelley

  
  

• ruckazz

  I've seen this problem a number of times and nothing short of OS reinstall was able to fix it. I have two affected machines at the moment, so if you want me to try something. I am here
  
  

• jegar

  To Mr./Ms. Manav:

  Thanks for your reply.

  According to the reason you gave, I have deleted and reinstalled some related programs. But I can not yet connect the remote process viewer and remote heap walker provided by VS2005 with my Microsoft mobile 5.0 Pocket PC (WZero 3). For other remote tools provided by VS2005, the connection is OK. For remote tools provided by Platform builder, all connection is OK but the remote heap walker can not obtain the heap information from non-system program.

  Because I think deletion and reinstallation are more reliable than repair, I didn't choose repair this time. Because it still can not connect with w-zero3, I will try repair later.

  Operation is recorded below:

  Deletion:

  　　　　　　　1. Windows Mobile 5.0 Emulator Images for Pocket PC
  2. Windows Mobile 5.0 Pocket PC SDK
  3. Microsoft Windows CE 5.0 Emulator
  4. Standard SDK for Windows CE 5.0
  5. Microsoft ActiveSync 4.0
  
  Reinstallation
  1. STANDARD_SDK.msi
  2. Microsoft Windows CE 5.0 Emulator
  3. Microsoft Windows CE 5.0 Device Emulator
  4. Microsoft ActiveSync 4.2
  5. Windows Mobile 5.0 Pocket PC SDK.msi
  6. Windows Mobile 5.0 Emulator Images for Pocket PC .msi
  
  

  
  
  

• arkiboys

  Thanks for all the reply.

  Because the conncetion with W-zero3(es) is availabe, I did not do any change to my system then.

  Just as Manav said, remote call tools must require enough memory on the target device. However, not enough memory can not be taken as the reason of the problem I described at the top of the thread.

  It seems that  remote tools are not so helpful in developing large-scale program. Maybe VS2005 with Platform build 6.0 will be better.

  
  
  

• Marcin Książek

  Go to Add/Remove Programs, Select the SDK and click Remove, select "Repair" option in the resulting dialog box.

  Manav

  
  
  

• c_shah

  Alex Feinman wrote:

  In my exeprience the entire OS needed to be reinstalled

  Thank you very much for you quick reply.

  Reinstalling OS is really a big work. I will try if I have enough time.

  After the OS installation, how about the turn of VS2005, platform builder and emulator

  For example

  1. Platform builder

  2. VS2005

  3. Emulator

  
  
  

• soul creator

  Thanks and I want you more help.

  I find four with "SDK" in the add/remove programs, which one should I repair

  Standard SDK for Windows CE 5.0

  Windows Mobile 5.0 pocket PC SDK

  Microsoft Platform SDK

  Microsoft DirectX SDK

  If it is possible, would you pls tell me the reason why repairng SDK can then conncect the WM5.0 device with the remote process viewer and remote heap walker.

  
  
  

• LittleSettler

  Thank you very much for your reply.

  Do you mean I have to reinstall my OS (Windows XP) or just the VS2005 and Platform builder

  Because I want to use remote tools provided by platform builder with the VS2005, would you please give me any suggestion about the turn to install the VS2005, platform builder and other packages or tools(i.e. Activesync, emulator).

   

  
  
  

• ChangLuo

  You need to do SDK repair.

  Manav

  
  
  

• MauriceSibrandi

  Thank you very much for your reply.

  Would you please give me more information about how to repair the SDK

  
  
  
• Why Can not I connect the WM5.0 device by the remote process viewer and remote heap walker?