none
CE 6.0 change Hive-based to RAM-based registry; shell.exe doesn't start RRS feed

  • Question

  • Hello,

    I switched from Hive-based registry to RAM-based registry and now my OS stops after lunching shell.exe.

    PB Debugger Loaded symbols for '<reldir>\SHELL.EXE'
    FS: Creating signal event SYSTEM/DevMgrApiSetReady
    FS: Creating signal event SYSTEM/PowerManagerReady
    FS: Creating signal event SYSTEM/GweApiSetReady
    FS: Creating signal event ReleaseFSD
    FS: Creating signal event system/events/notify/APIReady
    FS: Creating signal event SYSTEM/DCOMApiSetReady
    FS: Creating signal event SYSTEM/ShellAPIReady
    FS: Creating signal event SYSTEM/NLedAPIsReady
    FILESYS: Launching apps
    PB Debugger Unloaded symbols for '<reldir>\SHELL.EXE'
    FILESYS: Launching shell.exe
    OSAXST1: >>> Loading Module 'coredll.dll' (0x8FAD9848) at address 0x40010000-0x4016A000 in Process 'shell.exe' (0x8FA4AED0)
    OSAXST1: >>> Loading Module 'shell.exe' (0x8FA4AED0) at address 0x00010000-0x00028000 in Process 'shell.exe' (0x8FA4AED0)
    ValidateArgs: Arg 0 invalid ASCII string pointer 0x00000042
    ObjectCall: returning 8088c5b0
    !! Process Initialization failed - Process 'shell.exe' not started!!
    OSAXST1: <<< Unloading Module 'coredll.dll' (0x8FAD9848) at address 0x40010000-0x4016A000 in Process 'shell.exe' (0x8FA4AED0)
    OSAXST1: <<< Unloading Module 'shell.exe' (0x8FA4AED0) at address 0x00010000-0x00028000 in Process 'shell.exe' (0x8FA4AED0)

    With Hive-Registry, some drivers are loaded before Filesys launces its apps. Do I need to set something that filesys loads the drivers before init?

    Or do I have to pay attention to something when booting with RAM-based registry?

    I'm on MIPS IV and Updates are from end of 2012.

    Regards,

    John

    Monday, July 22, 2013 10:20 AM

Answers

  • Hello,

    Thanks for your replys.

    The issue was somethings with my CE installation. Not long ago, we put it under version managemant and the PC where it was done had problems with it.

    I've tested the change with a "clean" one and there it booted normaly.

    Stragely, I hadn't any errors with hive-based.

    Regards,

    John

    • Marked as answer by John Bober Tuesday, July 23, 2013 10:54 AM
    Tuesday, July 23, 2013 10:52 AM

All replies

  • Hi,

    You would need to change registry contents to support ram based registry. Initially it would have been customized to support hive. You need to make changes in platform.reg especially for sections enclosed under

    ;HIVE BOOT SECTION ... ;END HIVE BOOT SECTION. Typically try reversing one by one the changes under these sections.

    The changes in these portions along with selection of SYSGEN_FSREGRAM should help you in booting back under ram based registry.

    Regards,

    Balaji.

    Monday, July 22, 2013 12:43 PM
  • I don't think ;HIVE BOOT SECTION ... ;END HIVE BOOT SECTION is harm for this issue.

    After switched to RAM based registry, did you give clean sysgen?


    Please mark as answer, if it is correct.
    Please vote,if it is helpful post.
    All the Best
    Vinoth.R
    www.e-consystems.com
    http://vinoth-vinothblog.blogspot.com

    Monday, July 22, 2013 1:20 PM
  • Hello,

    Thanks for your replys.

    The issue was somethings with my CE installation. Not long ago, we put it under version managemant and the PC where it was done had problems with it.

    I've tested the change with a "clean" one and there it booted normaly.

    Stragely, I hadn't any errors with hive-based.

    Regards,

    John

    • Marked as answer by John Bober Tuesday, July 23, 2013 10:54 AM
    Tuesday, July 23, 2013 10:52 AM