Microsoft KB Archive/260537

= How To Build a Windows CE OS Image with Product Ethernet Included =

Article ID: 260537

Article Last Modified on 3/9/2005

-

APPLIES TO


 * Microsoft Windows CE Platform Builder 2.11
 * Microsoft Windows CE Platform Builder 2.12

-



This article was previously published under Q260537





IN THIS TASK
SUMMARY
 * Building the Windows CE OS Image

REFERENCES



SUMMARY
In some Windows CE configurations you must have two Ethernet connections, one for download and debug and another connection for accessing the Web or other application-level usage. The application-level usage could be another tool such as Microsoft's Visual Studio remote tools that are used during software development. The basic difference between these two Ethernet connections is that one is employed before the Windows CE OS is loaded and running, and the other one is used after the Windows CE OS is loaded. The latter is called a product Ethernet because unlike the former connection, it is part of the Windows CE operating system communications stack.

back to the top

Building the Windows CE OS Image
The following procedures assume that you have a CEPC with one parallel connection and one Ethernet connection. The procedure assumes that a parallel connection is available for download of the Windows CE OS image. You can do this through another Ethernet connection as well (which is faster, but may not be available on all devices). These procedures show how to create an OS image with built-in product Ethernet and how to test the image:  Use the parallel port for download (that is, &quot;cesh -p cepc nk.bin&quot; on the Microsoft Windows NT side, and use &quot;loadcepc /p nk.bin&quot; on the CEPC side). Leave the Ethernet connection for network commands.  Get the I/O base address and Interrupt number for your CEPC Ethernet card and put that information in the Platform.reg file in your release directory. For example: [HKEY_LOCAL_MACHINE\Comm\NE20001\Parms] &quot;BusNumber&quot;=dword:0 &quot;BusType&quot;=dword:1 &quot;InterruptNumber&quot;=dword:0B          ; change this &quot;IoBaseAddress&quot;=dword:240           ; change this

NOTE: This specific example is for the NE2000 net card in an ISA bus. Yours may be different. Locate the right area in the Platform.reg file for your information and insert it there.  In your environment (Build window) run this command:

set CEPC_NE2000_ISA=1

This value should match your actual network card. Refer to the &quot;cepc_ne*&quot; topic in Platform Builder Books Online to see the environment macros. Run a makeimg to build the Win CE with the changes in effect. Do not perform a full build, because the release dir is re-created and all your changes will be cleared.  On your CEPC, after you download the OS image through the parallel port, open Control Panel, and then click the Communications icon. Give your computer a unique name. Do not use the default &quot;wince&quot;. You must change this to a unique name. You can also add this in the Release\Project.reg file as: [HKEY_LOCAL_MACHINE\Ident] ; fm  &quot;Name&quot;=&quot;LOC_IDENT_NAME&quot; ; fm  &quot;Desc&quot;=&quot;LOC_IDENT_DESC&quot; &quot;Name&quot;=&quot;fm_WinCE&quot; &quot;OrigName&quot;=&quot;WinCE&quot; Here you add the OrigName to show the system that fm_WinCE is different from the default name and is unique.  One way to test the Ethernet product is to use net commands. To do this, create a share on your NTWS. You will map this share to your CEPC file system and it then use the share as a local dir on the CEPC.</li> Open a command window (Cmd.exe) on your CEPC. You can now use the net commands as follows:</li></ol>

-> net view \\yourNTName            ; This shows the shares you have. -> net use * \\yourNTName\sharename ; This maps your Windows NT share to                                      ; the \network dir on your CEPCdir on                                      ; your CEPC. ; It will be like a regular ; subdir on your \network dir on cepc.

-> mapped to &quot;sharename on yourNTName&quot;  ; This is the form of the remote ; share mapped to your \network ; dir on CEPC. -> ?                                ; Displays all the commands available ; from your CEPC command window. -> dir                             ; Shows you files in your current dir

You can now treat the remote share (mounted in your \network dir in the CEPC file sys now as &quot;x on y&quot;) as a regular sub directory. You can copy files in and out of it as if it were local. Of course, any file you now transfer to or from this sub directory goes to your NTWS share.

For example: copy \windows\test.txt \network\fm-temp on farjam1\myfile.txt This copies the Test.txt file to your Windows NT share fm-temp under the name myfile.txt.

back to the top

<div class="references_section">