Can't play, at all.

[torichan]

So basically it works like this;

I logged in and made a character, when I put in the secrethearth to play with my boyfriend, it stuck on the loading screen, and then made my router crash.
I had to reset my internet, leaving the router off for about 10 minutes at least to fully reset it, else it wouldn't work.

It was late so I went to bed after this, but today I tried once more. It did the same thing, so I tried during several things, starting with the internet fresh new-like so that there wouldn't be a mass of packages and see what happened, crashed again.

I tried with Pacho's client, and I can't even open it. I click on the file to open it, I have to click over 10 times for it to give me a small window, I uncheck IRC and everything, and it just will NEVER open the game, nor it gives me an error report, nor a crash report, doesn't say anything.

I tried from the site again, and it gives me the small window 800x600 game etc, and then it's fine for 5 seconds, but then it just stops working, the whole game. It's stuck, no matter what I click or where I go it doesn't work anymore. If I even could make it as far as introducing the secret hearth it would get stuck on loading and then kill my net connection.

What is there to be done about this? Has anyone encountered the same issue and found a possible fix? For further information I run on W7 Home Premium, and I am on a Wireless (sadly I can't hook myself up to the router!).

My internet works fine the whole day, only HH seems to eff it up so I think calling my ISP will be in vain.

[loftar]

As for the router issue, please see this post. I'm afraid it won't be terribly helpful, however.

As for the client not starting, I seem to recall people having reported similar problems; I'm less sure, however, whether those were specific to Pacho's client, to the default client or applied to both. Either way, people (on Windows) reported that javaw.exe was still running for the clients previously started and somehow blocked new clients from starting up, and that the problem could be solved by killing all running javaw.exe processes.