help with windows ce command prompt

Question

Hello all,

I have the following problems with Windows CE command Prompt

none of the following commands is executing:

s ipconfig /d

gi proc

and others...

 

I used platform builder to build an SDK for x86, and I'm using the corresponding emulator.

After successful built of the OS, within visual studio 2005 (and platform builder r2), I open the Win CE command prompt, with the aforementioned effects.

 

some help please...

regards

ilias

Answer 1

You should have KITL enabled in your OS image to get those commands executed on the Target control shell.

Enable the KITL in the menu "Project-->Properties-->Configuration Properties-->Build Options-->Enable KITL".

After enabling build the OS image and download it.
--
Regards,
Prabu
http://prabukumar.wordpress.com/
www.e-consystems.com

Answer 2

The command you have shown only work on Target control shell (The shell used when you connect your device with KITL Enabled) on VS2005 platform builder. it won't work on cmd prompt.

s < proc name>

gi ["proc","thrd","mod","all"]* ["<pattern>"] : Get Information
    proc   -> Lists all processes in the system
    thrd   -> Lists all processes with their threads
    delta  -> Lists only threads that have changes in CPU times
    mod    -> Lists all modules loaded
    moduse -> Lists module usage data
    system -> Lists processor architecture and OS version
    all    -> Lists all of the above

These are Target control shell command and not the command console commands.

if you want to check ipconfig you have to directly use "ipconfig" command in the command prompt and don't add 's' infront of the command.

Also verify SYSGEN_NETUTILS component is added in your Wince device emulator OSDesign. ipconfig is the part of that component.

 

---

Vinoth.R http://vinoth-vinothblog.blogspot.com http://www.e-consystems.com

Answer 3

Ok. thank you guys for the replies... I will check them and report back

regards

ilias

Answer 4

hm... The options you mentioned are already checked, but still no luck.

Let me explain the procedure I am following.

After building the OS image i configured the emulator as follows

1.  Target Device Connectivity Options   -->   Device Emulator (DMA) for both the Download and Transport options.

2.  Target Device Connectivity Options   -->  Debugger --> KdStub

3.   Target Device Connectivity Options   --> Download Settings, to get to the Emulator Properties window.

4.    Emulator Properties --> General --> checked Specify RAM size and entered !@*

5.    Configured screen width to 640 and screen height to 300. 16 bits per pixel in color depth

6.    Emulator Properties -->Network tab, checked "Enable NE2000 PCMCIA network adapter" and bind to "Connected network card.

Wait, all these settings seem correct. I think that the problem is that I want to use a x86 emulator, but in the initial project creation I selected "CEPC: x86" as a bsp. Which means that It needs to be connected to an actual PC. What I want is an emulator. So these settings are wrong...

Am I correct? If Yes, how can I use an x86 device emulator???

Answer 5

The Emulator BSP given in Windows CE 6.0 is  ARMV4I Emulator and it is not a X86 Emulator. Which BSP you are using for build your project? CEPC or DeviceEmulator .

you have to use DeviceEmulator BSP to use the existing device emulator.

---

Vinoth.R http://vinoth-vinothblog.blogspot.com http://www.e-consystems.com

Answer 6

 

If you want a X86 emulator for WinCE 6.0,then check out this Virtual PC.

• Download the VirtualPC binary BSP and create a OSDesign by selecting the VirtualPC BSP
• Build the  Osdesign and create a image.
• Install the Virtual PC 2007 in your PC and configure it for download just like you did for emulator.
• Download the image to the VirtualPC using Platform builder.

http://blogs.msdn.com/b/mikehall/archive/2009/05/21/download-windows-embedded-ce-6-0-virtual-pc-binary-bsp.aspx

 

For more details on VirtualPC check out the following link

http://www.eminsenay.com/blog/?p=343

 

Good Luck.

 

--
Regards,
Prabu
http://prabukumar.wordpress.com/
www.e-consystems.com

Answer 7

Hi ilnak,

    I'm very interested in hearing more about your issue, did you solve your problem?

If so please share the solution with us and mark the right answers.If not please let me know and I will tray to help you find further solutions.

 

Have a nice day!

---

