True, which means all version of XP are supported, including XP x64. I know, try to tell the marketing guys...

 

Any news on the 6.2 install for XP x64 users Neil?

 

 

Nope, since 32 and 64 bit are specified for Vista, not being specified for XP means no 64 bit support, if 64 bit was not specified for Vista then your argument would/could hold true.

That way I could also argue for no 32 bit support for XP, as 32 bit was not specified, might as well not support XP, Hmm?

Not really considering 32-bit is the standard. While Vista 64-bit is gaining popularity, XP 64-bit hasn't shined one bit. So generally when something is listed Windows XP that means 32-bit unless specifically stated like it does with Vista.

nope just "XP" means all version of XP, how am I supposed to know what Stardock considers the standard?

Quite a few XP versions have made it to the marked the past years... Windows XP Home, Windows XP Professional, Windows XP Media Center 2003 Windows XP Media Center 2005 Windows XP Tablet PC Edition , Windows XP N, Windows XP Starter Edition, Windows XP Professional x64 Edition, not even mentioning the service packs.

Stardock doesn't consider it a standard, the industry does. Believe it or not XP 64-bit was a total flop. It's a very small nitch market that companies are providing a supported product to.

Since 32-bit is still the standard in todays market it's safe to say that if something is labeled Windows XP is only 32-bit. I think the dead giveaway that WB 6.3 had no XP 64-bit support would have been the fact that Vista lists both 32-bit and 64-bit, rather than just saying "Vista".

I agree with you that XP x64 was a total flop, a nitch market and support might not be economicly justified but I dissagre with you on how to write that down. I think software companies should be more aware of the windows versions that are out there, after all, that's what they are designing their product for. If your product doesn't work on a specifiec version of the OS, write that down.

 

I know that with running XP x64 I have take the risk that my OS will not work optimally, or not at all with software. What is different in this situation is that 64 bit XP support was supported by WB 6, Stardock "dropped" support in an update.

Am I supposed to look up system requirements for every update of my software?

Uhm, yes? I thought that was a given? Especially when XP 64-bit is the OS you run.

Window Blinds 6.3 on XP 32-bit Service Pack 2: Since updating to 6.3 Windowlinds will not list any of the animations that are included with many of my skins, for example I used to force the use of the animations in "Aeroglass V5". The skin list is built properly for applying the other visuals, but only the bundled skins show in the animations option screen. I tried an uninstall of WindowBlinds followed by a fresh download and install, but can't get past this. I force animations as some of the other Vista Aero style skins have buggy animations and I don't like the plain ones! What do you think causes this? Thanks.

Remember we're talking about an automated update here, more over, I'd have to browse to stardock.com and look up the system requerments for 6.3 bevore giving Impulse the go-ahead for the update, also, in the update history is no mention of dropping XP x64 support, where in other updates oddities with this OS were mentioned in the history. I just think whatever is preventing 6.3 to work under XP64 got Stardock by suprise, as it did the useres.

It's not an automated update, you still have to click "Update" in order for the update to start. This just goes to show that people don't even care to look at something as simple as System Requirements before updating/installing something. It takes a few seconds to check them out rather than an hour trying to fix a problem that is easily avoidable.

Showing sys reqs (specially if they change) might be a good thing.

Good feedback.

In any case the History should be current on all updates and somethign like this should be in teh history.

Indeed, I'm not so much anoyed at Stardock for not (beeing able) to support XP x64 with version 6.3, I'm anoyed because they didn't tell me that their update would break my blinds and make it impossible to intall 6.2 again.

 

Contacted support, they told me to try and roll back the 6,3 install, I did try, but that didn't work because I uninstalled WB. I did try installing WB and then rolling back, but that didn't work either.

Well actually... XP 64 is just Server 2003... with XP user interface options. I wouldn't call XP64 a flop... mainly because when it was released everyone would've never thought you'll use more than 2GB of RAM in a PC... now it's different. In widely PC forums, areas, XP64 is acutally a really heavy used OS.

More or less.. in 6.2 Enhanced XP64 was supported, if 2003 is supported in 6.3 there should be no reason why xp64 shouldn't be compatible as well mainly because like I said, xp64 is server 2003, and the standard server 2003 version is 64-bit.

Now onto my question... with every custom skin I try I lose my top window bar(close, minimize, maximize) I can't even move the window! Only way is to revert back to the XP theme.

Anyone have a solution for this? I've tried everything in the knowledge base as well.

Start a new post and you'll have more luck I think.