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.
Lain8
[quote who="steve-" reply="8" id="1900786"]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. [/quote]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, wher
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 opti
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.
The problem isn't about what is intended to mean, it's more about not writing it down properly. I found out 6.3 dropped support for XP x64 systems, the hard way, I think that's just dumb software developers aren't able to properly write down the OSes their product supports. Frankly, I think the "dropped support" on XP x64 is just a bug Stardock isn't able to overcome, or got them by surprise after release. Stardock added support for XP x64 specif
[quote who="Cavan1" reply="2" id="1899750"]True, which means all version of XP are supported, including XP x64. 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. [/quote]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?
Neil, "XP" means all versions of XP are supported, just as "2003" means all versions of server 2003 are supported (so, including 64 bit versons of the OS'es)
[quote who="Bebi Bulma" reply="19" id="1898284"]It doesn't specify about XP 64bit, but it does support Vista 64bit. [/quote]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?
Look, I know with XP X64 I'm the odd one out, especially as many developers (including MS) don't realise it's a version of XP, that their product just will have to work on it if they claim your product is suitable for windows XP. I've kinda grown used to not expecting anything from hard- and software and vendors, but you guys did have a working product, even if it has it bugs, but it worked if I just left it alone (don't try to unload WB). Now, I'm stuck with the worst idea Microsoft's design
Sorry, but I understood XP x64 support was added with the update to 6.1. :S I wouldn't be bothered with it if it wasn't for that pesky hardware issue those nforce 4 chips are having, preventing me from using Vista.
6,3 broke the XP64 support I'm afraid, the frames around the windows just stopped working.
Windowblinds does mess up the ff3 skin, specifically the slight gradient in colour in the toolbar, or any other toolbar theme for that matter. (I think it's because windowblinds switches the windows skin to classic) Messes up a lot of other things too, when I try to make it switch to windows I have to use ctrl-alt-delete to disconnect my account, and even then my sound isn't working when I reconnect. But that's a whole other issue. :P
I have a licence for wb 5 and 6, (got 5 because 6 won't work on XP x64) now my XP x64 system is dead and waiting for a new mobo. Can I use WB6 on this computer and when my other system is repaired use WB5 on that one? (keeping WB 6 installed and running at the same time)
The main question is of course how much work it is to adapt wb 6 for XP x64 systems, if it's mainly the same with a few slight differences then it would be doable. But I understand from Stardock staff that XP x64 support is in the works, so us who use that OS just have to hold our breath for a bit, like we're used to.
kudo's for Stardock promt reply, I got an serial for 5.51 They told me that "sorry about the XP 64 bit support, I do know the developers are working on it and someday we should have it compatible." I still have a problem with v5.51 though: [link="http://www.xs4all.nl/~degast/Lain/Desktop_wb.jpg"]screenshot[/link]
Just got my first copy of WB, just to find out version 6 doesn't work with XP x64. *mails support@Stardock* XP x64 isn't as bad as some people think though, support could be a little better but I see no reason to upgrade to Vista other than autoCAD not working, but that doesn't work on Vista x64 either.