What is the blue screen code you're getting? Are there any errors in the event logs?

It seems a bit odd that any virtualized app would cause a blue screen.

On Wed, 16 Jan 2013 14:56:02 GMT, zeevromm
<zeevromm@no-mx.forums.novell.com> wrote:

>
>What is the blue screen code you're getting? Are there any errors in
>the event logs?
>
>It seems a bit odd that any virtualized app would cause a blue screen.

But I can make it happen without fail.

Found this in the event log:
The computer has rebooted from a bugcheck. The bugcheck was:
0x00000050 (0xfffff900c3200000, 0x0000000000000000,
0xfffff9600025e328, 0x0000000000000002).

I created a debug version of the app and found this in one of the
logs:
0x0B74, 0xB875A:ERROR: 0xD000003A, Unable to open file the startup
module: \DEVICE\HARDDISKVOLUME2\Program Files (x86)\Tracker
Software\PDF-XChange Lite 4\pdfSaver4l.exe.

That is the PDF driver we are using. The driver works great on both
XP and Win7. And it works fine with the application on XP. But if I
try to print using the application as a virtual app on Win7, a blue
screen is guaranteed.

By the way it references "win32k.sys" and
PAGE_FAULT_IN_NON_PAGED_AREA.

Ken

On Thu, 17 Jan 2013 16:50:19 GMT, KeN Etter
<ketter@no-mx.forums.novell.com> wrote:

>By the way it references "win32k.sys" and
>PAGE_FAULT_IN_NON_PAGED_AREA.

I tried including the PDF driver in the snapshot of the app. No blue
screen, but I did get a slew of other errors. If no one has any
suggestions, I may just open an SR with Novell.

Have you tried setting DEP compatibility, run child processes as user, or emulate elevated priveledges?

On Thu, 17 Jan 2013 22:26:02 GMT, rroncme
<rroncme@no-mx.forums.novell.com> wrote:

>
>Have you tried setting DEP compatibility, run child processes as user,
>or emulate elevated priveledges?

Just checked all three of those options. No change. Still get a blue
screen. Guess I need to open an SR and see if Novell can shed any
light on the problem.

Ken

This issue was reproducible in-house, thankfully. A case was filed with Spoon; we'll update the forum with the resolution if and when we get it.

On Thu, 24 Jan 2013 17:46:02 GMT, zeevromm
<zeevromm@no-mx.forums.novell.com> wrote:

>
>This issue was reproducible in-house, thankfully. A case was filed with
>Spoon; we'll update the forum with the resolution if and when we get it.

Hopefully "when", not "if". :-) Novell Tech Support has been taking
good care of me on this issue.

Ken