57 replies to this topic

[archer1960]

It can't be made as a command line option without introducing explicit code for splash screens, as the current one is a no-code built in utility of the WPF Framework. Introducing new code can then introduce other bugs. So it would be best to find the root cause of your problem instead of having to introduce these workarounds for a problem that exists for only one user out of thousands.

Hmm, that doesn't quite make sense, because one of your devs had no trouble making a package with no splash screen for me to test. Or is the splash screen a build-time option/setting?

[archer1960]

I'll be glad to continue collecting data to figure out what might be causing this, but so far, nothing appears to be out or the ordinary. Have you looked at the crash dump file to see if it holds any clues?

[Isbeorn]

It was me who gave you that version. And it is just a flag in the build where the framework will generate the splash screen or will not generate it. There is no explicit code.

[archer1960]

It was me who gave you that version. And it is just a flag in the build where the framework will generate the splash screen or will not generate it. There is no explicit code.

Ok, thanks for clarifying. I've done quite a bit of coding over the years, but never bothered with a splash screen, so I wasn't sure how they were done. I would still like to figure out if there is something in my system that is causing the issue, that can be fixed.

[archer1960]

It can't be made as a command line option without introducing explicit code for splash screens, as the current one is a no-code built in utility of the WPF Framework. Introducing new code can then introduce other bugs. So it would be best to find the root cause of your problem instead of having to introduce these workarounds for a problem that exists for only one user out of thousands.

Do you know if there is a way of testing my WPF installation? I ran dxDiag to test my DirectX installation, and it turned up nothing unusual.

[mjanzou]

Did you ever identify what HW video device and driver version/provider your system is using?
Perhaps the pc manufacturer has an updated bios and/or video driver available?

[archer1960]

Did you ever identify what HW video device and driver version/provider your system is using?
Perhaps the pc manufacturer has an updated bios and/or video driver available?

I did, and the drivers are fully up to date. It's the Intel built-in video driver.

[BlueGrass]

Archer, 

 

 I don't see anywhere in the posts that you tried running your system, I assume a mini-pc type?, just by itself with no other devices plugged in other than the necessary RDP connection. I'd try this just to make sure you don't have an external device problem causing this failure. I also don't see that you've done any checking on the OS drive such as a check disk to see if there is any file corruption? Just a few thoughts ...