I’m trying to figure out how much RAM and hard drive space I would need to
use the following QNX components:
QNX 4.25
TCP/IP runtime
Photon runtime
Of course, there will also be the actual application code, but I think I can
handle that…
There is a chance this will be an embedded system, so any hints on flash
disk space would be useful.
If there is a resource that I can use to figure this out myself, I would
appreciate hearing about it.
Thanks.
Previously, Kevin Miller wrote in qdn.public.qnx4:
I’m trying to figure out how much RAM and hard drive space I would need to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtime
I’m working on an embedded system that is using QNX 4.25 and
Photon runtime. The application is of moderate size, but it
uses a lot of custom .bmp files. I was able to squeeze it
all into a 20Mb Sandisk, although the customer is going for
64Mb so they can have a large log file. A pruned TCP/IP
installation should be a lot less than a Meg.
Note that I spent quite a bit of time paring down the QNX and Photon
distribution before it all fit. There’s a lot of “stuff” that you
can eliminate from most embedded systems. You want to do this anyway
for pricing so that your distributed QNX components are at a minimum.
If you are going for something more extreme, well it is possible to
used compressed objects that are expanded at run time.
Mitchell Schoenbrun --------- maschoen@pobox.com
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash, using a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.
“Mitchell Schoenbrun” <maschoen@pobox.com> wrote in message
news:Voyager.010426171224.219A@schoenbrun.com…
Previously, Kevin Miller wrote in qdn.public.qnx4:
I’m trying to figure out how much RAM and hard drive space I would need
to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtimeI’m working on an embedded system that is using QNX 4.25 and
Photon runtime. The application is of moderate size, but it
uses a lot of custom .bmp files. I was able to squeeze it
all into a 20Mb Sandisk, although the customer is going for
64Mb so they can have a large log file. A pruned TCP/IP
installation should be a lot less than a Meg.Note that I spent quite a bit of time paring down the QNX and Photon
distribution before it all fit. There’s a lot of “stuff” that you
can eliminate from most embedded systems. You want to do this anyway
for pricing so that your distributed QNX components are at a minimum.If you are going for something more extreme, well it is possible to
used compressed objects that are expanded at run time.
Mitchell Schoenbrun --------- > maschoen@pobox.com
“Kevin Miller” <kevin.miller@transcore.com> wrote in message
news:9caeqe$cla$1@inn.qnx.com…
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash, using
a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.
200mb of flash ? no, guess 24 should be enough for all times at least for
qnx distribution.
ps: hmm… it reminds me “640kb will be enough for everything !” ©
someone… 
// wbr
Kevin Miller <kevin.miller@transcore.com> wrote:
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash, using a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.
Just as an example of what you can pare down… you’ll probably only
have one graphics chip on your board – so you’ll only need one
graphics driver, not the whole suite.
You probably won’t need all the sample backdrops. You probably won’t
want all the sample applications – e.g. othello, etc.
You’ll have (at most) one disk controller – possibly none. You won’t
have a whole slew of ethernet cards, etc.
And, that’s the easy stuff to clean up.
QNX Training Services
dagibbs@qnx.com
I just setup a decent system (by decent I mean without too
may features removed) that fits in 7Meg of flash (compress
with deflate/inflator). That includes photon, and all fonts…
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:9cce6r$ben$1@nntp.qnx.com…
Kevin Miller <> kevin.miller@transcore.com> > wrote:
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash,
using a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.Just as an example of what you can pare down… you’ll probably only
have one graphics chip on your board – so you’ll only need one
graphics driver, not the whole suite.You probably won’t need all the sample backdrops. You probably won’t
want all the sample applications – e.g. othello, etc.You’ll have (at most) one disk controller – possibly none. You won’t
have a whole slew of ethernet cards, etc.And, that’s the easy stuff to clean up.
-David
QNX Training Services
dagibbs@qnx.com
I have just finished up the install disk for our product (which unlike many
embedded systems must work with a variety of modern off-the-shelf hardware).
Since it must work with a bunch of different hardware it does require a
significant set of drivers (although I did pare out the archaic ones).
Including our custom install program the whole kit fits onto 4 floppy disks,
and occupies about 12 MB of disk space(it’s compressed about 2 to 1). Now
mind you, we dont use Photon (but we do have QNX and TCP/IP). At the prior
company I worked for we did a flash based Photon product that occupied
exactly the same amount of flash space (but it only needed specific
drivers - i.e. it was a typical embedded app).
“Kevin Miller” <kevin.miller@transcore.com> wrote in message
news:9caeqe$cla$1@inn.qnx.com…
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash, using
a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.“Mitchell Schoenbrun” <> maschoen@pobox.com> > wrote in message
news:> Voyager.010426171224.219A@schoenbrun.com> …
Previously, Kevin Miller wrote in qdn.public.qnx4:I’m trying to figure out how much RAM and hard drive space I would
need
to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtimeI’m working on an embedded system that is using QNX 4.25 and
Photon runtime. The application is of moderate size, but it
uses a lot of custom .bmp files. I was able to squeeze it
all into a 20Mb Sandisk, although the customer is going for
64Mb so they can have a large log file. A pruned TCP/IP
installation should be a lot less than a Meg.Note that I spent quite a bit of time paring down the QNX and Photon
distribution before it all fit. There’s a lot of “stuff” that you
can eliminate from most embedded systems. You want to do this anyway
for pricing so that your distributed QNX components are at a minimum.If you are going for something more extreme, well it is possible to
used compressed objects that are expanded at run time.
Mitchell Schoenbrun --------- > maschoen@pobox.com
We have exactly that kind of Setup on embedded systems, we are using 8mb
DiskOnChips, and 32meg of Ram.
Kevin Miller wrote:
I’m trying to figure out how much RAM and hard drive space I would need to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtimeOf course, there will also be the actual application code, but I think I can
handle that…There is a chance this will be an embedded system, so any hints on flash
disk space would be useful.If there is a resource that I can use to figure this out myself, I would
appreciate hearing about it.Thanks.
–
Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.
Why’d you want to get rid of Othello? It’s my favorite 
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:9cce6r$ben$1@nntp.qnx.com…
Kevin Miller <> kevin.miller@transcore.com> > wrote:
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash,
using a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.Just as an example of what you can pare down… you’ll probably only
have one graphics chip on your board – so you’ll only need one
graphics driver, not the whole suite.You probably won’t need all the sample backdrops. You probably won’t
want all the sample applications – e.g. othello, etc.You’ll have (at most) one disk controller – possibly none. You won’t
have a whole slew of ethernet cards, etc.And, that’s the easy stuff to clean up.
-David
QNX Training Services
dagibbs@qnx.com
When storing the executables in compressed format, how do they end up as
task images in memory? Is there a special loader that decompresses, loads,
and starts execution?
Thanks for the help everyone!
Kevin
“Rennie Allen” <rennieallen@earthlink.net> wrote in message
news:9cigp5$akb$1@inn.qnx.com…
I have just finished up the install disk for our product (which unlike
many
embedded systems must work with a variety of modern off-the-shelf
hardware).
Since it must work with a bunch of different hardware it does require a
significant set of drivers (although I did pare out the archaic ones).
Including our custom install program the whole kit fits onto 4 floppy
disks,
and occupies about 12 MB of disk space(it’s compressed about 2 to 1). Now
mind you, we dont use Photon (but we do have QNX and TCP/IP). At the prior
company I worked for we did a flash based Photon product that occupied
exactly the same amount of flash space (but it only needed specific
drivers - i.e. it was a typical embedded app).“Kevin Miller” <> kevin.miller@transcore.com> > wrote in message
news:9caeqe$cla$> 1@inn.qnx.com> …
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash,
using
a
“standard” Photon system running on a regular PC. Sounds like the RAM is
probably about right, but I could pare the flash down by a lot.“Mitchell Schoenbrun” <> maschoen@pobox.com> > wrote in message
news:> Voyager.010426171224.219A@schoenbrun.com> …
Previously, Kevin Miller wrote in qdn.public.qnx4:I’m trying to figure out how much RAM and hard drive space I would
need
to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtimeI’m working on an embedded system that is using QNX 4.25 and
Photon runtime. The application is of moderate size, but it
uses a lot of custom .bmp files. I was able to squeeze it
all into a 20Mb Sandisk, although the customer is going for
64Mb so they can have a large log file. A pruned TCP/IP
installation should be a lot less than a Meg.Note that I spent quite a bit of time paring down the QNX and Photon
distribution before it all fit. There’s a lot of “stuff” that you
can eliminate from most embedded systems. You want to do this anyway
for pricing so that your distributed QNX components are at a minimum.If you are going for something more extreme, well it is possible to
used compressed objects that are expanded at run time.
Mitchell Schoenbrun --------- > maschoen@pobox.com
\
If get QNX4 to write you flash driver it has compression buildin.
If not there are various to do compression. The best
is program to write an io/manager that will do the
compression/decompression for you
(using the freely available z.lib library)
“Kevin Miller” <kevin.miller@transcore.com> wrote in message
news:9cms9g$njh$1@nntp.qnx.com…
When storing the executables in compressed format, how do they end up as
task images in memory? Is there a special loader that decompresses, loads,
and starts execution?Thanks for the help everyone!
Kevin
“Rennie Allen” <> rennieallen@earthlink.net> > wrote in message
news:9cigp5$akb$> 1@inn.qnx.com> …
I have just finished up the install disk for our product (which unlike
many
embedded systems must work with a variety of modern off-the-shelf
hardware).
Since it must work with a bunch of different hardware it does require a
significant set of drivers (although I did pare out the archaic ones).
Including our custom install program the whole kit fits onto 4 floppy
disks,
and occupies about 12 MB of disk space(it’s compressed about 2 to 1).
Now
mind you, we dont use Photon (but we do have QNX and TCP/IP). At the
prior
company I worked for we did a flash based Photon product that occupied
exactly the same amount of flash space (but it only needed specific
drivers - i.e. it was a typical embedded app).“Kevin Miller” <> kevin.miller@transcore.com> > wrote in message
news:9caeqe$cla$> 1@inn.qnx.com> …
Interesting. I made a quick estimate of 32mb RAM, and 200mb flash,
using
a
“standard” Photon system running on a regular PC. Sounds like the RAM
is
probably about right, but I could pare the flash down by a lot.“Mitchell Schoenbrun” <> maschoen@pobox.com> > wrote in message
news:> Voyager.010426171224.219A@schoenbrun.com> …
Previously, Kevin Miller wrote in qdn.public.qnx4:I’m trying to figure out how much RAM and hard drive space I would
need
to
use the following QNX components:QNX 4.25
TCP/IP runtime
Photon runtimeI’m working on an embedded system that is using QNX 4.25 and
Photon runtime. The application is of moderate size, but it
uses a lot of custom .bmp files. I was able to squeeze it
all into a 20Mb Sandisk, although the customer is going for
64Mb so they can have a large log file. A pruned TCP/IP
installation should be a lot less than a Meg.Note that I spent quite a bit of time paring down the QNX and Photon
distribution before it all fit. There’s a lot of “stuff” that you
can eliminate from most embedded systems. You want to do this
anyway
for pricing so that your distributed QNX components are at a
minimum.If you are going for something more extreme, well it is possible to
used compressed objects that are expanded at run time.
Mitchell Schoenbrun --------- > maschoen@pobox.com
\