Re: NO Flash - TFAT file system integration

Hi Henrik,

thanks a lot for your answers.

Henrik Viklund wrote:
Geez, Alexander! That's a LOT of questions! Next time, try splitting
them up into a couple of post, and I think you'll have better luck
getting them answered. Just to answer a few of your questions:


jejeje, I thought about it but I thought that I could get a "why are
you creating separated threads to ask about the same topic!" ;-)

In the meantime, I tested integrating the Hive-based registry and it
seems to be working fine.

I also plugged some USB memory sticks and I saw that the applet in the
control panel shows wrong Capacity values also. It is this a known
error in this applet or am I missing something? I just want to know
that this behavior is "normal" because if it somehow is overlapping
with the kernel or boot loader areas then in the future I could meet
bugs very hard to track...

I can't modify the mapping because in MIPS architecture the vector
reset is fixed. So, I have to flash the Boot loader there...I have
another board with less flash memory, that is the reason I would like
to use this part as storage too.


Question: that is my current state. Is it Ok what I did?

The only thing you might want to try is to remove the "AutoLoad"
section. "AutoLoad" entry in Storage Manager is usually only used to
load stand-alone (monolitic) drivers. Since you put the block driver
under "BuiltIn" the block driver is allready automatically loaded by
device.exe at startup. Since you have specified the block driver guid
IClass the storage manager will be notified when the driver loads and
it in turn will set up everything else that is defined by its Profile.


Great, I will give it a try.

Q: is there a way that I can include in the storage area the upper 3 MB
(4)?
No, at least not without using multiple partitions. What you can do is
shift things around in the flash to creata a large continous flash file
system area.


Ok, anyway I think that I will need to use multiple partitions if I add
the BinFS. I'm still blocked understanding this part. I don't see what
are the adventages to use the BinFS file system.

Now I'm checking some registry settings that could be useful. For
example:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash]
"Name"="MSFLASH for FASL FLASH"
"Folder"="NOR Flash"

;Automatically Mounts each detected partition (if FSD driver is
available)
; "AutoMount"=dword:1
;Automatically partitions the store with largest creatable
partition (???)
; "AutoPart"=dword:1
;Formats the store automatically
; "AutoFormat"=dword:1

As far as I know, with them I can do the formating and/or handling of
partition (?) after (the first) booting, so I would avoid to do it
manually (as I did it above).
Q: Am I right? It would be very useful in mass production.

Yes.

Great. But I have to define in advance the partitions and the
corresponding file system for them. Would it be done (in my case) in
the registry file creating new profiles (reusing the same FMD block
driver) giving the corresponding 'MemBase' and 'MemLen' for each area?

If that is the case, then I don't see (clearly) the adventage of
integrating the BOOTPART library in the boot loader. Maybe to allow the
end user to create subpartition or for defining the partitions without
the puzzle in the registry (?)...


For the 'HIVE BOOT SECTION' tag, I don't get the concept of using it
for "starting drivers in the first boot phase...". May anybody explain
me that, please?
When using hive based registry, you need to load it from some sort of
persistant storage, right? Since you need information from the registry
on where to find the registry hive, what block driver and partition
driver etc. to load, you can't store that information in the hive based
part of the registry, because it has not yet been loaded. So, what the
HIVE BOOT SECTION tag denotes is that this part of the registry won't
be part of the hive, but will be present at startup, before actually
having loaded the registry hive.


Thanks! It is clear now and as I stated above, it seems to be working.

Henrik Viklund
http://www.addlogic.se

.

Relevant Pages

  • IRC Packets being generated. Dont know where from...
    ... *Registry value not found* ... Autorun entries from Registry: ... Enumerating ICQ Agent Autostart apps: ... RAS Asynchronous Media Driver: System32\DRIVERS\asyncmac.sys (manual ...
    (microsoft.public.security.virus)
  • hijack this startup - can someone tell me the hack i am experienci
    ... *Registry value not found* ... Enumerating ICQ Agent Autostart apps: ... Intel82801 Audio Driver Install Service: ... Application Management: %SystemRoot%\system32\svchost.exe -k netsvcs (manual ...
    (microsoft.public.windowsxp.security_admin)
  • Re: BSOD Error 0x000000B8
    ... *Registry value not found* ... Enumerating ICQ Agent Autostart apps: ... ADI UAA Function Driver for High Definition Audio Service: ... Application Management: %SystemRoot%\system32\svchost.exe -k netsvcs ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: hijack this startup - can someone tell me the hack i am experienci
    ... | *Registry key not found* ... | *Registry value not found* ... | Autorun entries from Registry: ... | Intel82801 Audio Driver Install Service: ...
    (microsoft.public.windowsxp.security_admin)
  • 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)