Re: sdimgr and WinPE PnP conflict
- From: "JS" <nospam@xxxxxxxxxxx>
- Date: Tue, 26 Sep 2006 17:51:37 -0700
I think I have a solution.
At first I thought it might be related to AutoRun, but that had no effect.
What worked was to use Windows XP SP2 as the basis of the WinPE
boot disk. (I had been using Windows Server 2003 SP1).
To clarify, when creating a WinPE boot disk with the WinPE 2005 toolkit,
you can use either Windows XP SP2 or Windows Server 2003.
If you use Windows Server 2003, there is a conflict with SDIMgr
and SDIMgr is unable to write to the embedded device.
"JS" <nospam@xxxxxxxxxxx> wrote in message
news:unrMFmQ4GHA.508@xxxxxxxxxxxxxxxxxxxxxxx
Here is a weird issue:
I have a bootable WinPE 2005 disk with a SDI image of my embedded device.
I use SDIMGR.WSF to copy the XP Embedded image to the embedded device.
If the WinPE 2005 disk is booted with PnP detection disabled,
the SDI write is successful.
If the WinPE 2005 disk is booted with PnP detection enabled,
the the SDI write fails with the following error:
Error -2147467259 (0x80004005) in "SDIAUT.SDIFile.1": The device is not
ready.
To enable or disable PNP, set DoPNP=Yes or No in the winbom.ini file as
appropriate:
For example:
[WinPE.PNP]
DoPNP=No
Does anyone have any ideas?
.
- References:
- sdimgr and WinPE PnP conflict
- From: JS
- sdimgr and WinPE PnP conflict
- Prev by Date: Re: USB Keyboard and Mouse with Minlogon
- Next by Date: Device Driver Developmetn tools for xpe
- Previous by thread: sdimgr and WinPE PnP conflict
- Next by thread: XPE troubles with Time Service NTP
- Index(es):
Relevant Pages
|
