david_b

Hi all -
I'm getting a consistent failure in any of the print DTM tests that use the "Add NullPortMonitor and switch" task as part of the job, but particularly in the Devmode Corruptor test. I haven't been able to determine if there are any devmode handling deficiencies since none of the actual devmode corruption can run without this task succeeding.

I've seen this failure discussed elsewhere here, but supposedly the problem was due to an empty FriendlyName parameter for DevModeCorrruptW.exe when the test is run outside a submission. In my case, I'm seeing this happen within a submission.

Thanks in advance for any help or insights.

Regards
David

Klaus

Hi,
I have the same problem. If I run all tests, DevModeCorr or DrvStress can't add the NullPortMonitor. The test hang up. After using the command line instruction 'net stop spooler' the next test will start.

If I use only a single test, both tests run until the end and pass. The port has to be set to LPT1: and the printer must have the status ready. If the test hang up, no port is selected.

I believe that there is a bug in the DTM tests. The question is now: what can we do to run all tests 'in a single run'. How can the port set to LPT1: if there is nothing selected?

On the other hand there are different bugs in Vista. The test stops at simple API function calls like GetPrinter(), GetDriver() a.s.o.

Klaus