Brave Zhou [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 8

I get no "Catalog Items" view at the solution explorer....

Is this ok?

Answer 9

Go to View Menu -> Other Windows -> Select Catalog Items View.

But this is not an issue. How you are proceeding? are you using Device Emulator for ARM or Virtual PC suggested by Prabu?

Please answer to the question that we have asked. So that we can guide you easily.

---

Vinoth.R http://vinoth-vinothblog.blogspot.com http://www.e-consystems.com

Answer 10

I am using virtual PC. And currently I am building the OS. I have some issues, but it seems that I solved for the moment. I'll report back

thank you anyway though

Answer 11

yup. still getting the same error.

Error: Could not find file 'C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\oal.exe' on disk
nk.exe C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\oal.exe NK SHZ

I have a couple of things in mind to try. I'll give feedback as soon as I try them

Answer 12

hmm

No luck...

Guys I'm out of ideas... Any help would be gratly appreciated. Why  am I getting this error? Does anyone know?

Still, can I develop and "emulate" a program I made on arm architecture and then run it on x86, if the code is written in .NET?

 

regards

ilias

Answer 13

Please check your installed virtualPC BSP in the following location for the oal.exe file.

 

WINCE600\PLATFORM\VirtualPC\BIN\OAL\retail\oal.exe

 

If it is there then copy that exe to the release directory

WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\

 

Then try giving Build-->MakeRunTime Image.

 

And check whether it is making the NK.bin for the VirtualPC.

--
Regards,
Prabu
http://prabukumar.wordpress.com/
www.e-consystems.com

Answer 14

Hello, and sorry for not showing up for such a long time. I had extended holidays.

I'll try out what you suggest, Prabu, and I will report back on the progress.

ilias

Answer 15

How about this error:

Copying C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\oal.exe to C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\nk.exe for debugger

Error: Module nk.exe reqested kernel fixup and couldn't find required .rel file
Fatal error hit, exiting...

After copying the oal.exe file it asked for the kitl.dll file, which I copied from C:\WINCE600\PLATFORM\VirtualPC\BIN\KITL\retail folder

and then I got this error. Which .rel file is the compiler referring to?

 

ilias

Answer 16

Well in case the compiler is referring to the kitl.rel file, I thought that copying this file should the trick, but now I get I new error:

Error - cannot open input file C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\postproc\nlscfg.inf
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).

I wnat to proceed in parallel to this route so here's my other question. Could I develop an application for the arm architecture (so as to use the emulator) using the .NET platform and then install it on any other architecture like x86?

 

 

ilias

Answer 17

I found out that the nlscfg.inf file exists in the following directory:

C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\Wince600\VirtualPC_x86\OAK\files

but every time i clean the solution to make the runtime image, if it existed it will be deleted. So I clean the solution paste the file and after pressing Build>Make run-time image I get the following error:

makeimg: run command: fmerge -txt C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\postproc\nlssrc.txt C:\WINCE600\public\common\oak\files\locale.txt C:\WINCE600\OSDesigns\x86OSEmulation\x86OSEmulation\RelDir\VirtualPC_x86_Release\nlssrc.txt
fmerge for Windows CE (Release) (Built on Apr  5 2006 11:32:16)
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
x86OSEmulation - 2 error(s), 0 warning(s)

Answer 18

After creating new OSDesign based on Virtual PC did you builded using the Build-->Advanced build Menu-->Sysgen?

 

If yes then try the following options otherwise try the above mentioned command .

* Build-->Copy files to the Release Directory

* Build --> Make Runtime image

--
Regards,
Prabu
http://prabukumar.wordpress.com/
www.e-consystems.com

Answer 19

I am very close to quiting the procedure.... Nothing works, and there's no one to tell me that it works, or that he/she has tried it.

But how is it possible...? They made an emulator only for the arm architecture @#%$#$^@^#$^.

Anyway can I develop in .NET for arm, test in the emulator, and then run it on x86?

Answer 20

If you are developing application using ..netcf then it will run on all the CPUs.Only your compact framework libraries will be CPU dependent.

So you can develop application in ARM emulator.

--
Regards,
Prabu
http://prabukumar.wordpress.com/
www.e-consystems.com

Answer 21

ok thank you very much Prabu.

Answer 22

Hi buddies,

 

Thanks for your replies and thanks for share your experiences.

 

Have a great day!

 

 

---

Brave Zhou [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 23

Bravezhou. Where did you find the answer to my problem? Because I definitely can not see it.