Start8 doesn't work (correctly) with Fences Pro

With Start8 (latest, test/locked version) and Fences Pro installed, there are no icons on the desktop at startup.  None at all, irrespective of Fences settings.  In fact, what I discovered is that Fences Pro doesn't actually even start, at least in terms of what the user sees (presumably the processes do).  Of course, when one sees a desktop devoid of all icons when there should be about thirty, it's not a small matter and I've just spent the past three hours figuring out - uninstalling, reinstalling, doing system restores and, of course, replicating to be certain - what Stardock should have noticed before ever releasing Start8. Shades of the "exclude from quick-hide" problem with Fences 2 (which is why I'm still using Fences Pro).  

Here's what I found:

1) I have to right-click to get icons showing on the desktop.  At that point, all icons show, irrespective of Fences settings, which means in effect, Fences hasn't started.

2) Double-clicking on the desktop then gets Fences going, hiding what is meant to be hidden and not hiding those that have been excluded.

I've sent a problem report, though I doubt that the log files are going to catch it (one is empty).   

 

 

5,069 views 6 replies
Reply #1 Top

Fences Pro is not compatible with Windows 8. The problem with it not starting until you right click on the desktop is exactly the problem it has on Win8 with or without Start 8.

Fences 2 is Windows 8 compatible.

BTW when you say latest / test of Start8 did you mean 1.03 or 1.09/1.1 beta?

Reply #2 Top

Well, considering that Start8 officially came out right around the same time that Fences 2 was announced, at least by email to subscribers, this makes your Stardock's failure to fix Fences 2 (yet!) all the more objectionable.  I know that I'm far from alone in finding the ability to hide/not hide icons central to use of Fences. To me, Fences 2 is not attractive without that central feature - and I feel ripped off having paid for a fundamentally unfinished program. 

As for Start8, I took what was generally available on the site a couple of days ago; i.e., I didn't go beta hunting.  And obviously I didn't realize - missed? - that you were pulling a double whammy on Fences Pro users with Start8.

Reply #3 Top

Quoting genegold, reply 2
Well, considering that Start8 officially came out right around the same time that Fences 2 was announced, at least by email to subscribers, this makes your Stardock's failure to fix Fences 2 (yet!) all the more objectionable.  I know that I'm far from alone in finding the ability to hide/not hide icons central to use of Fences. To me, Fences 2 is not attractive without that central feature - and I feel ripped off having paid for a fundamentally unfinished program. 

As for Start8, I took what was generally available on the site a couple of days ago; i.e., I didn't go beta hunting.  And obviously I didn't realize - missed? - that you were pulling a double whammy on Fences Pro users with Start8.
End of genegold's quote

I think you may have missed my point.

The problem with Fences Pro on Windows 8 is nothing to do with Start8.  Having Start8 installed will make no difference to the problem.  Here is a link to a thread from July where the non loading up problem is raised with Fences Pro : https://forums.wincustomize.com/428848

Microsoft made a change with Windows 8 that broke the ability for Fences Pro to load up at startup.  This change also impacts DeskScapes 3.  We filed a bug with Microsoft on this during the beta but they indicated it was an intentional design decision rather than a bug.

Fences Pro itself does not work correctly with Windows 8 due to this OS change.  Fences 2 changed how Fences loads up (along with other changes) in order to be compatible with Windows 8.

I am sorry if you are having problems with Fences 2 and all I can suggest is contacting support@stardock.com regarding that as I have no direct influence over Fences 2 development and am unaware of the plans for future updates.

Just to repeat, we are not breaking Fences Pro on Windows 8 with Start8 in order to cause people to buy Fences 2.  Fences Pro is broken without Start8 too.

Reply #4 Top

Quoting Neil, reply 3

Microsoft made a change with Windows 8 that broke the ability for Fences Pro to load up at startup.  This change also impacts DeskScapes 3.  We filed a bug with Microsoft on this during the beta but they indicated it was an intentional design decision rather than a bug.
End of Neil's quote

does this mean there is no chance of deskscapes running on windows 8? or will a new version be made to run on windows 8?

Reply #5 Top

Quoting JCR2323, reply 5



Quoting Neil Banfield,
reply 3

Microsoft made a change with Windows 8 that broke the ability for Fences Pro to load up at startup.  This change also impacts DeskScapes 3.  We filed a bug with Microsoft on this during the beta but they indicated it was an intentional design decision rather than a bug.



does this mean there is no chance of deskscapes running on windows 8? or will a new version be made to run on windows 8?
End of JCR2323's quote

Deskscapes 3 will never run on Windows 8, Deskscapes 4 will do so.

Here isa picture of Deskscapes 4 : https://forums.stardock.com/437936

Reply #6 Top

Thanks for the explanation, which as far as I know hasn't been conveyed to users (even this forum doesn't seem to have an email notification system - or if it does, I couldn't find it).  In any case, it's good to know the background (finally).  But no, I didn't miss your point.  In fact, it underlines mine: Stardock has a financial and moral responsibility to get Fences 2 in order.  The "exclude from hiding" bug is something that presumably should have been caught in testing, but at least responded to quickly when they heard about it.  And they did hear about it.  Check the thread about it not far down this forum's list and I know that at least one person filed a bug report back in October.  As someone very familiar with the way organizations work, Stardock appears from a distance to have serious management problems. Even gettng a response from tech support takes several days to a week or two - and often they aren't responsive, as if the person responding has forgotten to reread what the problem was.