阅读:2693回复:3
4.2下HIVE-based Resgistry实现的问题
4.2下我照帮助添加了HIVE-based Registry,设置了环境变量,修改了[HKEY_LOCAL_MACHINE\\init\\BootVars]下面的设置,但是我的系统起不来。我用flash来存储HIVE,因为我没有专门的外部存储器。除了上面的设置外,还要做哪些修改???
|
|
沙发#
发布于:2003-12-03 16:04
下面是我的串口打出的消息:
>>> Loading module NK.EXE at address 0x800B8000-0x80166000 (RW data at 0x81376000-0x813E4A4B) 0x83cb7024: first = 01f40000, last = 02000000, SharedDllBase = 02e80000 0x83cb7024: >>> Loading module coredll.dll at address 0x03F10000-0x03FF6000 (RW data at 0x01FFF000-0x01FFFFD0) 0x83ca48c0: >>> Loading module filesys.exe at address 0x04010000-0x0408C000 0x83ca48c0: FileSystem Starting - starting with clean file system 0x83ca48c0: FSVOL: Opening existing volume 0x83ca48c0: FSVOL: Volume heap already initialized 0x83ca48c0: FSVOL: Initializing volume heap 0x83ca48c0: >>> Loading module fsdmgr.dll at address 0x03D30000-0x03D4C000 (RW data at 0x01FE1000-0x01FE1754) 0x83ca48c0: InitSharedHeap: 46200000 10000 c 0x83ca48c0: InitSharedHeap: return 46200050 0x83ca48c0: >>> Loading module relfsd.dll at address 0x03E80000-0x03E8B000 (RW data at 0x01FF4000-0x01FF4ABC) 0x83c6e184: InitSharedHeap: 46200000 0 c 0x83c6e184: InitSharedHeap: return 46200050 0x83c6e184: >>> Loading module pm.dll at address 0x03EE0000-0x03EFD000 (RW data at 0x01FFB000-0x01FFB6C4) 0x83c6e184: *** Power Manager: DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x83c6e3e6 *** 0x83c6e184: >>> Loading module device.exe at address 0x06010000-0x06020000 0x83c6e184: >>> Loading module ceddk.dll at address 0x03D10000-0x03D16000 (RW data at 0x01FDD000-0x01FDD068) 0x83c6e184: Ceddk!CalibrateStallCounter: Enter 0x83c6e184: Ceddk!CalibrateStallCounter: Could not find stall counter 0x83c6e184: Ceddk!BeginCalibration: min(368) max(460) 0x83c6e184: Ceddk!BeginCalibration: elapsed is 432 0x83c6e184: Ceddk!BeginCalibration: delay is 22 0x83c6e184: +PmInit 0x83c6e184: +PlatformValidatePMRegistry 0x83c6e184: -PlatformValidatePMRegistry: returning 0 0x83c6e184: DeviceListsInit: default GUID found in registry as expected 0x83c6e184: DeviceListCreate: creating list entry for class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 0x83c6e184: PlatformDeviceListInit: using stream interface to access class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 0x83c6e184: DeviceListCreate: creating list entry for class 98c5250d-c29a-4985-ae5f-afe5367e5006 0x83c6e184: PlatformDeviceListInit: using stream interface to access class 98c5250d-c29a-4985-ae5f-afe5367e5006 0x83c6e184: DeviceListCreate: creating list entry for class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 0x83c6e184: PlatformDeviceListInit: using display interface to access class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 0x83c6e184: InitDisplayDeviceInterface: returning 1 0x83c6e184: DeviceListCreate: creating list entry for class a32942b7-920c-486b-b0e6-92a702a99b35 0x83c6e184: PlatformDeviceListInit: using stream interface to access class a32942b7-920c-486b-b0e6-92a702a99b35 0x83c5d424: +PnpThreadProc: thread 0x03c5d662 0x83c5da94: +ResumeThreadProc: thread 0x03c5dcd2 0x83c59400: +ActivityTimersThreadProc: thread 0x03c5dfb2 0x83c59400: ActivityTimerCreate: ActivityTimerCreate(\'UserActivity\') returning 0x00000000 0x83c59400: ActivityTimerCreate: ActivityTimerCreate(\'SystemActivity\') returning 0x00000000 0x83c57628: +SystemThreadProc: thread 0xe3c5df7e 0x83c57628: +PlatformManageSystemPower 0x83c57628: PlatformPMActivelyManagesPower: returning 1 0x83c57628: PlatformManageSystemPower: waiting for initialization to complete 0x83c57d4c: +BatteryMonitorThreadProc: thread 0xe3c596f2 0x83c57d4c: BatteryMonitorThreadProc: battery interface APIs not available, exiting 0x83c57d4c: -BatteryMonitorThreadProc: exiting 0x83c6e184: -PmInit: returning 1 0x83c57628: PlatformManageSystemPower: initialization complete 0x83c57628: PlatformLoadTimeouts: ACUserIdle 60000, ACSystemIdle 300000, ACSuspend -1, BattUserIdle 60000, BattSystemIdle 180000, BattSuspend 300000 0x83c6e184: DEVICE!DevloadInit 0x83c6e184: DEVICE!InitDevices: Root Key is Drivers\\BuiltIn. 0x83c6e184: DEVICE!ActivateDeviceEx(Drivers\\BuiltIn) entered 0x83c6e184: >>> Loading module regenum.dll at address 0x03F00000-0x03F07000 (RW data at 0x01FFD000-0x01FFD4A4) |
|