Stardock will be closed for the week starting on Monday, June 29th and we will be returning on Monday, July 6th. We will be monitoring support tickets and forums during this time but expect delays in responses during this time.
The beta causes the same crashes as before. No change. I've removed fences for now and I hope in the months ahead that this can be fixed. But for now, I need to do actual work and can't have a buggy program installed. Donn
It's been a few days since I changed the startup command for Fences, so I thought that I should report back. My suggestion at the time was to launch Fences from the task manager and not the "startup" folder. Simply put, don't do it. While starting up Fences from the Task Manager does stop the crashing, Fences gets all confused. It does not know that it was auto started and pops up the configuration screen every time you boot. And, worse y
I'm using Windows 7 x64 Crucial M4 256Gb SSD 8 HHD of various sizes 8 GB DDR3 Water Cooled Crashing the windows explorer (i.e. the desktop) has been a problem since Fences 1.0 and, in fact, the problem existed in other Stardoc apps before then too. The old version would only crash once on every boot up. While annoying, I could live with this. The new version, however, crashes multiple time
I can confirm that this problem has existed for quite some time. My system has three monitors. Docks on either the left or right monitor show their separators on the center (main) monitor. They are in the correct position, just the wrong monitor. This is a programming error even if it might somehow relate to your video driver or motherboard or cpu. As a programmer myself I do not believe that this type of error is overly complex. It might, however, be hard