when finisher launches KTD process, the machine should already run the drive in enhanced mode (DMA etc), which is why I wonder what hardware your tests run on..
Strangely enough I have come across enough (older) machines that need to have DMA enabled manually after installation., which is quite annoying for any unattended installations obviously.
It's a laptop HDD, jtdoom
That's the reason why. I've also seen that when you copy large files from one location on the HDD to another one on the same HDD, that everything gets very slow. It's still LONG though.
Quite normal, as it has to read and write simultaneously.
Using two drives on the same IDE channel gets you better reults since one drive only has to read while the other only has to write, however, since the IDE bus isn't full-duplex capable, it still cannot do both tasks at the same time.
Yeah right...
It never did , its something that happens since the finisher.
And i dont have the time to sit back and relax.
Some people have to work u know.
We not all as lazy as you are.
Woha, now that is completely uncalled for! 
I don't think personal attacks help solving the matter or bringing the discussion any further.
Besides, the point of an unattended instalation is that you, well, don't have to attend it.
In that regard it does not matter if it takes a bit longer or not, as you are supposed to do some other work in the meantime!
If you're doing this professionally, you probably have several systems to install on.
The overall time for one machine is negligible, since you can just start it on one machine, then move to the next, while it installs automatically.
I fail to see how this has anything to do with lazyness and if you conclude that my joke of "having a drink in the meantime" means I am lazy, then you completely misunderstood what I said...!
Get a sense of humour before coming back to me.
