Inside: SereneScreen Fan Forum - View Single Post

Dale · 09-17-2009, 10:01 AM

Originally posted by Jim Sachs:

I simply don't have a clue as to why it would be incompatible with the Windows screensaver routines on that machine. In order to diagnose it, the problem would have to occur on my machine while I'm using the debugger. The two problems with that are the fact that my machine doesn't crash, and his machine only experiences the problem when Windows attempts to use the screensaver system to launch it (so I assume it wouldn't happen if launched by a debugger).

You did notice that MA3 works correctly when the Screen Saver launches it (based on time). But the "miniature" version in the "monitor" is what causes the crash. (Display Properties is what is running).

09-17-2009, 10:01 AM	#31
Dale Banned Join Date: Jun 2005 Location: Western Missouri Posts: 960	Originally posted by Jim Sachs: I simply don't have a clue as to why it would be incompatible with the Windows screensaver routines on that machine. In order to diagnose it, the problem would have to occur on my machine while I'm using the debugger. The two problems with that are the fact that my machine doesn't crash, and his machine only experiences the problem when Windows attempts to use the screensaver system to launch it (so I assume it wouldn't happen if launched by a debugger). You did notice that MA3 works correctly when the Screen Saver launches it (based on time). But the "miniature" version in the "monitor" is what causes the crash. (Display Properties is what is running).