> Hi, Oleg,
> 
> If you are combining your IFS and EFS images using the mkimage tool 
> (which the IDE's System Builder uses to combine images) then it is my 
> understanding that procnto should find all of the embedded files and 
> make them available in the run-time filesystem.  Other procedures for 
> mounting EFSes should only be necessary if the images aren't combined, 
> for example, if an EFS is included as a regular file in the IFS.
> 
> Do you see any warning messages in the System Builder's build console 
> when you build and combine your images?  Do you get different results if 
> you use the command-line tools, yourself, instead of System Builder?
> 
> Originally, you indicated that the image stopped working correctly when 
> its size exceeded 3MB.  If you are combining images, would you not still 
> have that problem?  It seems that the work-around would require 
> downloading and mounting the EFS separately from the boot image ...
> 
> Cheers,

Hi Cheers.


This is output. I find no warnings.





Building Image: qnxbase
C:\QNX640\host\win32\x86\usr\bin\mkifs.exe -vvv C:/Docs/workspace/.metadata/.plugins/com.qnx.tools.ide.builder.core/.
projects/new-vp9/qnxbase.mkxfs C:/Docs/workspace/new-vp9/Images/qnxbase.ifs 
  Offset   Size    Entry   Ramoff Target=Host
  400000    3f8        0      --- C:/QNX640/target/qnx6/x86/boot/sys/bios.boot
Execute: ldrel -s!* -p -l -t 0x4004f8 "C:/QNX640/target/qnx6/x86/boot/sys/startup-bios-32" "C:\DOCUME~1\05AC~1\LOCALS~1\
Temp\QE7000a50fee.tmp"
Execute: qcc -bootstrap -nostdlib -Wl,--no-keep-memory -Vgcc_ntox86 -Wl,-Ttext -Wl,0xf0016000 -o"C:\DOCUME~1\05AC~1\
LOCALS~1\Temp\QE7000a510c9.tmp" "C:/QNX640/target/qnx6/x86/boot/sys/procnto"
  4003f8    100     ----      --- Startup-header
  4004f8  137d8   404038      --- C:\DOCUME~1\05AC~1\LOCALS~1\Temp\QE7000a50fee.tmp (480015334)
  4138d8     5c     ----      --- Image-header
  413934    be8     ----      --- Image-directory
    ----    ---     ----      --- fs
  41451c    608     ----      --- proc/boot/.script=C:\DOCUME~1\05AC~1\LOCALS~1\Temp\QE7000a50fad.tmp
  414b24     18     ----      --- etc/fstab=C:\QNX640\target\qnx6\etc\fstab (191537521)
  414b3c     12     ----      --- proc/boot/unlink_list=C:\DOCUME~1\05AC~1\LOCALS~1\Temp\QE7000a50fbe.tmp (449623294)
  414b4e      7     ----      --- .diskroot=C:\QNX640\target\qnx6\etc\.diskroot (2932538503)
  415000  6b000 f0047ef0      --- proc/boot/procnto=C:\DOCUME~1\05AC~1\LOCALS~1\Temp\QE7000a510c9.tmp (2071201803)
  480000  75000    3d05a      --- proc/boot/libc.so.3=C:\QNX640\target\qnx6\x86\lib\libc.so (76736551)
    ----    ---     ----      --- proc/boot/libc.so=libc.so.3 (76736551)
  4f5000   6cae     17f0      --- proc/boot/libhiddi.so.1=C:\QNX640\target\qnx6\x86\lib\libhiddi.so (2601117683)
    ----    ---     ----      --- proc/boot/libhiddi.so=libhiddi.so.1 (2601117683)
  4fc000   b060     3120      --- proc/boot/libusbdi.so.2=C:\QNX640\target\qnx6\x86\lib\libusbdi.so (2085745603)
  507060    bcd     ----      --- etc/system/sysinit=C:/QNX640/target/qnx6/etc/system/sysinit (3480538215)
    ----    ---     ----      --- proc/boot/libusbdi.so=libusbdi.so.2 (2085745603)
  508000  104d0     3550      --- proc/boot/libcam.so.2=C:\QNX640\target\qnx6\x86\lib\libcam.so (4090673103)
    ----    ---     ----      --- proc/boot/libcam.so=libcam.so.2 (4090673103)
  519000  2462a     4d20      --- proc/boot/io-blk.so=C:\QNX640\target\qnx6\x86\lib\dll\io-blk.so (3853069029)
  53e000   d537     1550      --- proc/boot/fs-qnx4.so=C:\QNX640\target\qnx6\x86\lib\dll\fs-qnx4.so (2356113523)
  54c000   fbd4     1bf0      --- proc/boot/fs-qnx6.so=C:\QNX640\target\qnx6\x86\lib\dll\fs-qnx6.so (2560413354)
  55c000  12e1e     1e30      --- proc/boot/fs-dos.so=C:\QNX640\target\qnx6\x86\lib\dll\fs-dos.so (2706432591)
  56f000   d819     16f0      ---...

Thank you Davidl. Please tell me, whaat is NOR flash or NAND flash?????