Win7 TranscodedWallpaper.jpg and heavy disk use
Posted: Sun Dec 30, 2012 11:41 am
Hi there!
I've been regularly using WSSPro for quite some time now, and I've noticed something interesting...
On Windows XP, when WSSP creates it can be directly applied as the wallpaper -- and in fact, WinXP converts any file type manually set as a wallpaper to a bitmap file anyway, even when Active Desktop is enabled.
But in Windows 7, wallpapers seem to be converted to JPG in order to display, under so unless I'm missing something, when WSSP creates the BMP file, windows converts it back into a JPG which is causing a CPU and disk usage spike when changing between wallpapers with the program.
What possibility is there of testing to see what version of Windows the application is running under, and writing a BMP to disk for XP and a JPG for newer operating systems? I haven't had the chance to see how things work in Windows 8 yet, but I'd guess that it's probably using JPG as well, so Windows XP would be the special case...
Thanks for reading, and I look forward to a reply!
I've been regularly using WSSPro for quite some time now, and I've noticed something interesting...
On Windows XP, when WSSP creates
Code: Select all
C:\Documents and Settings\{username}\Application Data\WallpaperSSPro\Wallpaper.bmp
But in Windows 7, wallpapers seem to be converted to JPG in order to display, under
Code: Select all
C:\Users\{username}\AppData\Roaming\Microsoft\Windows\Themes\TranscodedWallpaper.jpg
What possibility is there of testing to see what version of Windows the application is running under, and writing a BMP to disk for XP and a JPG for newer operating systems? I haven't had the chance to see how things work in Windows 8 yet, but I'd guess that it's probably using JPG as well, so Windows XP would be the special case...
Thanks for reading, and I look forward to a reply!