recent warden may detect innerspace

[decxxx]

a recent warden update (4 hours ago at most) is causing lax's popular innerspace extention isxwarden to close world of warcraft for innerspace users on both US and EU realms. some people may still be able to bot wow by going around this detection (delete scan.dll from wow directory) but this does not fix the problem, it just makes isxwarden not know what its doing.

just thought id give you a heads up.

updates will be available whenever lax finishes them

here: Installing ISXWoW - ISXWoW

and here: IS Mods.com :: View Forum - Extensions::Releases

edit: and no im not talking about the recent wow patch warden, im talking about a newer sneaky warden update initialised with the rolling restarts. gliders may want to watch out too.

[bl@cK!]

I got a Message when i started WoW "Unexpected Warden Behaviour" so it wont start at the moment.

[mAdlax]

ye it kinda "protects" u in case the warden update may detect IS. just wait for update!

[decxxx]

"Unexpected Warden Behaviour" is what im talking about, it also appears as error(or somthing?) #78

[tttommeke]

People, just wait for some hours for an update if you want to feel safe !

[Apoc]

Any time warden updates, ISXWarden needs to be updated as well. This is nothing new. There are numerous threads about this between 3 different sites. Even a sticky on both about NOT making threads about warden updates.

[Kissy]

Error #78 usally requires you to reinstall ISXWarden. So just download current version and it'll be fine. Sometimes on Closing ob it seems to mess up (I've even lost my whole mapping folder due to this.)

Quote from Lax @ ISXWoW Posted: Fri Oct 12, 2007 4:42 pm

"ISXWarden 2.2.3-2 fixes the behavior #78 that began on Oct 12, 2007."

Yes thats and old post but its just to remind you that its a problem with ISXWarden sometimes that causes the #78
And in my usage of IS i generally get this error once or twice after updating.

[fattony]

Error #78 usally requires you to reinstall ISXWarden. So just download current version and it'll be fine. Sometimes on Closing ob it seems to mess up (I've even lost my whole mapping folder due to this.)

Yup, I've lost all my mapping data too because of this :/

[1337asusual]

some of the moderators of openbot and innerspae on mIrc are powertrips and jerks... i probably wont be buying this program.

[mAdlax]

Yup, I've lost all my mapping data too because of this :/

reinstalled, same error.

[goatjuh]

rofl, if u think a reinstall is gonna 'fix' the warden update u should be banned.

[Slint]

Just to clarify:

1) Reinstalling will not "fix" ISXWarden

2) There is no hotfix for error #78

3) Wait for Lax (ISXWarden owner) to update the file

4) Ignore 1, 2 and 3 and you will vastly increase your chances of getting banned

Patience is a virtue: )

[Edge]

Patience is a virtue, /agree

[T@rget]

I feel pretty pwnd tbh because I bought Inner Space yesterday and now I have to wait for a update. Not that I mind Inner Space costs money but ISXWarden is freeware. He might also be busy with other stuff

[tttommeke]

T@rget, you can also do a solution by copy the scan.dll to a backup folder, create a new, empty scan.dll and give it read-only rights. Because warden hasn't anything to do with scan.dll (scan.dll is for the preload of WoW to detect keyloggers etc) you are pretty save. Then you are also back able to bot further.

But if you want to be very sure, just wait until the update