Re: TFAT stability

Yes, the flash modifying is the issue here, but why? I have tried to remove
the registry hives from the flash to RAM and now my filesystem crushes, but
at least the platform boot itself (ethernet is working etc.). All files are
missing on my storage card (we are using Intel StrataFlash J3). I have also
tried to make two partitions, both with files written to them. In normal
operation the application is only on the first patiition and all the wriiting
and reading is done to that partiion. After crash, only files on this
partition are missing. The second one is ok.

Do I have some registry settings wrong for the TFAT or is it something else?
I have check the newsgroups and it seems to me that a lot of folks are having
this kind of problems. But there is no solution proposed except for "UPS
kind" of backup during power down. This is not an option for us. Microsoft
also said that TFAT is safe and stable. Ok, there could be an issue with the
msflash strata driver, but that is also supplied by them. So, where is the
catch? I' ve ruled out the hardware problem, because there is the consistency
about filesystem crash. If it would be hardware then there would be problems
with image and bootloader too and not with filesystem only.

Thanks, Jernej

"Bruce Eitman (eMVP)" wrote:

> I have also seen these failures on a few platforms, both CE 4.2 and 5.0. I
> think that it has a lot to do with background compaction and removing power
> while the flash is being modified.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
>
> "turnsek" <turnsek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A6C143B2-6D21-49DF-8F05-B5950ECE3A2A@xxxxxxxxxxxxxxxx
> > Hi all!
> >
> > We have PXA255 based platform with WCE42 and we are testing stability of
> the
> > platform. Our hardware is not battery backed and we rely on powerdown
> driver
> > and TFAT file system. We have noticed that after number of power down and
> > power up cycles (quite a lot) our platform dies. We have flash resident
> > persistent registry (hive based). Platform could not start anymore. I am
> > suspecting that the file-system is corrupted (so the registry too). We are
> > using msflash strata driver.
> > Our settings are:
> >
> > [HKEY_LOCAL_MACHINE\System\StorageManager]
> > "Dll"="fsdmgr.dll"
> > "PNPUnloadDelay"=dword:0
> >
> > ; @CESYSGEN IF CE_MODULES_STRATAD
> > ; HIVE BOOT SECTION
> > ; StrataFlash block driver.
> > [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD]
> > "Dll"="stratad.dll"
> > "Order"=dword:2
> > "Prefix"="DSK"
> > "Ioctl"=dword:4
> > "Profile"="MSFlash"
> > "IClass"="{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
> > "MemBase"=dword:b9300000
> > "MemLen"=dword:03000000
> > "Flags"=dword:1000
> >
> > ; Override names in default profile
> > [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash]
> > "Name"="MSFLASH for STRATAFLASH"
> > "Folder"="Storage Card"
> >
> > [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles]
> > "AutoMount"=dword:1
> > "AutoPart"=dword:1
> > "AutoFormat"=dword:1
> >
> > ; Keep FATFS from trying to shadow \Windows
> > [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
> > "MountFlags"=dword:2
> >
> > [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\MSFlash]
> > "DriverPath"="Drivers\\BuiltIn\\StrataFMD"
> > "LoadFlags"=dword:1
> > "Order"=dword:0
> >
> > ; END HIVE BOOT SECTION
> > ; @CESYSGEN ENDIF CE_MODULES_STRATAD
> >
> >
> > ; @CESYSGEN IF FILESYS_FSREGHIVE
> > ; HIVE BOOT SECTION
> > [HKEY_LOCAL_MACHINE\init\BootVars]
> > "SYSTEMHIVE"="Registry\\system.hv"
> > "PROFILEDIR"="Registry"
> > "Start DevMgr"=dword:1
> > "DefaultUser"="Iskraemeco"
> > ;Causing some debugchk's in debug version,
> > ;performance monitoring tools doesn't work.
> > ;RegistryFlags"=dword:1
> > ; END HIVE BOOT SECTION
> > ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
> >
> > [HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
> > "FriendlyName"="FAT FileSystem"
> > "Dll"="fatfsd.dll"
> > ;"Flags"=dword:00000024
> > "Flags"=dword:007C0028
> > "Paging"=dword:1
> > "EnableCache"=dword:1
> > "CacheSize"=dword:0
> > "Util"="fatutil.dll"
> > "FormatTfat"=dword:1
> > ; END HIVE BOOT SECTION
> > ; @CESYSGEN ENDIF CE_MODULES_FATFSD
> >
> >
> > Any help would be more then welcome.
> >
> > Thanks, Jernej
> >
>
>
>
.

Relevant Pages

  • Hive-Based Registry Settings
    ... I want to store registry hives on compact flash. ... ; END HIVE BOOT SECTION ... ; @CESYSGEN ENDIF FILESYS_FSREGHIVE ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Not able to understand Hive registry
    ... short - don't just look in your persistent store and assume that a lack of a ... hive file means that the Hive registry is not implemented/enabled. ... the hives are deleted and new hives are created. ... In my platform.reg i do see few registry marked with HIVE BOOT ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Hive based registry in IXDP425
    ... Also Make sure that initialization registry for your flash ... ; END HIVE BOOT SECTION ... and the order of the driver getting load should be 0. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Hive based registry problem...
    ... I have included the following drivers for my flash to work. ... I want to store the registry in Flash partition. ... hive between;HIVE BOOT SECTION tags? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Troubleshooting the flash driver loading
    ... I have included the catalog item in my OS design. ... ; END HIVE BOOT SECTION ... Do you think I should add/remove some more registry items under "HIVE BOOT ... I am seeing that after loading nk.exe, WinCE is trying to load the flash ...
    (microsoft.public.windowsce.embedded)