I installed Fusion Display on my Vista computer yesterday and it worked fine and I set up my wallpaper over my two displays, very happy

Today I get “Display Fusion stopped working” error message.

I have noticed they have been a post before about this http://www.binaryfortress.com/Forum/index.php?topic=277.0 but this has not worked for me.

I have downloaded Microsoft .net 2, but it will not install because it’s not for Vista?

Can anyone help me?

I have the same problem. It works like a charm most of the time, but now and again it stops working when I boot up, and I'm running Vista Ultimate on a laptop.

One of the things I think is common with all of my crashes is that it only stops working during times when I don't have an immediate network connection. For example, if I turn my laptop on at work after running it at home, it takes a few minutes for my wireless card to switch to the new network and during that time it stops working. However, when I connect to the network and restart Display Fusion, no issues.

Maybe others can confirm that it only crashes when no connectivity is present and that might help identify the issue.

It does seem to be a bit hit and miss.

Display fusion has not worked since the day I have posted this, but worked today for the first time since??

I have Vista Ultimate machine with a wired network.

I have recommended the software to a mate, and he has had no problems. He is running Vista Home.

Maybe it's an Ultimate bug?

I too have the same problem which appears to be caused by the lack of internet connection at startup. However, the program still seems to work OK but just with the annoying message at startup. Sometimes a message says 'Cannot resolve the name BinaryFortress.com' and then Windows says it has stopped working and sometimes it's just the Windows message.

Jon, This could be due to the fact that you code sign the binary. Check out this hotfix article from microsoft: http://support.microsoft.com/kb/936707. In essence it has to do with the fact that on application startup, whenever the .Net Framework encounters a code signed binary it tries to connect to the certificate issuer of the code signing certificate to download their latest Certificate Revocation List. Once it's downloaded the CRL it checks to see if the certificate has been revoked and if it hasn't everything continues. If however you have an active/semi-alive network connection but the internet connection isn't there yet the .Net framework will wait up to 15 seconds while it tries to download the CRL, after that it gives up and executes the binary without checking the authenticode signature. If you have no network connection, no authentication takes place. This problem is particularly noticable if you're using code-signed binaries in a .Net Windows Service OnStart() method call, as a windows service is only given 30 seconds to start before the service control manager gives up on it, basically DOS'ing your Service.

The hotfix article basically states that as of .Net 3.0 (or with a 2.0 hotfix) you can set a value in the app.config file to disable the authenticode check, which basically negates the point of code-signing your binary, but in my opinion there isn't really much of an option given this behaviour. The worst part is that if clients of your software figure out that on startup your application tries to make web requests to a foreign server on the internet, before investigating the IP address it's hitting, they'll often simply assume your software is "phoning home" and tell everyone it's spyware. Quite the opposite effect it's supposed to have!

Or it could just be the hit you make against your own server periodically to check for updates...

Josh.