Re: Hive with self made Flash File System

Hi Paul!

I am mounting as root. Location of hive files is on Flash. Flash Filesystem
is marked bootable. I set the flag to start device manager and storage
manager so that it will be started.

Actually, I further digged into the problem. Everytime new file "System.hv"
and "user.hv" gets recreated. I have no idea why would the filesystem do that.
It is a system file with hidden attribute. FSD gets queries for the file
twice with "OPEN_EXISTING". It replied with correct attributes and size and
directory location. Thereafter next request come to recreate the
file"CREATE_ALWAYS".


Any reason why would it re-create the files?

Thanks much.


"Paul G. Tobey [eMVP]" wrote:

So, currently you have the flash file system *not* mounted as root. Change
the location of the hive files to be on the flash. Capture the debug
messages. It's saying that it can't find the hive? The flash filesystem is
marked as bootable? So that the hive registry code knows what to wait for?
*Is* it waiting? Have you set the right things for starting device manager
and storage manager so that it will be started? You don't have any other
disk devices marked as bootable, right?

PSM is monolithic. It does not use a separate file system driver.

Paul T.

"JAM" <JAM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7494EC62-2145-4426-BC3D-7ACD0BFD39FD@xxxxxxxxxxxxxxxx
Hi !
Hi!

Apology if I was unable to explain earlier.

Actually I tried both using MountasRoot and MountasBootable flags for
particular profile I created and thereafter I tried without those flags.

I am actually able to see hive files in the storage device where its
getting
created.

But for some reason it's seems like not reading from those locations when
rebooting the system.

Depending on the Flags value I set below it either loads DeviceManager or
Storage Manager.
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="system.hv"
"ProfileDir"="Profiles"
"Flags"=dword:0
; END HIVE BOOT SECTION

When MyFSD driver loads, thereafter DeviceManager driver loads and just
hangs at BUSENUM.dll. Usually in any normal situation Block driver gets
loaded at this point.

I was curious if the Block Device Driver is required for Hive Based
Registry
Functionality?

As I had earlier mentioned that I do not have any Block Driver(or FMD) and
I
have implemented read/write NAND functionality in my File System Driver
itself. As my File System Driver is Monolithic.

Since I have my own FSD do I have to implement Registry read write
functions ?


Thanks!

"Paul G. Tobey [eMVP]" wrote:

I just told you! You're expecting to store the hive in \Documents and
Settings, but *that's not on the flash filesystem*! So, reading it back
won't work; it was never saved to persistent storage!

Paul T.

"JAM" <JAM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7EA21E69-2CB2-4DB8-8FE9-3AB72CA85AEC@xxxxxxxxxxxxxxxx
No I am not mounting the flash filesystem as the root.

So I made changes as below.
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="system.hv"
"ProfileDir"=""
"Start DevMgr"=dword:1
"Flags"=dword:3

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\MYFSD]
"FriendlyName"="MYFSD"
"Dll"="MYFSD.dll"
"BootPhase"=dword:0
"LoadFlags"=dword:1 ; 1:load synchronously 2:load asynchronously

; END HIVE BOOT SECTION

Could you please let me know if I am still doing something wrong in
registry.

Thanks much!


"Paul G. Tobey [eMVP]" wrote:

You're mounting the flash filesystem as the root? Otherwise, won't
Documents and Settings *not* be in the right filesystem?

Paul T.

"JAM" <JAM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D635428D-ECC6-4896-A0B9-CD31DFEAE04E@xxxxxxxxxxxxxxxx
Thanks for prompt reply.

I would appreciate if you could verify the registry settings.

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Documents and Settings\\system.hv"
"ProfileDir"="Documents and Settings"
"Start DevMgr"=dword:1
"Flags"=dword:3

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\MYFSD]
"FriendlyName"="MYFSD"
"Dll"="MYFSD.dll"
"BootPhase"=dword:0
"LoadFlags"=dword:1 ; 1:load synchronously 2:load asynchronously

; END HIVE BOOT SECTION

I am glad to know about PSM. In our case. FSDMGR does load the
MYFSD.
Either I am missing load order or some functionality.

Thanks!



"Paul G. Tobey [eMVP]" wrote:

You can use the hive registry with any storage device. Reading
back
probably indicates that you are not mounting the filesystem
properly
during
startup. I'm using Intel's Persistent Storage Manager, which
doesn't
use
FAT, and it works fine.

Paul T.

"JAM" <JAM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EBE2226E-9374-4155-B318-34FE761DAF87@xxxxxxxxxxxxxxxx
Hi!
Can I use hive functionality with self made flash file system ?
Flash File System is autoloaded using FSDMGR.
There is "NO" block driver. I use Flash File System driver with
self
made
NAND read/write routines. I have implemented all functions
required
by
File
System.

I am able to save Hive registry but not able to read back on
reboot.

Is it possible to use hive registry with any other file system
then
FAT?



















.

Relevant Pages

  • Re: [PATCH] LogFS take three
    ... but for real long-term storage it's really a bad idea. ... For example, removing flash card ... the problems with the underlying FTL continuing to keep (and copy around ... However, as the demand for capacity, reliability and high performance ...
    (Linux-Kernel)
  • Re: Question about Flash + Law
    ... have heard anything and everything when it comes to flash. ... Now days you better have at least type 4 storage and if you really want to ... going to shoot your stuff off. ... tubes that either burn slowly with a very bright light (Green, ...
    (rec.pyrotechnics)
  • Re: Invisible USB
    ... It's possible your flash drive lost its drive assignment letter. ... Access Disk ... > under 'USB controllers', and described as working properly in the status ... > manager troubleshooter right the way through to uninstalling the USB ...
    (microsoft.public.windowsxp.hardware)
  • Re: Nvram write modes and problems
    ... attached devices like them are non-volatile *storage*. ... If you make a distinction based on ease of write then flash ... becomes non-volatile storage rather than memory. ... too different from actual RAM to be called NVRAM. ...
    (comp.arch.embedded)
  • Re: A very unique new camcorder !!
    ... This camcorder stores its' recordings on either a hard disk or Flash ... In essense post-shoot storage is a massive and currently unsolvable ... hard drives" anything but deeply stupid. ... thousand gallons of popcorn a second. ...
    (rec.video.production)