Page 2 of 2
Re: API Error 8
Posted: Fri May 19, 2017 4:09 pm
by JohnS
Thanks for some more suggesitons.
And yes I know about WinXP. The problem is I have been using some very useful, but old software that goes back to early 1990s, and runs under DOS. No windows version exists, and it is fast, a lot of commandline stuff. Version of Windows beyond XP still run some stuff slower. Latest is not always the best and fastest. And I understand why you would not test under WinXP--a waste of your time for sure
Re: API Error 8
Posted: Fri May 19, 2017 4:50 pm
by JohnS
Re: API Error 8
Posted: Fri May 19, 2017 11:54 pm
by gpb
It seems windows active desktop fails to set wallpaper, there is another (older) way to set a new wallpaper but currently wallpaperss uses it only when active desktop components are disabled. I don't remember how active desktop works on XP, anyway on next days I will prepare a WallpaperSS version that allows you to use the old method. It should work better.
Re: API Error 8
Posted: Sun May 21, 2017 2:49 am
by JohnS
Oh, well, gee, THANKS!
But I think read on forum that this error also appeared on a non XP system??? Not sure. if so, your work may be useful for all users, not just me
Re: API Error 8
Posted: Wed May 24, 2017 3:06 pm
by gpb
Here is a version where you can disable active desktop:
http://www.gphotoshow.com/files/wpsprosetup-424.exe
Here are a couple of .reg files to disable/enable active desktop interface. Extract them from the zip file and double click on DisableActiveDesktop.reg, accept all security prompt from windows and start WallpaperSS.
Re: API Error 8
Posted: Sat May 27, 2017 4:19 pm
by JohnS
Ok I will test these. Thanks for all your great support. I'll get back to you
Re: API Error 8
Posted: Sun Nov 26, 2017 3:47 am
by JohnS
Sorry for the long delay here. With the continual API error message I sort of had stopped using WPSSPro. I had downlaoded version 4.24 you gave, and also now have applied the DisableActiceDesktop registry setting, and am back to using WPSSPro on WinXP.
I will see if the API Error now goes away