Hartmut Birr wrote:
Hi,
since some time, I'm not able to install ReactOS on real hardware.
Freeldr fails at the first boot after the second stage setup. The error
message is 'Couldn't open CodePage registry key'. I've add some debug
messages to freeldr. Freeldr isn't able to open the key
'\Registry\Machine\SYSTEM\CurrentControlSet'. If I rename umpnpmgr.exe
between usetup and the second stage setup, ReactOS boots without any
problems. If I rename umpnpmgr.exe back, ReactOS fails on the second
boot with umpnpmgr.exe.
- Hartmut
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
In fact i think it's a problem in freeldr. If i change the keyboard /
regional setting during initial setup, freeldr gives an error message on
each following boot. :-(
So, changing the keyboard layout via the settings is NOT working. You
can end the blocking problem by recopying the original (the unchanged
from before the setup) registry files into /reactos/system32/config
There are 2 solutions for having a regionalized keyboard:
- a complicate one, you change the default codepage in the sources of
the initial registry parameters (i don0t remember exactly where because
i have blocking compile problems on reactos since 6 weeks)
- a "quick and dirty" but 100% functional one:
you simply copy your favorite keyboard layout "kbd????.dll" onto
"kdbus.dll"... :-)
This is now my favorite solution because it does not force me to compile
reactos myself.