如何将 NULL 设备添加到 Windows XP Embedded？
Windows XP Embedded 缺少 NULL 或“NUL”设备。 一方面，Visual Studio 似乎需要它，并且尝试构建项目会因 PRJ0015 错误而中止。
有人知道如何配置 XPe 映像以包含对 NUL 设备的支持吗？
Windows XP Embedded is missing the NULL or "NUL" device. For one thing, Visual Studio seems to require it and trying to build a project aborts with a PRJ0015 error.
Anyone know how to configure an XPe image to include support for the NUL device?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
“空设备驱动程序”在 XPe Target Designer 中可用，但通常是隐藏的。 显然，每个组件都有一个可见性级别，如果它低于目标设计器选项（工具->选项）中设置的可见性级别，则它会被隐藏。 空设备驱动程序的级别为 200，因此我将级别设置为 100，并且可以看到它并安装它。
"Null Device Driver" is available in the XPe Target Designer, but it's normally hidden. Apparently each component has a visibility level, and if it's lower than that set in the Target Designer options (Tools->Options), it's hidden. Null Device Driver is at level 200, so I set the level to 100 and could see it and install it.
还有另一种重要情况，您需要 NUL 设备：如果您正在安装部分或全部 Windows 的 Cygwin UNIX 解决方案。 特别是，如果你正在做类似的事情，哦，我不知道，选择一个完全随机的例子，试图在该死的东西上放置一个 SSH 服务器，这样你就可以，只是为了好玩，比如说，登录并维护它。
没错，Cygwin 实际上将其 UNIX /dev/null 设备映射到 Windows NUL 设备。 你知道，为了最大程度的兼容性。 以防万一平台特定的“立即将数据扔进厕所并抹掉它，再也不会出现，直到宇宙热死”的实现恰好是新颖和创新的。
虽然 cygwin 将在没有 NUL 可用的情况下安装，但实际上它不会真正享受典型的工作日。 当您第一次尝试启动 bash shell 时，这一点最为明显，并注意到大量有关 /dev/null 的错误消息，导致没有此类文件或目录错误。 有人推测该设备实际上可能只是一个 NTFS 链路，但谁知道呢。
无论如何，修复方法是添加“空设备驱动程序”组件，该组件位于“软件”->“空设备驱动程序”下。 系统-> 其他的，一个令人惊讶的小类别，其中还包含一些有用的组件，如 Internet 检查器、调度服务命令行实用程序、1394 内核调试器支持库、对 Microsoft Bob 的 EBCDIC 支持、Zork 的一些作弊代码以及表示“( A）bort，（R）尝试，（I）忽略，（F）ail？” 布偶瑞典语（“(B)ork、b(o)rk、bo(r)k、bor(k)？”）
希望这有帮助，
马特“断点”赫克
There's another important situation where you're going to want the NUL device: if you're installing some or all of the Cygwin UNIX solutions for Windows. In particular, if you're doing something like, oh, I don't know, to pick a completely random example, trying to put an SSH server on the damned thing so you can, just on a lark, say, log in and maintain it.
That's right-- Cygwin actually maps its UNIX /dev/null device to the Windows NUL device. You know, for maximum compatibility. Just in case the platform-specific implementation of IMMEDIATELY THROWING DATA INTO THE TOILET AND OBLITERATING IT, NEVER TO BE SEEN AGAIN, UNTIL THE HEAT DEATH OF THE UNIVERSE, happened to be novel and innovative.
While cygwin will INSTALL without NUL available, it will not, in fact, actually enjoy a typical work day. This is most evident the first time you try to launch a bash shell, and notice a slew of error messages about /dev/null resulting in no such file or directory errors. One presumes the device is perhaps actually just an NTFS link, but who knows.
In any case, the fix is to add the "Null Device Driver" component, helpfully located under Software -> System -> Other, a surprisingly small category which also contains such useful components as Internet Checkers, the Schedule Service Command Line Utility, the 1394 Kernel Debugger Support Library, EBCDIC support for Microsoft Bob, some cheat codes for Zork, and the code pages to say "(A)bort, (R)etry, (I)gnore, (F)ail?" in Muppet Swedish ("(B)ork, b(o)rk, bo(r)k, bor(k)?")
Hope this helps,
Matt "Breakpoint" Heck
在 XP Embedded 上运行 Visual Studio 本身似乎不受支持。 您应该构建一个完整的操作系统，然后将您的应用程序部署到嵌入式 XP。
Running Visual Studio itself on XP Embedded doesn't seem like it'd be supported. You should build on a full OS and then just deploy your application to XP embedded.