[jszrules]

Someone on another forum said that deleting "iCAR.bundle" will fix the following problem. Before I do that, I just wanted to check here if you think that makes sense?...

I logged on to iChat and all my buddies appeared correctly and everything, but when I selected a screenname and chose to text message them, a window appeared that said:

iChat Internal Error!
NSInternalInconsistencyException:
Chat is not in compose mode anymore

There were two buttons I could select: "Quit" (would quit iChat) or "Continue" (would make the window disappear, but the same thing would happen if I tried to text message someone again).

This is different from the iChat error messages that end with
Invalid parameter not satisfying: (index >= 0) && (index < (_itemArray ? CFArrayGetCount(_itemArray)
or
NSConcreteMutableAttributedString addAttribute:value:range:: nil value.
Apparently both of those can be fixed by disabling CocoAspell or enabling the Helvetica font. But, as you can see, the message I am getting is a little different.

Will deleting iCAR.bundle essentially kill iCAR on my computer, or will it just kind of "refresh" iCAR, allowing me to continue using it in the future? Obviously, my main concern is if deleting the file will get rid of this iChat error message in the first place. Thanks.

[jszrules]

can anyone confirm that deleting iCAR.bundle makes sense? i don't know what .bundle is, so i wouldn't want to delete it, have it not work, and then find out that iCAR died in the process.

[Chuckit]

I don't use iCAR, but it appears to be a SIMBL plugin, so deleting iCAR.bundle will remove iCAR. But I think the point is that iCAR is causing the problem. Keep in mind, iCAR is a hack for iChat; it isn't a supported plugin, so it's a bit iffy. It could very well be causing internal inconsistencies.

[jszrules]

it worked. deleting iCAR.bundle did solve the problem, although it sucks losing some cool features that came with iCAR. hopefully the Tiger iChat has some of those features. thanks.