Installed & registered fine. But when I try to create a screensaver, I get the message; the program can't start because VCRUNTIME140.dll is missing from your computer. Try reinstalling the program to fix this problem.
Uninstalled & reinstalled = same message.
Restart PC, install again, and get the same message once more.

Deeg  –  3 years ago  –  このコメントは役に立ちましたか？ はい | いいえ (+10)

翻訳

Animated Screensaver Maker is one of 3 similar, related apps Desktop Paints develops. They basically use the same sort of graphics FX you might find in a mid-range to higher end game to add motion FX, & optionally sprites, to a static image of your choosing. Screensaver Maker saves the results as a screensaver, Wallpaper Maker creates animated wallpaper, & Animation Maker lets you create video clips.

On the plus side the software lets you create animated scenes without the learning curve & work involved creating the same thing from scratch, while the screensaver & wallpaper files are smaller than a video file would be, so they're easier to share. The apps, screensavers, & wallpaper work best using the graphics hardware on a Windows device [PC, laptop, tablet], and one downside is that not every device has the graphics horsepower needed. Note that running one of the created screensavers or animated wallpapers will likely bring a graphics card or separate [discrete] GPU out of power saving mode [if your device has a graphics card or separate GPU].

All three of the Desktop Paints apps are light weight -- installing them has little impact on Windows itself -- and as you can see on their blog page, Desktop Paints is continually adding improvements.
blog[.]desktoppaints[.]com/

mike  –  3 years ago  –  このコメントは役に立ちましたか？ はい | いいえ (+8)

翻訳

Windows XP, Editor_S.exe is not a valid Win32 application.
The same version 4.3.2.

JardaH  –  3 years ago  –  このコメントは役に立ちましたか？ はい | いいえ (0)

翻訳

JardaH, because the issue here is NOT about core processing or anything to do with the CPU or even resource requirements like procedures not found in system DLLs..

That error is due to the version number they chose when building the program is NT version 6.0 which is potentially executable or recognised as a valid win32 application in Vista and above. Version 2.4.9 that I still have installed here too was built to be potentially runable or accepted as a valid win32 application in NT 4.0 and above. Theoretically it could be possible to hack the executable file to pretend it was built for a different NT version number but that would invalidate the digital signature and just expose a new reason why it won't work under XP... but it might also work!

The system requirements statement including XP in the list with the build you have AND the version given away today 4.3.9 is an error and sadly for the millions of XP users out there, it is not XP compatible in its current form.

JardaH, because the issue here is NOT about core processing or anything to do with the CPU or even resource requirements like procedures not found in system DLLs.. That error is due to the version number they chose when building the program is NT version 6.0 which is potentially executable or recognised as a valid win32 application in Vista and above. Version 2.4.9 that I still have installed here too was built to be potentially runable or accepted as a valid win32 application in NT 4.0 and above. Theoretically it could be possible to hack the executable file to pretend it was built for a different NT version number but that would invalidate the digital signature and just expose a new reason why it won't work under XP... but it might also work! The system requirements statement including XP in the list with the build you have AND the version given away today 4.3.9 is an error and sadly for the millions of XP users out there, it is not XP compatible in its current form.
Save | Cancel

TK  –  3 years ago  –  このコメントは役に立ちましたか？ はい | いいえ (+6)

翻訳