Hi Jon,

the facts in a short:
- 281 images files
- 177mb
- 0.63mb per file
- different background image for every monitor (2 devices, 1600x1200 and 1440x900)
- DF running since 8 hours and 40 minutes
- background image changes every 20 minutes
- 26 switches until now for today

Today I saw that DF wrote ca. 290mb of data on my hdd. This are more than 10mb per switch! What is DF doing?!
I'm using sysinternal's process explorer:
-- http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

DF doesn't slow down my laptop, so it's no problem for me. But maybe you can reduce the written bytes per switch. Maybe it will make some people lucky.

Have fun,
Carsten

You can configure the columns to be shown: View - Select columns... - Process performance - I/O Read Bytes and I/O Write Bytes
The delta may be interesting too in this case.

Carsten

DF writes a CustomeWallpaper.bmp file (in my case a dual screen width file), and bmp's are huge (10 meg), so that may be correct.

Not sure if windows will use a .jpg without converting it to a big 'ol .bmp file...

Do you know how Windows 7 handles wallpaper? (.bmp or .jpg/.png)

Looks like Vista (and W7) use .JPGs now: Good article:

http://chris.pirillo.com/vista-wallpaper-tip/

"Okay, since Windows Vista supports JPG wallpapers, you should no longer set your wallpaper through Internet Explorer (which converts images to BMP before they’re set to your desktop, totally nullifying any kind of improvement the Vista shell team did in respect to saving system resources). Here’s how I’d suggest doing it from this point forward...."