Bit of both, though I assure you it had nothing to do with your post. Upgrades on x64 were not quite happy earlier, but I think I've got it sorted for tonight and fresh installs should be fine as well.
OK, I believe I have everything sorted for the evening. It's at .20 now and it's forcing writing some files again on x64's. No code changes. Sorry for the bumps there. I'll keep watching this for a bit, but anything further is liable to be deferred until tomorrow.
I'm still trying to get the "best" solution for tonight. The initial issue was a file wasn't in sync on the server, but it's shown up a problem relating to upgrading x64 now. Fresh installs should be fine.
I have checked the standalone installers again on x64 Vista for shareware and the enhanced builds. The only way this error should be happening is if somehow the compatibility flag is tripped to tell the installer it's running on XP SP2. Vista can automatically offer to set this if it thinks the install didn't complete for some reason, which would then carry over to subsequent attempts. Can right-click on the file and open Properties for it and check the Compatibility tab.
OK, we understand the code path that resulted in this from the update. SoundPackager has been setup to copy the packages from the master all users directory to allow other users on the system the option of editing the packages under their user accounts and not impacting other users on the machine. However, in this build, that was triggered to only be on new installs rather than updates. So when the directories for the sound packs switched to the new location with the beta, the t
If you lost the sound packages on update, please send \program files\stardock\sdcentral\installed\snd.log to [email protected]. I've upgraded them here successfully, not clear what went wrong (though they did move directories from where they were in the previous install). Does uninstalling SoundPackager and reinstalling it get them back?
WinCustomize Forums
Nothing was touched online today. Odd. Email [email protected] your program files (x86)\stardock\sdcentral\installed\wb6.log please.
Yes, Agrippa. I will try and get a better handle on it tomorrow.
Uninstall. Before rebooting, do this: Start / run / cmd.exe cd \windows\system32 ren wbload.dll wbload.old cd \windows\syswow64 ren wbload.dll wbload.old Reboot. Reinstall. Better?
Did you (anyone reporting a problem) previously have WindowBlinds 5.51 installed for Windows Vista x64? And is Stardock Central reporting Build 160 in Help / About?
VapidProse, best thoughts on your "not a valid win32 app" report: your download was corrupted, you've leftover temp files from something else, or you've got something that's mangling the installer when it tries to run.
The webpage is wrong and I'm correcting it. The 6.00 release will not be supporting Windows XP x64. We may revisit that in the future, but no promises. Customer service can refund your order or add a WindowBlinds 5.51 registration that does have XP x64 support, though not the new WB6 features. I apologize for that. It looks like it was corrected after the pages published, but something was holding onto the cached version with the old text.
I've reset your activation count.
Stardock Central is treating "WindowBlinds 6" as a new application, so the Update dialog that appears on start won't show it. Maybe we'll tweak that, but under the Object Desktop section, select WindowBlinds 6 from the list and install it. You can install it over an installed WindowBlinds 5 installation, though be sure to reboot when prompted at the end of it. After installation, you won't see the WindowBlinds 5 listing (unless you fiddle with the show/hide settings in Stardock C
With regards to the problem with serials I mentioned earlier, that should be sorted and a non-issue for people who got emails with one that was unhappy. The backend has been updated and they should use the serial in email and their email address as normal. Still sending out emails with the free upgrade info. There are quite a few of them. Come Wednesday, if you do not have your email (
There as an issue with some of the emails that went out. We're trying to sort it on the back end so the serials won't have to be changed. Otherwise, there will be a second email for some people. There's no need to install WB5 first, though once you install WB6, Stardock Central should be hiding the display of the WindowBlinds 5 component so there's less confusion.
Does it say build 160 in Help / About in SDC?
AnneMarie, it doesn't seem to have gotten to your account yet. Jebro, you don't seem to have a WB5 registration under the email address you're using on WinCustomize.
Emails are being sent with a download link and serial to the WindowBlinds 6 upgrade for eligible standalone users. If you don't get the email, by later this afternoon you should be able to visit stardock.com/support and it will also resend the info. The serial is different from your WB5 one and you will have to activate after installing/upgrading. Kris
The .vmdk files that make up the disk images should have no trouble being on flash drives. I use mine off USB hard drives on a daily basis. I am not using a flash drive for them because I make use of the "snapshots" feature of VMWare workstation to keep various machine states ready for testing. That winds up adding another 1GB or so per XP snapshot based on the amount of allocated ram to the image and differentials to the disk images.
I've created an account and sent them a 1:1 as well, but no guarantees on if/when I'll get a response. They seem to be renaming wblind.dll and wbhelp.dll rather than deleting them, though admittedly I didn't reboot to see if they were then queued for removal on reboot.
larry2004, you appear to have one order from April in the system. If there's been a problem with attempting to charge a more recent order (or something else quite frankly), please contact [email protected].
WinCustomize Forums
We've reproduced it internally and are contacting ATI to let them know the latest update isn't quite thrilled.
Natsgum, I reset your activations. Remember you can save the sig.bin or sig6.bin (in the case of WindowBlinds) and not have to reactivate on that particular OS installation in the future.
The beta for SkinStudio 6 should be available next week.
Stardock Forums
JoeUser Forums