CodePage Reg Key Error at Boot

[James Tabor]

Hi,
I'm getting "Couldn't open CodePage registry key. With OK".
I copied freeldr.sys and the rest and reinstall everything, including
config files from hives. Installs and go. 1st install system, 2nd reboot
ok run fine, and 3rd reboot and get the above error at freeldr.
Revision: 18820
Node Kind: directory
Schedule: normal
Last Changed Author: cwittich
Last Changed Rev: 18820
Thanks,
James

[Ge van Geldorp]

>   From: James Tabor
>  Hi,
>  I'm getting "Couldn't open CodePage registry key. With OK".
>  I copied freeldr.sys and the rest and reinstall everything,
>  including config files from hives. Installs and go. 1st
>  install system, 2nd reboot ok run fine, and 3rd reboot and
>  get the above error at freeldr. 
Not sure if this is the cause of the problem, but I just fixed a memory
overwrite (r19068) which could potentially have caused the in-memory copy of
the registry to be corrupted. If this corrupt copy was then written out to
disk you could get that error message during the next boot. Again, not sure
if this was the cause of the problem (I can't reproduce the original
problem), but the time frame seems to fit.
GvG

[Hartmut Birr]

Ge van Geldorp wrote:
> >   From: James
> > Tabor
> >  Hi,
> >  I'm getting "Couldn't open CodePage registry key. With OK".
> >  I copied freeldr.sys and the rest and reinstall everything,
> >  including config files from hives. Installs and go. 1st
> >  install system, 2nd reboot ok run fine, and 3rd reboot and
> >  get the above error at freeldr.
> >       
>  Not sure if this is the cause of the problem, but I just fixed a memory
>  overwrite (r19068) which could potentially have caused the in-memory copy of
>  the registry to be corrupted. If this corrupt copy was then written out to
>  disk you could get that error message during the next boot. Again, not sure
>  if this was the cause of the problem (I can't reproduce the original
>  problem), but the time frame seems to fit.
>  GvG
>  _______________________________________________
>     
I've investigate a little bit in the registry problem. Freeldr imports
the binary hives. During importing the system hive, it fails at
\Registry\Machine\SYSTEM\ControlSet001\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}.
A key or subkey cell has a wrong identifier. Freeldr stops at this point
and imports the next hive. Later, freeldr does search for
\Registry\Machine\SYSTEM\Select. This key isn't loaded,  because it is
located after the wrong cell. Freeldr isn't able to create the correct
link for \Registry\Machine\SYSTEM\CurrentControlSet. I will check, if
r19068 does fix the problem.
- Hartmut

[James Tabor]

Hartmut Birr wrote:
>   Ge van Geldorp wrote:
> > >   From:
> > > James Tabor
> > >  Hi,
> > >  I'm getting "Couldn't open CodePage registry key. With OK".
> > >  I copied freeldr.sys and the rest and reinstall everything, including
> > >  config files from hives. Installs and go. 1st install system, 2nd
> > >  reboot ok run fine, and 3rd reboot and get the above error at freeldr.
> > >       
> >  Not sure if this is the cause of the problem, but I just fixed a memory
> >  overwrite (r19068) which could potentially have caused the in-memory
> >  copy of
> >  the registry to be corrupted. If this corrupt copy was then written
> >  out to
> >  disk you could get that error message during the next boot. Again, not
> >  sure
> >  if this was the cause of the problem (I can't reproduce the original
> >  problem), but the time frame seems to fit.
> >  GvG
> >  _______________________________________________
> >     
>  I've investigate a little bit in the registry problem. Freeldr imports
>  the binary hives. During importing the system hive, it fails at
> \Registry\Machine\SYSTEM\ControlSet001\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}.
>  A key or subkey cell has a wrong identifier. Freeldr stops at this point
>  and imports the next hive. Later, freeldr does search for
>  \Registry\Machine\SYSTEM\Select. This key isn't loaded,  because it is
>  located after the wrong cell. Freeldr isn't able to create the correct
>  link for \Registry\Machine\SYSTEM\CurrentControlSet. I will check, if
>  r19068 does fix the problem.
>  - Hartmut
>   
Yes, that worked.
Thanks,
James

