CE6的Windows CE 5打印机驱动程序导致系统锁定 [英] Windows CE 5 printer driver to CE6 causes system to lockup

问题描述

您好，

我们根据windows ce5.0的示例pcl驱动程序开发了一个打印机驱动程序。  这个驱动程序工作正常，我们可以从wordpad等打印。然后我们决定迁移到ce6.0。  我们在32位机器上安装了vs2005，获得了所有必需的
包，并使用之前的驱动程序构建了我们的图像。  稍微摆弄我们再次使用它，显示为有效的打印机并可以与打印机通信。  我们没有问题向打印机发送基本命令，但如果我们尝试
使用gdi调用打印图像（所有打印作业都是图像）打印机接收图像，将其打印出来，然后系统锁定。

We developed a printer driver based on the example pcl driver for windows ce5.0.  This driver works fine, we can print from wordpad etc.  We then decided to migrate to ce6.0.  We installed vs2005 on a 32bit machine, got all of the required packages, and built our image with our previous driver included.  With a little fiddling we got it to work again, shows up as a valid printer and can talk to the printer.  We have no problem sending basic commands to the printer, but if we try to print an image (all print jobs are images here) using the gdi calls the printer receives the image, prints it out great, then the system locks up.

有时ce6设备会自动重启，通常是从wordpad打印时。  作为打印后的wordpad中的示例，现在打印对话框但不会消失。  如果我们从我们的应用程序打印（这使gdi调用创建
图像），它似乎永远不会重新启动。  我们试图在ce6上研究对gdi调用的更改，但一无所获。

Occasionally the ce6 device will reboot itself, usually when printing from wordpad.  As an example in wordpad after hitting print, the now printing dialog appears but never disappears.  If we print from our app (which makes gdi calls to create the images) it never seems to reboot.  We have attempted to research changes to the gdi calls on ce6 but found nothing.

任何帮助都会非常感激，因为这个问题已经让我们持续了近一个星期了。  如果重要，我们正在使用ebox4300，但这个问题也发生在装有wince6.0的手持式Symbol设备上，所以我们不相信它是
是一个OSImage问题。

Any help would be greatly appreciate as this problem has been holding us up for nearly a week now.  If it matters, we are using an ebox4300 but this issue also occurs on a handheld Symbol device with wince6.0 installed on it so we do not believe it to be an OSImage issue.

最好的问候，

Sean

推荐答案

答案将涉及使用内核调试器来确定图像决定重新启动的原因。 在第一次猜测时，我怀疑你的司机使用了RAM，但这是一个非常疯狂的猜测。 使用DEBUG配置为某些目标硬件
构建操作系统映像。 将Platform Builder中的内核调试器连接到设备，看看会发生什么。 您可以观看在打印过程中和之后生成的调试消息。

The answer is going to involve using the kernel debugger to identify why the image is deciding to reboot itself.  At a first guess, I'd suspect RAM usage by your driver, but that's a pretty wild guess.  Build the OS image for some target hardware that you have using the DEBUG configuration.  Connect the kernel debugger in Platform Builder to the device and see what happens.  You can watch the debug messages that are generated during and after your print process.

Paul T。

这篇关于CE6的Windows CE 5打印机驱动程序导致系统锁定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！