Windows XPe with .NET - How small can you get it?

[Guest]

Hi.

I'm building a Digital Picutre frame out of an old Dell Inspiron 7500
laptop. I've replaced the 2.5" IDE Hard Drive with a Compact Flash to 2.5"
IDE adapter, so the computer got a 256MB hard drive at the moment. The CPU is
a 500mhz PIII, and it has 128MB of RAM.

I was wondering how small it is possible to get a Windows XPe image running
..NET Framework 1.1. I've managed to get it down to 220MB, but once i boot it
get an out of memory error whent the first boot agent runs. I've tryed using
the remaining 30MB for paging file, but it's obvious not big enough.

Do you think buying a 512MB card and increasing the paging file size is the
solution? Will the memory usage of the computer drop once first boot agent is
runned? If my computer is depending on a paging file to run, write protecting
the CF card using Enhanced Write Filter is out of the question?

Is it possible to install .NET Compact Framework on Windows XP instead of
the full framework?

 

[KM]

Jonas,

I'm building a Digital Picutre frame out of an old Dell Inspiron 7500
laptop. I've replaced the 2.5" IDE Hard Drive with a Compact Flash to 2.5"
IDE adapter, so the computer got a 256MB hard drive at the moment. The CPU is
a 500mhz PIII, and it has 128MB of RAM.

I was wondering how small it is possible to get a Windows XPe image running
.NET Framework 1.1. I've managed to get it down to 220MB, but once i boot it
get an out of memory error whent the first boot agent runs. I've tryed using
the remaining 30MB for paging file, but it's obvious not big enough.

Since currently .Net Framwork "depends" on Winlogon, you will unlikely be able to minimaze the image footprint much :-(

Do you think buying a 512MB card and increasing the paging file size is the
solution? Will the memory usage of the computer drop once first boot agent is
runned? If my computer is depending on a paging file to run, write protecting
the CF card using Enhanced Write Filter is out of the question?

Extending RAM would definitely help.
However, if you have (or plan to have) CF as your target storage I would not recommned you enabling pagefile. Having the pagefile on
unprotected CF area would wear it out very fast. Having the pagefile with EWF enabled is also a bad idea becuase they don't live
together well.

Is it possible to install .NET Compact Framework on Windows XP instead of
the full framework?

No, .NetCF is not avaiable on Desktop. (or at least it used to be the case)

 

[Guest]

Hmm..

Okey, so basicly these are my options:
a) add more memory (will 256MB of ram be enough for a WinXP + .NET image?)
b) use a 512MB memory card with paging file, but with reduced life span
c) get a more quiet 2.5" IDE disk
d) use Windows CE and .NET CF instead of Windows XPe (is this possible on a
regular laptop? booting from IDE device?)
e) learn some C++ and write a simple image application in native code
f) install VB6 runtime and write a VB6 application to display images?
g) just make the slide shows a web page and install a simple image with IE
and point it to a URL to display pictures

at first glance option d, e and f are most tempting. what do you guys think?

 

[KM]

Jonas,

Okey, so basicly these are my options:
a) add more memory (will 256MB of ram be enough for a WinXP + .NET image?)

Considering how RAM is cheap these days I'd go with this option if I want to stick with XPe.
I can't tell you if 256M is enough for your image since I never saw it but I'd think it is from my previous playing with "big"
images.
It will all come to the testing of the image on the final hardware.

b) use a 512MB memory card with paging file, but with reduced life span

Not good option since you may end up dealing with much of support issues after you deploy the devices.

c) get a more quiet 2.5" IDE disk

I think this is much more expensive option than a).

d) use Windows CE and .NET CF instead of Windows XPe (is this possible on a
regular laptop? booting from IDE device?)

CE is good option here, especially considering it's licence pricing
CEPC BSP is what you asked for.

However, please keep in mind that .NetCF is way too restricted vs .Net Full Frammework (in my personal opinion - .NetCF sucks).
But there will be alternatives for you like OpenNETCF (www.opennetcf.org).

e) learn some C++ and write a simple image application in native code

The best option here for any OS you choose

f) install VB6 runtime and write a VB6 application to display images?

The worse option here for any OS you choose unless you want to save some money on development hours.

g) just make the slide shows a web page and install a simple image with IE
and point it to a URL to display pictures

Depending on the "slide show" implementation this may or may not be a good option. Is it ASP based or else? HTML/DHTML? How complex
the content and the code? What is the network connection quality for your devices? Will the content be on Interanet, Extranet or
Internet? Etc.
These are only some of the questions you shuold ask yourself before going by this route.

at first glance option d, e and f are most tempting. what do you guys think?

See my comments above.
There are too many factors of your environment (budget, development time, licencing, developer availability, personal preferences,
etc.) that I do not know about but that will [should] have a big influence on your decision.

KM

 

[Guest]

Thanks for great reply.

First of, this is a personal experimental project, not commercial. So
licencing, support/development time is not that important.

I think the first thing I'm going to try is replacing one of the 64MB memory
modules with a 128MB spare module i have laying around. This will give me 192
instead of 128MB ram. Hopefully this will be enough to boot Win XPe with out
enabeling a paging file.

If this doesnt work, i think the C++ solution is the best.

The reason i'm keen on using C# is that it's the only language i know really
well. And, .NET CF is not a good option since i need to run a remoting server
on the frame. Planning on building a .NET CF remoting client to remote
control the frame.

But, first things first, i need to build a OS

Thanks so far. I'll keep you updated on my progress. Right now i'm having
issues with blank screen when turning on the device.. (After BIOS info, so
the screen is working)

- Jonas

Jonas,

Okey, so basicly these are my options:
a) add more memory (will 256MB of ram be enough for a WinXP + .NET image?)

Considering how RAM is cheap these days I'd go with this option if I want to stick with XPe.
I can't tell you if 256M is enough for your image since I never saw it but I'd think it is from my previous playing with "big"
images.
It will all come to the testing of the image on the final hardware.

b) use a 512MB memory card with paging file, but with reduced life span

Not good option since you may end up dealing with much of support issues after you deploy the devices.

c) get a more quiet 2.5" IDE disk

I think this is much more expensive option than a).

d) use Windows CE and .NET CF instead of Windows XPe (is this possible on a
regular laptop? booting from IDE device?)

CE is good option here, especially considering it's licence pricing
CEPC BSP is what you asked for.

However, please keep in mind that .NetCF is way too restricted vs .Net Full Frammework (in my personal opinion - .NetCF sucks).
But there will be alternatives for you like OpenNETCF (www.opennetcf.org).

e) learn some C++ and write a simple image application in native code

The best option here for any OS you choose

f) install VB6 runtime and write a VB6 application to display images?

The worse option here for any OS you choose unless you want to save some money on development hours.

g) just make the slide shows a web page and install a simple image with IE
and point it to a URL to display pictures

Depending on the "slide show" implementation this may or may not be a good option. Is it ASP based or else? HTML/DHTML? How complex
the content and the code? What is the network connection quality for your devices? Will the content be on Interanet, Extranet or
Internet? Etc.
These are only some of the questions you shuold ask yourself before going by this route.

at first glance option d, e and f are most tempting. what do you guys think?

See my comments above.
There are too many factors of your environment (budget, development time, licencing, developer availability, personal preferences,
etc.) that I do not know about but that will [should] have a big influence on your decision.

KM