|
Originally Posted by davrol
|
I had a similar problem. When I installed CB 1.2 "over the top" on my X50v running WM2003 SE OS, PocketBreeze V5 did not run as a Today Screen plug-in. When I went to "settings\today\items" PocketBreeze did not show as an option.
This was caused (I think) becuase the file "windows\pocketbreeze.dll" had been deleted!
Re-installing PB5 cured the problem and both now work fine. Both upgrades are superb :approve:
PocketWeather and iLauncher are run from PB5 tabs and were not affected.
Although I have only installed CB 1.2 very recently, it seems that my whole X50v now runs much faster and more smoothly, particularly after a soft reset. I don't really understand why this should be so (it may be just my imagination, but I don't thnk so).
|
Hi davrol :)
There seems to be some kind of issue that is caused by CB installer that caused the "DLL" registry key for PocketBreeze to be removed, and then causing PocketBreeze to be removed from the Today screen after users install the new ContactBreeze version in some rare cases, which I'm still not sure what they are

but you can be sure I'm working really hard to find and get this resolved of course :)
To resolve this users can simply reinstall PocketBreeze after CB, if this happened to them, or, you can manually add the missing DLL string value on the PocketBreeze registry entry and set it to "\Windows\PocketBreeze.dll", which will also resolve this issue.
Anyway, this is something that we noticed from our side and working to resolve as fast as we can :approve:
In the meanwhile, we've finished moving our downloads server to our new dedicated servers that are much larger and faster than our old servers, which means many of the load issues that we had on our servers in the past will now be resolved, so although we gave up a bit on our development in the past two days during this weekend I'm pretty happy with the move to our new servers :approve:
Since Juni's skins are also stored on our downloads server, users that usually download Juni skin updates from our site and had a few issues with it in the past due to the load on our servers should see that things work much better now :) (we just finished moving the DNS to the new server a few minutes ago).