Hello
I have Serial Port Device (PCI) which its driver is using the windows inbox driver (I just have an INF).
Now it is working fine on Regular Windows 10 (10240, 10586, and 14393)
But when I tried it on Windows PE, it seem like Windows does not load or allocated COM port number on Windows load.
Only when I disable and enable the driver then I got a COM Port allocated.
I?m adding the driver using DISM /add-driver to the PE image.
Furthermore it seem like Windows PE does not like any serial port, even the inbox or the serial port expose using Virtualbox.
Any idea why Windows PE is behaving differently? Do I miss some step in the image creation?
Thank in advance.
Win pe is not a general purpose is, it only loads the minimum set of drivers to boot strap machine os setup. What bugger problem are you trying to solbe by loading the serial driver?
Get Outlook for Androidhttps:
On Thu, Aug 4, 2016 at 9:31 AM -0700, “xxxxx@gmail.com” > wrote:
Hello
I have Serial Port Device (PCI) which its driver is using the windows inbox driver (I just have an INF).
Now it is working fine on Regular Windows 10 (10240, 10586, and 14393)
But when I tried it on Windows PE, it seem like Windows does not load or allocated COM port number on Windows load.
Only when I disable and enable the driver then I got a COM Port allocated.
I?m adding the driver using DISM /add-driver to the PE image.
Furthermore it seem like Windows PE does not like any serial port, even the inbox or the serial port expose using Virtualbox.
Any idea why Windows PE is behaving differently? Do I miss some step in the image creation?
Thank in advance.
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:></https:>
I have recovery usecase when we want to us our serial port of the device.
this is why we would like to use Widows PE