Quote:


so, actually, what you are saying that "break off" works just as it should.
you just don't want to read from the manual what it does.




Uh so actually you're just calling me lazy, because you were too lazy to read my posts. I know what the manual says it does, in fact if you read my posts, I mention the behavior described in the manual. What I am trying to figure out is why the behavior described in the manual isn't working if the console is hidden.

Quote:


and, you can't terminate wkix32 process with any priviledges without proper special tools.




Do you consider Task Manager a special tool? While logged in with an account that has local admin privileges to the workstation, I can go to the processes list in Task Manager, highlight wkix32.exe, click the "End Process" button, click "Yes" on the warning that says something about ending a process could adversely affect your system, and wkix32.exe will terminate. Now on my workstation, yes I do have all kinds of "special tools", such as the Windows Server 2003 resource kit. However none of those tools change the behavoir of the task manager. I can do the exact same thing from any other workstation on my network. In fact my test machine has nothing but the OS, Office, and all the latest service packs and hot fixes installed on it.

Quote:


I have a small voice in the back of my head that this behavior/bug of break off and a hidden console for kix32.exe has been talked about before.... but be damned if i can find a topic on it.




I couldn't find a topic on it either. Found some really old topics about modifying a .dll file to remove the close button from the console window... crazy stuff like that. Nothing specifically mentioning break off not working on a hidden console.

As soon as you change the console state to anything other than hidden, it works the way the manual says it should. Just doesn't work while it's still hidden.