R
Roger Levy
I am brand new to the Windows embedded world but I have an eval copy of
XPe/SP1. Eventually, I want to boot 50 or so cPCI PCs with identical target
images but each one should be parameterized differently. Since individual boot
parameters can be set for each target in the spreadsheet provided by the remote
boot manager, I was hoping that I could define my own parameters and have the
component(s) I write recover them. However I could find essentially no
discussion of boot parameters in the documentation and no answer to whether I
can define and recover application specific boot parameters.
My second question relates to the tutorial Hello World application. I followed
the tutorial exactly and built this target. I decided to go one step further
and try and download it to a PXE enabled PC via remote boot manager. I used a
protocol analyzer to trace the messages between server and target. The target
did not boot up and it displayed a message saying that its ramdisk was missing
some components. My trace showed that the file BOOTFONT.BIN was requested by
the target but was not available on the server. Why did the target designer
allow me to build without errors an image that was incomplete and could not be
downloaded? What steps that are apparently missing from the tutorial are needed
to guarantee a complete image?
Roger Levy
XPe/SP1. Eventually, I want to boot 50 or so cPCI PCs with identical target
images but each one should be parameterized differently. Since individual boot
parameters can be set for each target in the spreadsheet provided by the remote
boot manager, I was hoping that I could define my own parameters and have the
component(s) I write recover them. However I could find essentially no
discussion of boot parameters in the documentation and no answer to whether I
can define and recover application specific boot parameters.
My second question relates to the tutorial Hello World application. I followed
the tutorial exactly and built this target. I decided to go one step further
and try and download it to a PXE enabled PC via remote boot manager. I used a
protocol analyzer to trace the messages between server and target. The target
did not boot up and it displayed a message saying that its ramdisk was missing
some components. My trace showed that the file BOOTFONT.BIN was requested by
the target but was not available on the server. Why did the target designer
allow me to build without errors an image that was incomplete and could not be
downloaded? What steps that are apparently missing from the tutorial are needed
to guarantee a complete image?
Roger Levy