I am redownloading the current 0.2.9 just to double check it. Ok old version of 0.2.9 pre audit works so I would not except that as a problem. Unless something has changed because of the audit<not expect so>.
I have upgraded my qemu to version 0.8.0 without the kernel accerator. Ok I have to put that back. Ie the reason for running the old version had to update both. So if yours is 0.8.0 then its not most likely the cause.
binutils-2.16.91-20060119-1-src.tar.gz I know works.
As well as standard tree binutils-2.16.1(Ok a few other bugs appears but it boots past that point it get the full gui up it can cause minor apps problems).
gcc-3.4.5-20060117-1.tar.gz I know works as well.
Since you followed the setup Guide I guess you have them.
ntoskrnl.exe Displayed does Suggest a problem I big one.
To be at the ntoskrnl.exe Qemu has already loaded and run the freeloader. Now is locating it.
Note I built my gcc and binutils poorly optmised in i386 mode not i586 mode. This very rarely can cause differences. I don't expect this to be a problem since the core developers are using i586 optmised.
This is something strange. The question is what is causing the problem.
I missing that you mentioned blue screen before sorry. QEMU gives the same message on a black screen(I sometimes wish that programs had completely different error messages). Blue screen is a kernel bail out bad causes can be many. Incompad envorment Ie QEMU bad versions can do this.
This error is suggesting that either the cdrom driver is not loaded or the cdrom filesystem driver is not working. Question why. Has freeloader failed to load it. Or the default hives damaged in your version of reactos.
Note I always press a key there but I don't expect that to be the difference.
At this point all we can do is compare versions and make sure we match kinda close.
I will edit this message after I test the current source on the download server
http://jaist.dl.sourceforge.net/sourcef ... EL-src.zip
Or post a confirm note if the forum blocks me from editing this message.