Regrettably, my Software -> System -> Other tree does not contain "Null
Device Driver", which probably explains why a filter search for
NULL.SYS fails, as does any kind of search for LEGACY_NULL. My Other
tree has 1394 Kernel Debugger Support, Files and Settings Transfer
Wizard, five Internet games, Schedule Service Command Line Utility and
Search Tools. No Null Device Driver. My WinXPe distribution is SP1.
What might explain this strange absence? Thanks for your time.
Martin Grossen, eMVP [AVNET Silica] wrote:
Hi Frank
Include the Null Device Driver into your build.
Software -> System -> Other -> Null Device Driver
--
Martin Grossen, eMVP
AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe
Your competent partner for Microsoft Embedded licencing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No, I have not, and thanks very much for the reference. I have
recently
discovered that Apache web services is complaining about the absence
of
device NUL under my particular build of WinXPe. That is apparently
why
the web services server will not start. To test, "copy license.txt
nul"
fails with "file not found". But "copy license.txt foo" copies to
file
"foo" just fine. Any way to convince web services server to use
something other than NUL?
Martin Grossen, eMVP [AVNET Silica] wrote:
Have you checked out the Apache Component on
www.xpefiles.com ?
--
Martin Grossen, eMVP
AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe
Your competent partner for Microsoft Embedded licencing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Installed Apache Webservices but will not start, no message, no
pop-up.
IIS not at this time part of WinXPe component list. Can anyone
comment
on which components are necessary for Apache Webservices to
function
with WinXPe? Thanks.