2 Jan
2009
2 Jan
'09
2 p.m.
João Jerónimo
I've done some hobbyist OS developing for some
time in the past and one of
the worst things I could do, specially when writing hardware-sensitive
? stuff, was
write tons of code without testing it on real hardware.
IMHO, it's ok to test with the emulator when
writing the code (i.e. during
the write-compile-test cycle), but from time to time you'd better check it
on real hardware, too.
ReactOS is tested on many real systems, on a daily basis.
There are millions of different hardware specs and configurations, not all of which follow
the standards, and which of course have their own subtle bugs and misnomers. We obviously
don't have access to the same range of beta testers Microsoft has, or the same number
of hackers linux has.
Combine this with the fact that ReactOS is still in Alpha and you have a combination which
isn't going to work on every single real machine out there. As ReactOS matures, it
should start to run on more and more default setups as we start to both stabalise our code
and introduce new code to handle the problems of running an OS on a huge amount of
different bases.
But of course, as you've done some hobbyish OS development, you didn't need me to
tell you that.
Currently the only way we can find out what is causing the problem on your system is by
getting debug output from you. If you aren't able to do this, then your only hope is
that someone else hits the same problem you have, from which we are able to get debug
output and fix, or we inadvertently notice whatever is causing your problem and things
just start to work for you.
Ged.