i tried installing ie6 using winetricks but still no luck, curseclient still keeps crashing after login :(

@scrimpy32: please stop your "windoze vs. linux troll flaming" here, thats definitly OFF TOPIC.

I was a matrix user and after reading that it doesn't respect people hard work i switched to curse immediately.

In the past curse was working with wine thanks to some people patching here and there, with version 3.0.4 curse developers embeded internet explorer in curse to show adds ( for pete's sake!!!!!). This mean that they destroyed on purpose the hard work of the linux community, even if they didn't do it on puprose it's clear that they consider us as important as a banana. On the other hand when you go to wowmatrix website you see a little penguin over there.

The question i ask myself is: is it worse to use wowmatrix that cosinders the linux users too but doesn't pay respect to addon developers or it's worse to use curse that breaks linux compatibility on purpose and doesn't give a s***  about linux and all the people that use it?

You can guess what most linux user answear will be. GG for breaking a perfectly working app!!!!!

  Quote:

Originally Posted by subbass

Can anyone confirm that installing the paid for client does work, rather than it "should" work. Currently I can't even install 3.0.4 , is the paid for version a seperate client or just the normal one you register with a key ?

I don't mind paying for it if its going to work.

Yes I'am able to run the CurseClient Premium under wine-1.1.20, x86.

It's actually the same Client you just have to login with the Premium Curse Account.

Some Problems persist with some wired NtLockFile if the Client tries to search for an update. You have to 'killall CurseClient.exe' then.

I have the normal version working perfectly now.

Karvec's solution of using winetricks to install ie6 was simple and effective. You can follow the directions on the WineHQ wiki at :

http://wiki.winehq.org/winetricks

But it boils down to two simple commands as follows:

First download the winetricks script from the authors site (kegel.com)with:

wget http://www.kegel.com/wine/winetricks

then use the next command to run the script and install IE6

sh winetricks ie6

Once thats grabbed the IE6 installer and done its thing the Curse Client worked fine.

Whether or not I do bother registering now is something I am going to reconsider, breaking an app for a not insigificant number of people (though it is a very small overall percentage) simply to show adverts does rise my hackles to the point I am not sure I feel like paying,  this morning I absolutely was about to pay and was happy to, as a way to  show my support of the site in general. As an alledged cheapskate, beardy, hippy, freetard linux user I actually donate to a lot of software projects.

  Quote:

Originally Posted by subbass

I have the normal version working perfectly now.

Karvec's solution of using winetricks to install ie6 was simple and effective. You can follow the directions on the WineHQ wiki at :

http://wiki.winehq.org/winetricks

But it boils down to two simple commands as follows:

First download the winetricks script from the authors site (kegel.com)with:

wget http://www.kegel.com/wine/winetricks

then use the next command to run the script and install IE6

sh winetricks ie6

Once thats grabbed the IE6 installer and done its thing the Curse Client worked fine.

Thanks a lot, I just wanted to confirm this solution as working perfectly.

It's not that we intentionally broke compatibility under wine.  However, we don't support or test on wine either.  I know that can be a frustration to the users who do play wow under wine and I apologize for that.   I am glad though that people found this solution.  After some more testing from you guys I'll be taking the info and making a sticky here for other wine users. 

I just installed Ubuntu 9.04 with wine.

I'm a premium user, and I ran "wine /windowspath/programfile/curseclient.exe" and everything went fine without any trick.

The curse client found the wow path itself and updated my addon without problem.

  Quote:

Originally Posted by subbass

I have the normal version working perfectly now.

Karvec's solution of using winetricks to install ie6 was simple and effective. You can follow the directions on the WineHQ wiki at :

http://wiki.winehq.org/winetricks

But it boils down to two simple commands as follows:

First download the winetricks script from the authors site (kegel.com)with:

wget http://www.kegel.com/wine/winetricks

then use the next command to run the script and install IE6

sh winetricks ie6

Once thats grabbed the IE6 installer and done its thing the Curse Client worked fine.

Just wanted to say thanks.  Those 2 commands you gave me worked perfect.  I had let curse sit there for awhile thinking it would need time, but it just never crashed or didn't anything.  Processes said it was a zombie.  Once I ran the sh winetricks ie6, bam curse was running fine.  Thanks again.

jau! it seems my ie6 installation was messed up, after doing a fresh install of ie6 the curseclient now works again :D

Hey, subass, thanks for breaking down my "use winetricks to install ie6"...  I should've done it myself, but I was feeling lazy.  Glad it's working with my fix.  Resubmitted to AppDB with Gold rating and fix.

Karvec: No, thank you for posting the solution in the first place, I take no credit at all ;)

Kaelten, I understand that you guys do not have a client for Linux. But you need to understand that many Linux users used WowMatrix mainly because it had a native Linux client, and things like this will only annoys those users.

And the workaround is just that, a workaround. I hope that you guys look and see if there is a bug in the client causing the crash, due to the lack of Internet Explorer, and find a solution. Seeing as there is a high chance that IE will not be a mandatory core part of Windows anymore, even Windows users may see this crash; and I bet you wouldn't ask those users to use IE just for your client, right?

IE8 is installed by default in Windows 7 RC and the Final as well with the option to remove if the end user wants to .

this wont change anything.

Im sorry

Being a Wine user, I have to say that installing IE6 just to get the Curse Client working is not an option for me. Sure it can be done as other people have shown here. However, I've read about problems people have had with installing IE on Wine. The results can be pretty bad. I'd prefer to avoid having to delete my .wine directory because IE hosed my Wine registry.

I was using WUU until I found out that the Curse Client wasn't all that evil. I would even put up with the popup advertisement if the client still worked. The Curse client was slick, and worked pretty well under Wine. Unfortunately I'm going to have to go back to WUU until the Curse client's design is modified to run on Wine. It won't surprise me if that never happens of course; Curse has already stated that they had to imbed an IE frame, which means MSHTML.DLL. Wine developers are probably going to have to fix their Gecko adaptation instead.

If you're still having trouble launching after installing IE6 through winetricks, try running via command line at the Curse directory (ie)

karvec@icecube:~$ pkill pulseaudio

karvec@icecube:~$ cd .wine/drive_c/Program\ Files/Curse/

karvec@icecube:~/.wine/drive_c/Program Files/Curse$ aoss wine CurseClient.exe

In other words, kill pulseaudio and then run aoss in front of wine.  I was having some problems myself, and I read this on this forums from http://wow.curse.com/forums/t/75439.aspx :) :)

Hope it works for everyone!!  Thanks all!

I've gotten a little further with WUU.  Requires wxPython.  Thanks for the tip.

Isn't WUU just like WM, leeching?

  Quote:

Originally Posted by divideoverflow

Being a Wine user, I have to say that installing IE6 just to get the Curse Client working is not an option for me. Sure it can be done as other people have shown here. However, I've read about problems people have had with installing IE on Wine. The results can be pretty bad. I'd prefer to avoid having to delete my .wine directory because IE hosed my Wine registry.

I was using WUU until I found out that the Curse Client wasn't all that evil. I would even put up with the popup advertisement if the client still worked. The Curse client was slick, and worked pretty well under Wine. Unfortunately I'm going to have to go back to WUU until the Curse client's design is modified to run on Wine. It won't surprise me if that never happens of course; Curse has already stated that they had to imbed an IE frame, which means MSHTML.DLL. Wine developers are probably going to have to fix their Gecko adaptation instead.

I haven't read anythng about problems with ie6 in current 1.x versions of wine.  I even ran ie6 just to verified it worked, and it surfs the internet.  Strange seeing that on linux.  And it's not going to get changed, us linux users are a small subset of users, and it works fine under wine, so does it matter?  Also, if you go premium it works without ie6 installed.  Your call, but WUU looks to me to be just like WM so far, leech of bandwidth.

I'm think it might be similar.  The general issue here is that addons have to be essentially GPL according to Blizzard's terms of service.  So now they are whacking update manager's for "leeching" what they release, because it doesn't have credits or redirects to the author, or isn't updated on time, or it's just too much bandwidth.  That's not very team. 

Perhaps the problem can be solved by blizzard hosting the addons, and allowing any manager to update from it.  If you can't find addons in the first place, what is the gain for the user, the addon author, or for WoW in the long term?  They need to solve this, because I can't spend what little free time I have tripping over author's ego's.

I think we can all agree that wow would suck without the addons.  Maybe Blizzard should, in their own self interest, give something back to the addon author's.  Giving credit where credit is due, and taking the bandwidth hit would be a big help for them and for WoW as a whole.  With whatever self-preservation WoW and the author's possess, they had better figure this out quick.  Messing around with pop-up's/broken clients and paying another monthly fee for a GPL'd addons that they don't even create is not my idea of fun.

"is that addons have to be essentially GPL according to Blizzard's terms of service. "

That is absolutely not what the ui policy says _at all_.

Addons must be a) free of charge, and b) readable.  That in no way implies that addons must be GPL or any other OSI compatible license.