Tatakai Software & PB Restriction: Invalid Memory Image 89003

[Huntsman]

Hi Andie,

Our Clan has been using Tatakai Software to manage both our CoD:UO and CoD2 servers for the past few years. And Tatakai ServerScan has been a wonderful Admin facility that has ed us maintain easy server moderation for both our Admins and Moderators.

Unfortunately since the last PB update, we have started to notice issues when our Moderators attempt to join any servers to play while having Tatakai running on the same machine. They are unfortunately getting kicked by PB for a Restriction: Invalid Memory Image 89003.

Have you heard of any others having this issue? Or have any ideas to find a solution. We have contacted PB to try and find a resolution, but no answer to date, other than not to run the software. Tatakai is a great facility and we would still love to use it.

At the moment the only way we can run the software is to have it independantly installed on another machine, and game on another. Which is not a problem for some of us in our clan that now run 2 or more computers, but would love to find another resolution for our other moderators.

Any suggestions would be greatly appreciated.

Cheers,
Hunts

[(WG)Agent_M]

Just as an additional note, to huntsman's post, it only seems to be the uo servers that are giving this kick, even if your not using tatakai for the server your playing on.
For example, I may have tatakai running for our cod2 server in the background, but playing cod:uo, and I will get the kicked from the uo server.
PB are not very forthcoming with information, as hunts mentioned above, and I believe there are other legit programs or processes that run in the background, that can also cause this, but again, PB is seemingly tight lipped about it all.

Be good to hear from other ppl playing uo, or even cod vanilla, who might be having this issue between tatakai and the new PB

[Andiehuk]

We have heard about this issue but as you say PB don't seem to be ing to fix it. Unfortunately we cannot really do anything I'm afraid. It's all in PB's court so to speak guys. Keep hassling them, thats all I can suggest!

Ta

Andy

[Huntsman]

Cheers Andy,

Will get back onto PB

[Andiehuk]

No prob, sorry I can't be of more . Let me know how you get on. Ta

[=CSA= Reaper]

I have the same problem and PB is quick to blame the server scan as the culprit

[Andiehuk]

This is a PB problem which they are aware of but it looks as though they are not going to fix it:-

10/18/2007 13:16:40 - "Glenn Courington"


Note #4: For the time being, the use of Tatakai cannot be used on PB-enabled servers. I apologize for the inconvenience.


10/08/2007 13:18:30 - "Jason"


Note #3: Restriction: Invalid memory Image (89003)


10/08/2007 06:53:00 - "Hendrik Thole"


Note #2: Please join a Punk Buster enabled server and get kicked. After getting kicked, send me the exact word for word kick message that you receive.


10/06/2007 17:50:51 - "Jason"


Note #1: Ticket submitted to support staff.

There is little we can do to remedy the issue. All I can suggest is you all keep hassling PB about it until they get off their asses and sort it out.

Sorry guys.

[Andiehuk]

It might be worth getting all your clan members to raise a ticket for this issue on PB's website as individuals. And then keep doing it until they listen guys!

Just an idea anyway...

[(WG)Agent_M]

Sounds like a plan, although with the current ticket I have in they seem to have stopped talking to me altogether....not impressed, as its clearly a PB issue and not a tatakai issue, as there seems to be other progs that can cause the exact same issue.

Thanks for the feedback anyway

[(WG)Agent_M]

Ok, well its only taken 5 months to get the following response :

01/19/2008 09:53:38 - "Glenn Courington"
Note #10: It is due to the way the tatakai was actually coded, and it is triggering this kick. I'm sorry, but tatakai will need to be recoded to not do this.

and I have replied with this response:

01/19/2008 10:14:04 - "wG|Agent M"
Note #11: Ok, first I would like to point out, just as a matter of interest more than anything, That this never occured until the update of PB that made it a "service". Their coding seemed perfectly fine before this and never caused this kick. Is it possible that its also an issue with PB?? Especially when you take into account that Tatakai is not the only program that now conflicts with PB since that update, and as a result to also cause this kick.

My main question though is what do they need to do with their code? I have been in touch with the people that wrote tatakai, and from what they have said, it is hard to do anything with it until PB offers some more info on why this kick is being caused. Perhaps if you can give me some details, I can pass the info on to them on your behalf, as I'm sure you are as keen to see this resolved as they are. I will also pass the link to this ticket along to the people who wrote tatakai so they can read first hand all the info you post.

Now I'm taking bets on how long this gets ignored for, as well as how long it takes them to post again.....providing they don't just lock it of course

Andiehuk, I'll PM you the URL for the PB support ticket while we wait to see what lies they come up with next in order to get out of fixing it...lol