v7.2 Beta6 photos screen saver doesn't work. When I enable the screen saver (DF), CPU shortly thereafter goes to near 100 percent on all four cores and displays remain blank. I move the mouse to end the screen saver, okay. When I right-click the DF system tray icon to bring up the Screen Saver Settings screen, a notification window pops up "Photos Screen Saver has stopped working" and asks me to end the program or not. This didn't happen with Beta5.

Also, the installation procedure has changed. I used to be able to simply install a new version of DF on top of the old one and everything worked fine. Now I get a warning that two HookApps couldn't be unloaded/ended and do I want to Ignore, Abort(Cancel?), Retry. Retry doesn't work, Abort rolls-back the install, and Ignore just continues on but then requires a system reboot. This behavior started in Beta5 I believe. I learned that if I manually Exit DF before doing the update/install, then it works as before.

Yea, I'm having the same problem, but only on one machine, the other works fine. This error is the Event Log:

Log Name: Application
Source: Application Error
Date: 5/16/2015 2:09:28 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: KDAVISOFFSITE
Description:
Faulting application name: Photos.scr, version: 7.0.1.0, time stamp: 0x5554d26f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18839, time stamp: 0x553e8c17
Exception code: 0xe053534f
Fault offset: 0x000000000001aaad
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-05-16T19:09:28.000000000Z" />
<EventRecordID>20436</EventRecordID>
<Channel>Application</Channel>
<Computer>KDAVISOFFSITE</Computer>
<Security />
</System>
<EventData>
<Data>Photos.scr</Data>
<Data>7.0.1.0</Data>
<Data>5554d26f</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.18839</Data>
<Data>553e8c17</Data>
<Data>e053534f</Data>
<Data>000000000001aaad</Data>
</EventData>
</Event>

Just an update to tell you that v7.2 beta7 had no effect on either of these problems.

The photo screensaver seems to be working properly in v7.2 beta8.

I noticed that you changed the font scaling between beta5 and beta8, as used for the wallpaper image info text. When I changed the font, two sizes smaller to make it comparable to before, from the time I clicked OK to the dialog box clearing, was 64 seconds. That's a lot slower than previously. I didn't notice any CPU spikes so not sure what this is.

Just an observation on a related but different topic: I started using the 7 Sidebar gadget to keep some of my gadgets from seemingly migrating across the screen on their own. It has an option "Keep on top", and when I have this enabled the wallpaper info text respects this sidebar gadget column space and offsets the text. For example, I have the text set to lower-right corner, but with the gadget Keep-on-top set, DF sees the left edge of the sidebar as the right edge for text, not the display's right edge. The wallpaper image continues to show properly to the right edge of the display. Is this by design? I would prefer it use the display's right edge because I can always add padding to the text if I'm concerned about it being hidden by the sidebar.

Re the installation process, this time I got a warning very early on that DF was running and I would need to close DF before proceeding. While this warning was displayed the install process closed the main DF program but left two application hook processes running. So at the end of the install I got a second warning and that I would have to restart after installation. The second time I tried this I manually killed the two hook processes at this point and no restart was necessary.

Seems I spoke too soon re screen saver and CPU usage. As soon as the screen saver kicks in, CPU for all cores goes to about 80 percent. This is re v7.2 beta8.

No, no crashing problems while I had it installed. But I've gone back to beta5 because that was the last version that the screen saver didn't run-up the CPU.