[Hartmut Birr]

Ge van Geldorp wrote:
>   Not sure if this is the cause of the problem, but I
> just fixed a memory
>  overwrite (r19068) which could potentially have caused the in-memory copy of
>  the registry to be corrupted. If this corrupt copy was then written out to
>  disk you could get that error message during the next boot. Again, not sure
>  if this was the cause of the problem (I can't reproduce the original
>  problem), but the time frame seems to fit.
>  GvG 
It didn't solve the problem. I get the error again. The difference is,
that is now an other key which reports the error. I've also removed some
entries for my GB-NIC in hivesys.inf.
UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1506) Name:
\\Registry\Machine\SYSTEM\ControlSet001\Control\Class
UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1510) Class
UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1511) Invalid key cell id!
UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1512) "KeyCell->Id  0,
REG_KEY_CELL_ID 6b6e, KeyCell->CellSize 0
UNKNOWN means DEBUG_HB ;-) . On an unmodified source, it fails on line
#1481 in binhive.c.
- Hartmut

[Hartmut Birr]

2005/11/9, Hartmut Birr <osexpert(a)googlemail.com>om>:
>   Ge van Geldorp wrote:
> >   Not sure if this is the cause of the problem, but
> > I just fixed a memory
> >  overwrite (r19068) which could potentially have caused the in-memory copy of
> >  the registry to be corrupted. If this corrupt copy was then written out to
> >  disk you could get that error message during the next boot. Again, not sure
> >  if this was the cause of the problem (I can't reproduce the original
> >  problem), but the time frame seems to fit.
> >  GvG 
>  It didn't solve the problem. I get the error again. The difference is,
>  that is now an other key which reports the error. I've also removed some
>  entries for my GB-NIC in hivesys.inf.
>  UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1506) Name:
>  \\Registry\Machine\SYSTEM\ControlSet001\Control\Class
>  UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1510) Class
>  UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1511) Invalid key cell id!
>  UNKNOWN: (boot\freeldr\freeldr\reactos\binhive.c:1512) "KeyCell->Id  0,
>  REG_KEY_CELL_ID 6b6e, KeyCell->CellSize 0
>  UNKNOWN means DEBUG_HB ;-) . On an unmodified source, it fails on line
>  #1481 in binhive.c.
>  
My hivesys.inf conaints 11 entries for additional scsi drivers and one
entry for an test driver.
- Hartmut

[James Tabor]

Hi,
Problem is back in Revision: 19270. First and second boot no problem.
Third reboot, CodePage reistry key.
Thanks,
James

[Hartmut Birr]

James Tabor wrote:
>   Hi,
>  Problem is back in Revision: 19270. First and second boot no problem.
>  Third reboot, CodePage reistry key.
>  Thanks,
>  James
>  
Fixed by r19294.
- Hartmut

[James Tabor]

Hartmut Birr wrote:
>   James Tabor wrote:
> >  Hi,
> > Problem is back in Revision: 19270. First and second boot no problem.
> > Third reboot, CodePage reistry key.
> > Thanks,
> > James
> >  
>  Fixed by r19294.
>  - Hartmut 
Sorry, no it did not. After shutdown and power down, restart the system,
CodePage on the third boot.
James

[James Tabor]

James Tabor wrote:
>   Hartmut Birr wrote:
> >   James Tabor wrote:
> > >   Hi,
> > >  Problem is back in Revision: 19270. First and second boot no problem.
> > >  Third reboot, CodePage reistry key.
> > >  Thanks,
> > >  James
> > >  
> >  Fixed by r19294.
> >  - Hartmut 
>  Sorry, no it did not. After shutdown and power down, restart the system,
>  CodePage on the third boot.
>  James 
Ok,
Once you get CodePage, and have it fixed, you have to rm -rf * the drive and
recopy everything back, to rebuild the system. It's a pain but a clean fix.
Thanks,
James