off load nk.bin to msystem DOC

hello,
currently I am making my nk.bin a ram based image, and I load it from mdoc
to ram in eboot and run everything in RAM.
I am thinking about to make my nk.bin smaller by moving driver/application
files to msystem DOC fat partition. and the system load them from disk as
needed.
in this case...
1 compared with NOR flash I lose XIP, ram usage is going down from pure ram
image anyway
2 files stored in fat partition is freely copy-able!!
3 I have to give up the bib files and gather needed files on my own.
4 app start up time is slower
is there anyone who has experience on this? or is a ce pc similar in the
case(harddisk vs msystem DOC chip) ? and how about the CE license? do I have
to protect the system (ms) files from being copyied out of the device?

Dean
Thu Feb 09 08:15:07 CST 2006

This is a supported alternative. The way to accomplish this is to make the
MDOC filesystem root, and have it shadow the Windows directory. You just
need enough components in your nk.bin to get the operating system to boot
and mount the filesystem. It then up to you to populate the filesystem with
the components you are interested in.

Another alternative is to use the BINFS file system. That will allow you to
keep everything in nk.bin, but page in components as needed. This way you
don't have to copy the entire OS to RAM at once.

See PB documentation for more details on both options.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"mobilevil" <mobilevil@mobile.com> wrote in message
news:%23iQ2nwULGHA.3408@TK2MSFTNGP12.phx.gbl...
> hello,
> currently I am making my nk.bin a ram based image, and I load it from mdoc
> to ram in eboot and run everything in RAM.
> I am thinking about to make my nk.bin smaller by moving
> driver/application files to msystem DOC fat partition. and the system load
> them from disk as needed.
> in this case...
> 1 compared with NOR flash I lose XIP, ram usage is going down from pure
> ram image anyway
> 2 files stored in fat partition is freely copy-able!!
> 3 I have to give up the bib files and gather needed files on my own.
> 4 app start up time is slower
> is there anyone who has experience on this? or is a ce pc similar in the
> case(harddisk vs msystem DOC chip) ? and how about the CE license? do I
> have to protect the system (ms) files from being copyied out of the
> device?
>
>
>

mobilevil
Fri Feb 10 01:59:00 CST 2006

what do you mean by shadowing the windows directory?
making the mdoc as root file system, and make a \windows folder in the root?
do i have to copy the files in windows folder? what's the min where can I
find documentation about it? i can only find limited binfs stuff in msdn.

"Dean Ramsier" <ramsiernospam@nospam.com> wrote in message
news:exUG7MYLGHA.1028@TK2MSFTNGP11.phx.gbl...
> This is a supported alternative. The way to accomplish this is to make
> the MDOC filesystem root, and have it shadow the Windows directory. You
> just need enough components in your nk.bin to get the operating system to
> boot and mount the filesystem. It then up to you to populate the
> filesystem with the components you are interested in.
>
> Another alternative is to use the BINFS file system. That will allow you
> to keep everything in nk.bin, but page in components as needed. This way
> you don't have to copy the entire OS to RAM at once.
>
> See PB documentation for more details on both options.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation
>
>
> "mobilevil" <mobilevil@mobile.com> wrote in message
> news:%23iQ2nwULGHA.3408@TK2MSFTNGP12.phx.gbl...
>> hello,
>> currently I am making my nk.bin a ram based image, and I load it from
>> mdoc to ram in eboot and run everything in RAM.
>> I am thinking about to make my nk.bin smaller by moving
>> driver/application files to msystem DOC fat partition. and the system
>> load them from disk as needed.
>> in this case...
>> 1 compared with NOR flash I lose XIP, ram usage is going down from pure
>> ram image anyway
>> 2 files stored in fat partition is freely copy-able!!
>> 3 I have to give up the bib files and gather needed files on my own.
>> 4 app start up time is slower
>> is there anyone who has experience on this? or is a ce pc similar in the
>> case(harddisk vs msystem DOC chip) ? and how about the CE license? do I
>> have to protect the system (ms) files from being copyied out of the
>> device?
>>
>>
>>
>
>

Henrik
Fri Feb 10 02:46:25 CST 2006

Search the help for "Mounting an Installable File System as the Root
Directory".

Henrik Viklund

Dean
Fri Feb 10 08:01:57 CST 2006

There isn't much information on binfs. It's complicated, and brings up a
number of issues.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"mobilevil" <kccheng@kachun-youknowwhat.com> wrote in message
news:uV8lufhLGHA.2812@TK2MSFTNGP14.phx.gbl...
> what do you mean by shadowing the windows directory?
> making the mdoc as root file system, and make a \windows folder in the
> root? do i have to copy the files in windows folder? what's the min where
> can I find documentation about it? i can only find limited binfs stuff in
> msdn.
>
> "Dean Ramsier" <ramsiernospam@nospam.com> wrote in message
> news:exUG7MYLGHA.1028@TK2MSFTNGP11.phx.gbl...
>> This is a supported alternative. The way to accomplish this is to make
>> the MDOC filesystem root, and have it shadow the Windows directory. You
>> just need enough components in your nk.bin to get the operating system to
>> boot and mount the filesystem. It then up to you to populate the
>> filesystem with the components you are interested in.
>>
>> Another alternative is to use the BINFS file system. That will allow you
>> to keep everything in nk.bin, but page in components as needed. This way
>> you don't have to copy the entire OS to RAM at once.
>>
>> See PB documentation for more details on both options.
>>
>> --
>> Dean Ramsier - eMVP
>> BSQUARE Corporation
>>
>>
>> "mobilevil" <mobilevil@mobile.com> wrote in message
>> news:%23iQ2nwULGHA.3408@TK2MSFTNGP12.phx.gbl...
>>> hello,
>>> currently I am making my nk.bin a ram based image, and I load it from
>>> mdoc to ram in eboot and run everything in RAM.
>>> I am thinking about to make my nk.bin smaller by moving
>>> driver/application files to msystem DOC fat partition. and the system
>>> load them from disk as needed.
>>> in this case...
>>> 1 compared with NOR flash I lose XIP, ram usage is going down from pure
>>> ram image anyway
>>> 2 files stored in fat partition is freely copy-able!!
>>> 3 I have to give up the bib files and gather needed files on my own.
>>> 4 app start up time is slower
>>> is there anyone who has experience on this? or is a ce pc similar in the
>>> case(harddisk vs msystem DOC chip) ? and how about the CE license? do I
>>> have to protect the system (ms) files from being copyied out of the
>>> device?
>>>
>>>
>>>
>>
>>
>
>