Isn´t there any OS where you can decide over the task/process scheduler and command it like "UAE and all it´s subprocesses runs on this cpu and everything else runs on that cpu" wouldn´t that improve speed?
Yes. It's called processor affinity. Windows NT 4.0 and later have an affinity mask for both processes and threads. Linux kernels 2.2 and 2.4 required a patch to support this. Don't know about 2.6.
Normally, there isn't really a reason to tie a particular process to any one processor. It's best to let the OS thread scheduler do all the work. EDIT: I'm curious to see how dual-core processors perform in practice compared to a "hyper-threading" processor, in which multiple threads of execution share the same L2 processor cache.
Now, I suppose you could reduce latency due to context switching (EDIT: and cache misses) by sticking certain processes on certain processors, but I don't know that it would make a huge difference for an application like UAE that is mostly event driven. But if you're doing something fancy like rendering in LightWave 3D. . . .
So, dual-core processors are exciting, but it's up to application developers to take advantage of the features. SMP systems have been available for years, and most applications are still written to be either single-threaded or run multiple threads synchronously. Hopefully, dual-core processors will sell well enough to change things. Parallel programming has been a popular topic in recent issues of Dr. Dobbs, C/C++ Users Journal, and other practical programming mags, so I think change is on its way.
Trev