This is a very common problem, that probably a lot of people have without even realizing it.
The symptoms are long delays when linking, and slow breaking at breakpoints, specially the first one.
And also super slow context sensitive popups.
If linking in codewarrior takes longer then 1 - 5 seconds for you, you probably have this problem.
Its actually not the linking that is the problem, but it hangs after it is finished linking...
This annoyed me immensly, until I found the reason.
Every time you start the emulator, the "Symbolics Window" is opened. If you do not close this manually after exiting the emulator, codewarrior will start behaving badly, and extremly slow...
Just closing it will make everything A LOT more usable.
So.. until the codewarrior guys fix this problem, wich probably is just some stupid bug somewhere in the symbolics window, I created a small program, antisymbolics.exe, wich will monitor when you quit the emulator, and will then close the symbolics window for you.
Have saved our department hours of work time so far, and lots of avoided frustration.
If you want it, get it here: http://alh.underlandstudios.com/anti...isymbolics.exe
Source is available on request.
There is also another good reason to close the symbolics window, because it is often the one responsible for keeping some of your binaries opened, so that compileing from command line fails...
I've experienced these problems since CW 3.0, all version (tried OEM, personal and professional), and am now useing 3.1 professional