Re: Hive Registry problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

OK, I have gotten rid of the PCI Bus initializing warnings so now if I boot no hive it boots clean. When I change to HIVE I get a new message. Perhaps this message will provide a clue. I am including the last several lines of messages before the infamous "Failed to wait..." message. Again as in my earlier post the system.hv file gets created on the drive only now it has a size of 40 instead of 0.

Also, I contacted the vendor for the hardware to ask for help and they just want to sell us a BSP and have us paying royalties. The cost structure they indicate they want is prohibitive for what we are doing.

4294769213 PID:e3bc8c1a TID:23b940da 0x83bca800: FATFS!InitVolume: driver disagrees with BPB (BPB CHS=982:16:32)
4294769225 PID:e3bc8c1a TID:23b940da 0x83bca800: >>> Loading module diskcache.dll at address 0x03EB0000-0x03EB6000 (RW data at 0x01FF0000-0x01FF04EC)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\EMPC2000\RELDIR\ADVANTECH_X86_DEBUG\DISKCACHE.DLL'
4294769336 PID:e3bc8c1a TID:23b940da 0x83bca800: CreateCache: Successful. Cache Size: 123 KB, Start: 1, End: 492.
4294769337 PID:e3bc8c1a TID:23b940da 0x83bca800: CreateCache: Successful. Cache Size: 246 KB, Start: 493, End: 503263.
4294769337 PID:e3bc8c1a TID:23b940da 0x83bca800: FATFS!InitVolume: FAT version: 16
4294769338 PID:e3bc8c1a TID:23b940da 0x83bca800: FATFS!InitVolume: Cluster Size (Sectors): 8
4294769341 PID:e3bc8c1a TID:23b940da 0x83bca800: FS: Registering file system Disk, index 7, flags 0x00000002
4294769342 PID:e3bc8c1a TID:23b940da 0x83bca800: FS: Mount complete (Disk, index 7, flags 0x00000002)
4294769344 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FILESYS: Device started. Boot file system ready.
4294769344 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSREG: Unable to read value "SystemHiveInitialSize" under HKEY_LOCAL_MACHINE\init\BootVars
4294769350 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSVOL: Opening existing volume
4294769351 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSVOL: Volume heap already initialized
4294769352 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSREG: Mounted ROM portion of system hive
4294769352 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FILESYS: Loading system hive from Disk\Documents and Settings\system.hv.
4294769352 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49
4294769357 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_GetFileAttributesW(\Documents and Settings\system.hv) returned 0xffffffff (3)
4294769358 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_GetFileAttributesW(\Documents and Settings\system.hv) returned 0xffffffff (3)
4294769359 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_CreateFileW(\Documents and Settings\system.hv) returned 0x0 (3)
4294769359 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSREG: Mounting clean system hive
4294769359 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: BuildPath: Disk
4294769360 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_CreateDirectoryW(1 chars: \) returned FALSE (183)
4294769360 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: BuildPath: Disk\Documents and Settings
4294769470 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_GetFileAttributesW(\Documents and Settings\system.hv) returned 0xffffffff (2)
4294769471 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_GetFileAttributesW(\Documents and Settings\system.hv) returned 0xffffffff (2)
4294769471 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_CreateFileW(\Documents and Settings\system.hv) returned 0x0 (2)
4294769471 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FSVOL: Creating new volume (size=49152 bytes)
4294769472 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: FATFS!FAT_GetFileAttributesW(\Documents and Settings\system.hv) returned 0xffffffff (2)
4294789825 PID:a3b901e2 TID:e3bc8bea 0x83bc8a3c: Atapi!CDisk::ReadWriteDisk> Failed to wait for interrupt (m_dwDeviceId=0)
4294789825 PID:e3bc8c1a TID:e3bc8bea 0x83bc8a3c: Read/Write Sector failed (30) on Sector 86958

Voidcoder wrote:
First try to restore the original common.reg as may be some
necessary entries are modified or removed.

Another issue may that standard generic ATAPI driver
can not handle properly you IDE controller. Personally
I have seen this a few times on several x86 motherboard.
Hit PAUSE key when the BIOS is printing the device
map and verify what is behind the xx/xx/xx, normally
you will see Device/Bus/Function in that table.

Did you try to contact the board vendor?

"Steve" <skelley@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23CEHBuiQGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx

I think I may be having PCI bus initialization problems. I get several messages on boot either in HIVE on not mode. The messages are like:

Warning: No Match template is found for following PCI Device
The following devices give the above message
Host / PCI Bridge
PCI / ISA Bridge
Other Bridge

The messages give additional info then:
PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device xx/xx/xx.
PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus

My understanding of what is going on here is VERY limited. I would assume based on the message that the PCI devices are announcing themselves to the OS during power up (PNP?) and there is nothing in the registry to tell the OS what to do with them. If this is correct then it kinda makes sense that if the disk does not need to be accessed during boot for a ROM registry the boot would finish but with a hive registry these devices need to be configured before the OS completes booting. Does this sound right?

Voidcoder wrote:

Well, I don't know where you can get the original
Platform.reg, perhaps re-install the PB or install it on
a different PC.

Do you see Atapi!CDisk::ReadWriteDisk fails
when using RAM based registry?

Note in the most cases you don't really need any
changes in registry to get the hive registry working
with the standard HDD. The HDProfile in registry
already contains all the required setings for that.


--
Steve Kelley
Protean Instrument Corp.





--
Steve Kelley
Protean Instrument Corp.
.

Relevant Pages

  • Re: Hive Registry problems
    ... No Match template is found for following PCI Device ... PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device xx/xx/xx. ... I would assume based on the message that the PCI devices are announcing themselves to the OS during power up and there is nothing in the registry to tell the OS what to do with them. ... If this is correct then it kinda makes sense that if the disk does not need to be accessed during boot for a ROM registry the boot would finish but with a hive registry these devices need to be configured before the OS completes booting. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ntoskrnl.exe problem HELP
    ... option when you go to try to boot into safe mode, ... I hope I don't see anything like this ever again, messing with the registry ... access the installation as a simple data disk and use a suitable ... from the working Windows installation ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: ntoskrnl.exe problem HELP
    ... option when you go to try to boot into safe mode, but whenever I copied another boot.ini file to it, any additional options other than the different variations of "Safe" mode disappeared. ... I hope I don't see anything like this ever again, messing with the registry isn't one of those things I like to do, but in this particular case, I didn't really have any choice. ... 2- Mount the disk in another Windows NT type computer and use the "Load Hive" feature in Regedit or Regedt32. ... 3- Access the broken installation via a "Parallel" or proper "Dual Boot" installation on the same computer and use the "Load Hive" feature in Regedit or Regedt32. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Ho to run CF driver before reading hive-based registry
    ... BOOT SECTION": ... so I had to rewrite the driver for it. ... The problem is now the hive-based registry. ... FileSystem Starting - starting with clean file system ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Final Report Vundo
    ... Since I have a dual boot capability, ... registry is more easily done from the XP partition. ... Vundo with a now deleted file (another thing that Shedrick explained in his ... ddayv.exe and ddayv.dll in the system32 directory, ...
    (microsoft.public.windowsxp.configuration_manage)