Hi,all,

We have a very strange problem.

The following is the configuartion of our platform:
CPU:pxa270
flash:32MB
SDRAM:64MB
display hardware: intel 2700G

Let me detail the problem:
Our previous OS design has ROM-only file catalog.When we download the nk.bin
to target device,it has the following output:

4294776940 PID:43d49426 TID:43e1b002 0x83d394b8: >>> Loading module ws2.dll
at address 0x03B10000-0x03B24000 (RW data at 0x01FC3000-0x01FC3B24)
4294776943 PID:43d49426 TID:43e1b002 0x83d394b8: >>> Loading module
services.exe at address 0x0E010000-0x0E027000
Loaded symbols for
'D:\SOURCE_CODE\WINCE500\PBWORKSPACES\WINDOWTV\RELDIR\WINDOWTV_ARMV4I_DEBUG\SERVICES.EXE'
4294776992 PID:23d50f7e TID:23fb6ce6 0x83d50d3c: <<< Unloading module
oleaut32.dll at address 0x03210000-0x03261000 (RW data at
0x01F47000-0x01F47F04)
Unloaded symbols for
'D:\SOURCE_CODE\WINCE500\PBWORKSPACES\WINDOWTV\RELDIR\WINDOWTV_ARMV4I_DEBUG\OLEAUT32.DLL'
4294776996 PID:23d50f7e TID:23fb6ce6 0x83d50d3c: <<< Unloading module
ceshell.dll at address 0x02BB0000-0x02C25000 (RW data at
0x01F0A000-0x01F0B380)

It downloads some modules,then unload.And it can not display anything.

When We Remove ROM-only file system,it works fine and can display.Everything
is perfect.


We find in winceos.bat that the default internal file system is RAM and ROM
file system.It means if we remove ROM-file system,ROM and RAM file system
exists in our OS design.

We search in Help doc and only find this file
(ms-help://MS.WindowsCE.500/wcedata5/html/wce50conSelectingtheInternalFileSystemforyourDevice.htm).
And the only difference is that ROM-only file system does not allow
applications to place files in the object store.

But this is not enough to explain the problem.
Could some one give some suggestions?

Thanks in advance.

--
Best Wishes
Wang Yeqing
***********************************************************
Intelligent Grouping Research and Development Institute
Amoi Electronics Co., Ltd

Tel: 86-592-6516777-6523
***********************************************************

Re: about internal file system by Wang

Wang
Mon Jan 31 06:05:26 CST 2005

Has some one faced this problem?
Could some one give some suggestions?
"Wang Yeqing" <wangyq@amoi.com.cn> дÈëÏûÏ¢ÐÂÎÅ:ed7BKwzBFHA.2032@tk2msftngp13.phx.gbl...
> Hi,all,
>
> We have a very strange problem.
>
> The following is the configuartion of our platform:
> CPU:pxa270
> flash:32MB
> SDRAM:64MB
> display hardware: intel 2700G
>
> Let me detail the problem:
> Our previous OS design has ROM-only file catalog.When we download the
> nk.bin to target device,it has the following output:
>
> 4294776940 PID:43d49426 TID:43e1b002 0x83d394b8: >>> Loading module
> ws2.dll
> at address 0x03B10000-0x03B24000 (RW data at 0x01FC3000-0x01FC3B24)
> 4294776943 PID:43d49426 TID:43e1b002 0x83d394b8: >>> Loading module
> services.exe at address 0x0E010000-0x0E027000
> Loaded symbols for
> 'D:\SOURCE_CODE\WINCE500\PBWORKSPACES\WINDOWTV\RELDIR\WINDOWTV_ARMV4I_DEBUG\SERVICES.EXE'
> 4294776992 PID:23d50f7e TID:23fb6ce6 0x83d50d3c: <<< Unloading module
> oleaut32.dll at address 0x03210000-0x03261000 (RW data at
> 0x01F47000-0x01F47F04)
> Unloaded symbols for
> 'D:\SOURCE_CODE\WINCE500\PBWORKSPACES\WINDOWTV\RELDIR\WINDOWTV_ARMV4I_DEBUG\OLEAUT32.DLL'
> 4294776996 PID:23d50f7e TID:23fb6ce6 0x83d50d3c: <<< Unloading module
> ceshell.dll at address 0x02BB0000-0x02C25000 (RW data at
> 0x01F0A000-0x01F0B380)
>
> It downloads some modules,then unload.And it can not display anything.
>
> When We Remove ROM-only file system,it works fine and can
> display.Everything is perfect.
>
>
> We find in winceos.bat that the default internal file system is RAM and
> ROM file system.It means if we remove ROM-file system,ROM and RAM file
> system exists in our OS design.
>
> We search in Help doc and only find this file
> (ms-help://MS.WindowsCE.500/wcedata5/html/wce50conSelectingtheInternalFileSystemforyourDevice.htm).
> And the only difference is that ROM-only file system does not allow
> applications to place files in the object store.
>
> But this is not enough to explain the problem.
> Could some one give some suggestions?
>
> Thanks in advance.
>
> --
> Best Wishes
> Wang Yeqing
> ***********************************************************
> Intelligent Grouping Research and Development Institute
> Amoi Electronics Co., Ltd
>
> Tel: 86-592-6516777-6523
> ***********************************************************
>
>



Re: about internal file system by Steve

Steve
Mon Jan 31 09:08:07 CST 2005

There isn't enough information about what is happening to determine what the
problem is. Carefully review ALL of the debug output as there is likely more
information in other parts of the output that can help identify the problem.
Best guess is that some part of the system (either MS or your own) NEEDS the
RAM FS or an externally mounted system as the root of the File system. if
you don't include RAMFS and don't mount an external FS you basically have no
file write capabilities in the system.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: about internal file system by DongFang

DongFang
Mon Jan 31 19:08:25 CST 2005

Hi,

Actually, the problem is after load explorer.exe,service.exe will be
loadded.
then unloading explorer.exe message will output on the debug windows without
any other errors message.

we are debugging wince now, so our selection is download nk.bin to SDRAM.Is
this
have some influence on the selection of internal file system? or
services.exe
don't support ROM-only file system?

could you make an clear explanation about distinguish between two file
system?
In which condition should we use ROM-only? which use RAM and ROM file
system?

DongFang Tian
********************************************************
Intelligent Grouping Research and Development Institute
Amoi Electronics Co., Ltd
********************************************************
"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> дÈëÏûÏ¢ÐÂÎÅ:%23afowa6BFHA.3524@TK2MSFTNGP15.phx.gbl...
> There isn't enough information about what is happening to determine what
> the problem is. Carefully review ALL of the debug output as there is
> likely more information in other parts of the output that can help
> identify the problem. Best guess is that some part of the system (either
> MS or your own) NEEDS the RAM FS or an externally mounted system as the
> root of the File system. if you don't include RAMFS and don't mount an
> external FS you basically have no file write capabilities in the system.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>



Re: about internal file system by Steve

Steve
Tue Feb 01 08:17:50 CST 2005

if you don't build the system such that you have a writeable file system
ANYTHING that expects one will fail. So you either need to include the RAMFS
(which will include the ROMFS - ROMFS is ALWAYS there no matter what you
select) or mount an external file system as the root of the file system for
writing files to that.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com