Re: Windows 8 Pro MCE x64
DisplayFusion Beta 11
Classic Shell Classic Start /Menu 3.6.8

Immediately upon installation of Beta 11 Classic Start / Menu failed to display on the DF Taskbar. Failed on restart. DF Settings indicates that Classic Shell is 'detected'.

As soon as I reverted to Beta 10, the Classic Start / Menu was restored and functions normally.

Good luck guys!

Keith: thanks for checking this out. I was going to re-download Beta 11 and see if installing the new exe made a difference (it's been known to happen!) — but see 11 has been withdrawn for other reasons, so I'll wait for Beta 12 next week and get back to you then.

All good wishes ~ Hans-Peter

Keith — the problem persists on my system in the just-released Beta 12. Again 'Settings' shows that Classic Menu is detected but no button is displayed on the DF Taskbar.

Two thoughts: Because I have reverted again to Beta 10 and the Classic Menu Button immediately displays correctly on the DF Taskbar, it stands to reason that some code has changed in the new betas that now renders my setup incompatible with DF.

1) Perhaps the non-standard name for the image path of the custom button image I am using?

%SystemDrive%\Program Files\Classic Shell\Skins\Start_Button.png

or

2) Could this problem be an artifact of using this non-standard 'Skin Pack' for Classic Menu?

http://winaero.com/blog/introducing-winaeros-exclusive-special-skin-pack-for-classic-shell/

With more time tomorrow I may try changing back to a default Skin but I no longer remember the default name / path of the image in a fresh installation. If you can remind me I'll try that too.

Thanks!

Keith: Thank you for your prompt response and trouble-shooting instructions.

It's the custom button!

On two Windows 8 machines the native 'Aero Button' displays on the DF Taskbar with Beta 12. A custom button fails.

Something must have changed since Beta 10, as the same custom button on both systems displayed correctly on that version. I have attached the button PNG file in case you would like to test it and have the time.

All good wishes ~ Hans-Peter

Keith: Many thanks for looking deeper into this problem.

First, to answer your immediate questions: I am running Windows 8 default theme but with my own Desktop backgrounds, one image for the main monitor in landscape mode and another image for the secondary monitor in portrait. However, please see below for a new piece of information. And, no I'm not running Windows Blinds 8 (I've read their forum …!).

I am attaching the debug log, as you instructed me earlier. At 05:42 pm it records a start with the native Classic Menu 'Aero Button' button that displays correctly on the DisplayFusion Taskbar. Then at 05:44 and 05:48 pm it records starts with my custom button ["C:\Program Files\Classic Shell\Skins\WinAeroButton.png"] that fails to display at all.

BUT, during this testing, I noticed an additional symptom I should have reported to you earlier and which may make the situation clear to you: with the custom button selected in Classic Menu, DisplayFusion also fails to display the seven shortcuts I have specified for the DF taskbar. Once I revert to the native Aero Button and reload DisplayFusion, those seven shortcuts display again normally, along with the Aero Button. Up to Beta 10 these shortcuts also always displayed correctly along with the custom Classic Menu custom button.

Very grateful for you patience and persistence!

Hans-Peter

Twice interesting — because the problem is occurring on two Windows 8 Pro systems on separatemachines with rather different hardware! [x9650 versus mildly overclocked i7 2700K + Radeon Silent 6600 versus Radeon Silent 4800].

However, they are setup fundamentally the same and are running almost all the same software.

Classic Shell settings XML file and DF settings reg file attached as requested.

Keith, your time and effort on this weirdness are very much appreciated!

Hans-Peter

Maybe some progress, but the weirdness — in my mind — deepens: the following with Beta 13 installed.

I used Windows' 'System Configuration' to do several Diagnostic startups. Then I loaded much of the normal boot inventory manually but in different sequences. Without Classic Menu running, DF loaded and displayed the default Windows Eight logo button on the DF Taskbar with all my shortcuts + normal operation.

However, with all startup items disabled and CM & DF launched manually, the custom button + shortcuts still failed to display.

At this point I was ready to give up. Then came the 'Eureka moment': I changed the position of the DF taskbar from Left to Bottom. And there was the custom CM button + shortcuts. Same story with Top position.

Position selection > Left, Right, and Automatic: no dice. Top and Bottom: everything displays and works.

As an extra check I rotated the secondary monitor back to landscape mode and repeated all these settings with identical results.

Provisional conclusion: after Beta 10 the failure of the CM custom button to display — on my two Windows 8 systems — is a function of the position of the DF Taskbar.

Over to you, Keith …!

P.S. During the period of Betas 11–13 no new stuff was added to my systems and no updates to boot items; in particular no new AMD Catalyst suite.

Very good news — I deeply appreciate your persistence and patience, Keith; all good wishes!

Hans-Peter

Keith: Many thanks for fixing this in Beta's 14 & 15!