gregorsamsa11

I have a WinPE 2.0 build that I've been testing on a variety of hardware. On a few specific machines, WinPE fails to boot with the following error messages (paraphrase): Corrupt or missing ataport.sys Corrupt or missing fltmgr.sys I do not think these files are actually corrupt or missing. I suspect that this may be caused by the use of some unsupported XP drivers in my build. The problem is that trial and error has shown that these drivers solve issues on other machines, so removing them is problematic. Does anyone have any insight into this issue, beyond "using XP drivers in Vista is bad news?" Thanks, David

The problem is that the default resolution is unsupported by this device (it only supports 640 x 480), but we don't want to force this resolution accross the board. Most of the systems where this package will be booted have much newer displays that support much higher resolutions. We're just going to live with the issue. I don't think there is a workable solution. Thank you for your help.

Thanks for the tip. Using the SetRes tool, I was able to set a resolution that was supported by the old display, and the display appeared to work. My conclusion is that WinPE is auto-detecting a resolution for the display that isn't actually supported. For reasons I needn't go into, SetRes is not a viable solution to this problem. We would really like WinPE to correctly auto-detect the settings for this display. Does anybody have any suggestions for making this happen? Does WinPE generate any diagnostics/logs that might be of use here? We have injected the drivers for the video adapter, and we've also confirmed that there are no drivers available for the monitor. As I mentioned above, full versions of XP and Vista correctly auto-detect the settings for this display. I'm at a loss for what else to try. We can live with this issue if necessary, and I suspect we'll have to, but I haven't given up all hope.

We have a WinPE-based application that needs to run accross a wide variety of hardware. One device that's giving us trouble is an old 7" monochrome monitor. This device works just fine in full version of XP and Vista, but the display is garbled in WinPE 2.0. We've injected the video card driver into the image. We've also checked the XP and Vista systems where it is working for monitor drivers. These systems are using "Microsoft Default Monitor Driver." The point of the story is that we suspect that WinPE is setting the refresh rate and/or resolution to something incompatible with the display. Is it possible to manually specify these settings?

That clears it up a bit. Thanks for the help. I think my main problem is that I don't have a list of the devices that need to be supported, so I'll tackle it from that end. Once I have that, I can hunt down the Vista drivers I need. Hopefully they all exist. Thanks again.

My WinPE 2.0 image seems to default to an 800x600 display resolution. I read that it should default to the highest supported resolution, so I assumed that I needed to add a graphics driver for my hardware. I did that, but it still defaults to 800x600. Is there any way to attempt to force a new resolution from the command line?

We currently have a small application that runs from WinPE 1.2 bootable media. I know that there are a number of 3rd party drivers included in our WinPE 1.2 image, but there is no documentation about what they are and where to find them. Now that I'm tasked with integrating the application into new WinPE 2.0 bootable media, I need to discover all of these 3rd party driver files and add them to the WinPE 2.0 image in order to ensure this application works on all of the necessary hardware. Since there is no documentation about these drivers, I'm not sure how to do this, or if it's even possible. Even if I can't firmly identify all of the 3rd party drivers, I can settle for injecting all drivers from our WinPE 1.2 image into the new 2.0 image (if that makes sense). I started by diff'ing between our WinPE 1.2 image and a standard 1.2 image built by mkimg. This turned up a lot of .inf, .sys, and .dll files, as well as a few others. I think that .inf files are instructions for driver setup, and I know what .dll files are. What are .sys files? Furthermore, how can I determine which files in addition to the .inf are necessary for injecting the driver into the WinPE image? In other words, how can I discover the groups of files that are associated with one particular driver? I think I've identified some .inf files that represent 3rd party drivers that I need, but when I try to inject them using $peimg /inf="" I get an uninformative error (just an error code*, which I've so far been unable to find a translation for). I'm assuming that during the injection process, peimg failed to find the actual drivers, but this is not confirmed. Any advice would be appreciated. If there is anything unclear about the situation, please ask. I wrote this in a hurry. Thanks, gregor * The error is "PEIMG failed to complete the operation with status code 0x80070002." If anyone knows where I can find a table to translate PEIMG error codes, that would be helpful.

I have an existing HTML application that uses JavaScript, so I was hoping to avoid a rewrite in VBscript. I've got it running, so I'm happy.

Adding in the XML package did the trick. I'm using WinPE 2.1 as it turns out, so the 3.0 issue is not a problem for me. Your efforts are much appreciated. Thanks, mate.

I should clarify the situation. I created a WinPE 2.0 image which includes the HTA-suppport and Scripting packages. I also wrote the following "hello,world" hta/javascript program and added it to the image. When I boot the image and run the hta file, it is apparent that neither of the two JavaScript statements are executed. I did find one obscure post somewhere claiming that JavaScript is supported, but nothing else I've read or done confirms that. <html><head> <title>My application</title><hta:application id="MyApp" applicationName="My application" > </head><body> <script language = JavaScript> <!-- document.write("Hello, World"); alert("Hello, World"); //--> </script> </body> </html>

I have an HTA application originally written for WinPE 1.2 using JavaScript. I'd like to port it to WinPE 2.0, but there seems to be no JavaScript support. Googling has turned up no information on the subject, so I was hoping someone could enlighten me. Is there any reasonable way to get JavaScript support with WinPE 2.0? Thanks!