You’ll see that the program recollects information about your devices, and creates a new file on the same folder called “ devices.pmq” containing all that data. Since I’m using virtual machines in the same physical server, I’m going to collect hardware data in the same machine where I’m going to build the target image.ġ.1 Open a cmd and focus on “ C:\Program Files\Windows Embedded\utilities”. With the information gathered here, the corresponding drivers will be added to the image. exe file that compiles all of the hardware necessary information to be included on the image you are building. This step is done with Target Analyzer, that is just an. Get hardware information from your target And again, as I mentioned before, this deployment is oriented to Embedded images booting on diskless devices, so there will be steps that are not necessary if you are not looking for a remote boot environment with Windows Embedded Standard 2009 images. The process it’s practically the same that we executed on XP Embedded ( Post I, Post II and Post III). Windows Embedded Standard 2009 Step-by-Step Deployment – Part IIIĪfter reviewing Post I we’ve set our environment to start building the images. Windows Embedded Standard 2009 Step-by-Step Deployment – Part I
0 Comments
Leave a Reply. |