Antrix General !Help!

[xxWARKILLxx]

Ok so I got Antrix all set up and made a server I learned all the GM commands but I my WoW always has a Problem when going to Ashenvale were I get a "file corrupt" Ive tried everything repair utility , reinstalling WoW,reinstalling Windows and even using different installationdisks but one thing is for sure once I get this criticall there is NO WAY to log on that character anymore. Always end up deleting him. So I .saveall just before I went to Ashenvale since I knew it might happen is there anyway to rollback the server to that save point? or that I can remotely move my toon out of that area... I thought about making another GM account and using .summon ***** but it would only work if I was online and I cant even log into that certain toon... any help here?

[Jargs]

you could go into navicat and change his position in the characters table

[xxWARKILLxx]

Thanks for the help I use Heidi :P but will do :D

[[Nazzeth]]

I had that same issue on real wow for quite some time, Blizzard couldn't fix it.

The error has to do with one of the models for an Ashenvale Building being corrupt, and as soon as u get within a certain radius of it, it dies.

Blizzard suggested all sorts of stupid crap, but i found that installing it on another drive fixed the issue.

Hope this helps with your issue.

[xxWARKILLxx]

Yeah Kinda the reason I left Blizzard servers It all started right after 2.1.0 Patch and I'm sure as hell not gonna start over. so I sold my account (had all pre BC tiers and 2/5 T4 and full gladiators. I tried all their checkdisk shit and "defrag lawl" and down to the point in which they said it was my memory....It couldn't have been I returned my 2gigs OCZ 6400 Gamers Extreme PT edition ....one this is weird though out of all the ppl that posted this problem on Blizz site all of the were using dual core processors maybe that was the problem :P

Well more thread related... It wont let me change the location through Heidi gives me "WARNING NO ROW WAS AFFECTED BY LAST UPDATE"
"This is most likely caused by entering data which the MySQL-server has converted silently: For example When you enter a date like "0000-01-01"
(Applies to newer MySQL-versions)

[EDIT] spelling :P