Re: mounting external file system as root - filesys crash

Tech-Archive recommends: Speed Up your PC by fixing your registry

Have you tried to use RAM Disk and/or RAMFMD first for mounting as root FS??
And if you are using Have-based registry, make sure including proper
registry setting in Boot-Hive sections.

"AJM42" <software@xxxxxxxxxxxxxx>
???????:1159185132.469246.236490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In trying to answer my previous post about mapping \Program Files to
the MMC card, I hit upon using the capability in CE5 to map the
external file system as the root filing system.

So I set the filing system to ROM only (not RAM+ROM)
added these registry entries:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MMC]
"Name"="MMC Card"
"Folder"="Storage Card"
"MountAsBootable"=dword:1
"MountAsRoot"=dword:1

and did a clean-sysgen.
But on bootup I get an exception

294769908 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!MountDisk:
BPB_HiddenSectors(1) != 0
4294769910 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume:
access time updates disabled
4294769911 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume: event
logging enabled
4294769911 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume:
automatic scanning disabled
4294769912 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume: write
verify disabled
4294769913 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume: extra
FAT on format disabled
4294769913 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume: force
write through enabled
4294769915 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume:
Codepage = 1
4294769916 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!OpenVolume:
Number of path cache entries = 50
4294769929 PID:3fc3596 TID:43fa8fda 0x83fc64e4: >>> Loading module
diskcache.dll at address 0x03E30000-0x03E39000 (RW data at
0x01FF0000-0x01FF04F4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\USER\RELDIR\HSERIES_ARMV4I_DEBUG\DISKCACHE.DLL'
4294769972 PID:3fc3596 TID:43fa8fda 0x83fc64e4: CreateCache:
Successful. Cache Size: 122 KB, Start: 6, End: 495.
4294769973 PID:3fc3596 TID:43fa8fda 0x83fc64e4: CreateCache:
Successful. Cache Size: 245 KB, Start: 496, End: 250877.
4294770159 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!InitVolume: FAT
version: 16
4294770159 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FATFS!InitVolume:
Cluster Size (Sectors): 4
4294770163 PID:3fc3596 TID:43fa8fda 0x83fc64e4: FS: Mounting external
volume Storage Card as file system root
4294770163 PID:3fc3596 TID:43fa8fda 0x83fc64e4: Data Abort:
Thread=83fc64e4 Proc=832bc710 'filesys.exe'
4294770164 PID:3fc3596 TID:43fa8fda 0x83fc64e4: AKY=00000003
PC=0001fd64(filesys.exe+0x0000fd64) RA=0001fd30(filesys.exe+0x0000fd30)
BVA=0408b064 FSR=0000000f

Guess I've missed something critical.
I saw another post reporting this same exception but there was no
response.
Anyone any ideas now?



.

Relevant Pages

  • Re: Saving Objectstore to a WinCE OS device
    ... ANY filesystem can be used. ... It should indicate that this particular registry key is deprecated, ... the registry and mount it as the root and you'll be 80% of the way ... I thought when you mentioned File system that you was refering to ...
    (microsoft.public.windowsce.embedded)
  • Rom-only file system
    ... I have a VIA EPIA ME6000 system with ATA flash disk running CE5.0. ... I have a problem when I switch from RAM and ROM file system to ROM only file ... FS: Populating root file system... ... maybe I need to change a registry setting somewhere? ...
    (microsoft.public.windowsce.platbuilder)
  • Hive based registry over block driver boot problem [CE 5.0]
    ... I have a problem with hive based registry in my platform.... ... FileSystem Starting - starting with clean file system ... 0x83fc70cc: FSVOL: Volume heap already initialized ... 0x83fc70cc: FILESYS: Restarting storage manager. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: what to do about "cannot dump to dumpdev hd(1/41): space for
    ... smoke out anything that would point to root being there. ... whole disk division and maybe boot but nothing else. ... I've see that before when a client used Microlite Backup ... alter the file system and log its results to /tmp/logfsck. ...
    (comp.unix.sco.misc)
  • Re: Hive based registry over block driver boot problem [CE 5.0]
    ... I have a problem with hive based registry in my platform.... ... FileSystem Starting - starting with clean file system ... 0x83fc70cc: FSVOL: Volume heap already initialized ... 0x83fc70cc: FILESYS: Restarting storage manager. ...
    (microsoft.public.windowsce.platbuilder)