Re: Allocating Internal Flash as Root

Tech-Archive recommends: Fix windows errors by optimizing your registry

Ok, I have the Flash loading and showing up as a drive on my system. I
have set all the registry settings that I could find in the help
documentation to tell it to mount as the root file system.

How do I tell if it is working? If I create a folder under any of the
standard places (like My Docments) the folder disappears the next time
I boot up the system. Could this be because I am loading, running and
debugging from ram instead of flashing the unit and then trying it? Is
this the right way to verify it?

I looked into the registry and I have the following entries actually
in the file system:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NandFlash]
"Dll"="nandfcd.dll"
"Order"=dword:0
"Prefix"="DSK"
"Profile"="FlashDisk"
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"FriendlyName"="i.MX21 NAND FLASH Driver"

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"Name"="i.MX21 NAND FLASH"
"Folder"="NAND Flash"
"DefaultFileSystem"="FATFS"
"AutoMount"=dword:1
; Auto part and format disk if no partitions are present.
; WARNING! This can cause long boot times when encountering a
fresh disk.
"AutoPart"=dword:1
"AutoFormat"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
; Override common setting to enable automatic formatting of
unformatted volumes
"Flags"=dword:00000024

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\Nandfcd]
"DriverPath"="Drivers\\BuiltIn\\NandFlash"
; LoadFlags 0x01 == load synchronously
"LoadFlags"=dword:1
"BootPhase"=dword:0
; Note: if BinFS is used together with PS, then should ensure
; this is loaded after BinFS by setting order to 1 and that
; BinFS autoload order is 0.
"Order"=dword:0

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
; System registry in FATFS partition
"MountAsBootable"=dword:1
; To mount FAT partition as root
"MountAsRoot"=dword:1

Notice the MoustAsRoot setting and all.

I looked through the debug log and didn't see any errors. The only
thing I saw that stood out was:

8993 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module
fatfsd.dll at address 0x03E40000-0x03E6B000 (RW data at
0x01FF2000-0x01FF263C)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATFSD.DLL'
9005 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module
fatutil.dll at address 0x03E10000-0x03E27000 (RW data at
0x01FED000-0x01FEE0E8)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATUTIL.DLL'
9009 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New extended boot sector successfully written
9508 PID:bfc44ee TID:bfc44ca 0x8bfc4288:
FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't
exist for logical sector 0x200!!!
10002 PID:bfc44ee TID:bfc44ca 0x8bfc4288:
FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't
exist for logical sector 0x400!!!
10033 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New FAT #0 successfully written
10034 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New root directory successfully written
10036 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New BPB successfully written
10036 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume
complete.
10037 PID:bfc44ee TID:bfc44ca 0x8bfc4288: <<< Unloading module
fatutil.dll at address 0x03E10000-0x03E27000 (RW data at
0x01FED000-0x01FEE0E8)
Unloaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATUTIL.DLL'

It seems to be formatting the drive when it boots. The only thing that
doesn't make sense if that is true is that if I create a folder
directly on the drive that is created (NAND Flash) it remains. So if I
create a folder on that drive it stays, but if I create a folder in
one of the standard folders they go away when I reboot.

Help?


.

Relevant Pages

  • Re: Windows XP crash
    ... much rather just copying the Document and Setting folder to the USB ... Second, if I get one of these boot CDs, and can get to the DOS ... a Windows password on the machine but no boot password. ... if I elect to repair the registry by replacing it with an older ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Yea almost
    ... I get an open folder called Microsoft with a folder called Office Live. ... Right click on the programs icon in the Notification Area to see if there is an option to disable it from loading on boot. ... Look in the Registry under these keys to either remove the entry or comment it out to disable it from loading on boot: ... Always backup the registry or any key before making any changes so that you may import the keys back in should anything go wrong. ...
    (microsoft.public.windowsxp.general)
  • Re: Fixing a corrupt Windows Registry with Ubuntu (Linux)
    ... the reason a full System Restore is recommended after successful boot. ... If that fails, try F8 and a Safe Mode boot, then System Restore. ... There is also a way to use a functining system to inspect/edit a registry ... folder to get the name of the Restore Point folder. ...
    (misc.news.internet.discuss)
  • Re: I think I have virus after all....
    ... Compare the two lists. ... but not the hidden registry entries. ... folder is one good way to find these babies too. ... mismatch between Windows API and raw hive data. ...
    (rec.games.computer.ultima.dragons)
  • Re: Text of KB Article Included - From error to missing system file
    ... This article describes how to recover a Windows XP system that does not start because of corruption in the registry. ... If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives. ... In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. ...
    (microsoft.public.windowsxp.general)