Internode WoW Gateway Full Release v2 01/2010

[Azurewraith]

Hi all,
I have 3 computers in the house and all are having lag spikes at the same time. going from 229ms or there about to 2000+ms. Happens way to often or i wouldnt mention it.

My systems at home are patched, protected and working well otherwise.

I run a dlink router and a nice cisco wap.

Only time i have the problem is when i use the tunnel or 2 of us in the house use it. The 2000+ms latency can last quite a while.

I was playing online in a pug raid and about 3 of us said OMG Lag spike. after we wiped i asked who there isp was and they all said Internode.

Dont want be be nasty or annoying but need to have this looked at asap.

Thanks
Azures
Saurfang

[shlaimon]

i tried this 16 months ago and it didnt work then, just tried it now and it doesnt work.

Same thing wow just crashes.

[Grau]

http://rapidshare.com/files/433433664/wowgw.rar

edit the batch file to suit your locations
hasn't failed me once, couple hundred downloads too

Thanks Marshy919

[Marshy919]

No problem at all mate,
Just remember, if you come across any problems, run from the launcher.exe first (doesnt use the proxy), log into your character then exit.
Probably have to do this when 4.1 comes out.

Also, over 500 downloads now on the rapidshare server.
Heres a hotfile link:

http://hotfile.com/dl/111039421/7a96f16/wowgw.rar.html

[Duraze]

hi.

Is this still working?

I just downloaded from the last link and can't connect.
I get a wow error straight up.

[Linxus]

hi.

Is this still working?

I just downloaded from the last link and can't connect.
I get a wow error straight up.

Was working last night.

First off - are you setting it up correctly?
Also, what and where is the WoW error?
Are you actually an Intenrode customer?

[Marshy919]

Are you getting an error similar to this?

---------------------------
Wow
---------------------------
This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: c:\World of Warcraft\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:9CDCC920

The instruction at "0x9CDCC920" referenced memory at "0x9CDCC920".
The memory could not be "read".

Press OK to terminate the application.
---------------------------
OK
---------------------------

[Marshy919]

Something is wrong today, ping going up to 2000. Consistent drop-outs every hour or so.

[alpha_05]

Something is wrong today, ping going up to 2000. Consistent drop-outs every hour or so.

Not for me, I'm running at around 220ms and no dropouts so far in an hour and a half.

Anything else going on with your connection that could cause a problem?

[Marshy919]

Seems to have fixed itself
Must have been something else going on without letting me know.

[Jettblack]

^*** Never Mind I got it *** 450 500 down to 200

I have d/loaded the file above

For an Old Wow fella please put up some instructions on how to use it

i followed the info from front page but all i get is error - i believe i have done something wrong.

Its for Win 7 64

cheers

Jett

[Marshy919]

Sorry about late reply, haven't had time to check.
Good to see its working

[Nergo]

First of, sorry if an answer has already been posted but I keep getting a WoW Error whenever I try to run WoW.

ERROR #132 (0x85100084) Fatal Exception
Program: C:\World of Warcraft\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:74AB5D85

The instruction at "0x74AB5D85" referenced memory at "0x74AB5D85".
The memory could not be "executed".

[mokn2]

Is there anyway to get this working on rift?

[Marshy919]

Is there anyway to get this working on rift?

No, the gateway doesn't work to change by application.
Cant really speak on behalf of Internode on what the plans are for other MMO's.

First of, sorry if an answer has already been posted but I keep getting a WoW Error whenever I try to run WoW.

ERROR #132 (0x85100084) Fatal Exception
Program: C:\World of Warcraft\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:74AB5D85

The instruction at "0x74AB5D85" referenced memory at "0x74AB5D85".
The memory could not be "executed".

I actually had an error similar to this on another computer. The problem wasn't discovered, but after a reformat the error had vanished. I presume it was a conflicting program as the settings had not changed.