My error. I thought it determined boot sequence. Perhaps if you alter your boot sequence to have WB start and fully finish booting before Take Command boots (or just not have it in your startup programs but rather open only when you need it) the problem will be resolved.
As far as I understood, the word "startup" not necessarily means startup of Windows or PC. I am sorry if I was wrong. I meant the launch of Take Command. It has nothing to do with the boot process.
Could it be that the Take Command GUI conflicts with WB7's?
But WB is what responsible for GUI. It can only conflict with itself.
If so, excluding it from WB7 should have solved the problem.
In my first post I mentioned that it doesn't help. Only complete removal of WindowBlinds solved the problem.
There must be something else in that program conflicting with WB7.
Of course, no doubt
If that happens no matter what you do, and the Total Command is critical to your work, you might have to sacrifice WB7 on that machine
. Only Take Command, not Total.
Sorry for your trouble, noxmetus.