Installation QNX 6.5.0

Hi, my name is John, and on the past days I installed QNX 6.5.0, i try to create an image in a usb device, when I boot, the boot init good, but if i try to save a file, i can’t, apear the message:

Can’t open destination file ():No such file or directory

or if i try to create a dir show this:

mkdir : /tmp: Function not implemented

How can I do to storage files?
This is my build file

The build file for QNX Neutrino booting on a PC

[virtual=x86,bios +compress] boot = {
# Reserve 64k of video memory to handle multiple video cards
startup-bios -s64k

# PATH is the *safe* path for executables (confstr(_CS_PATH...))
# LD_LIBRARY_PATH is the *safe* path for libraries (confstr(_CS_LIBPATH))
#    i.e. This is the path searched for libs in setuid/setgid executables.
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin 
LD_LIBRARY_PATH=/proc/boot:/lib:/lib/dll procnto

}

[+script] startup-script = {
# To save memory make everyone use the libc in the boot image!
# For speed (less symbolic lookups) we point to libc.so.3 instead of libc.so

procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2

display_msg " "
# Display message to indicate which kernel I am running
display_msg Welcome to QNX!!

pci-bios
slogger -s32

# Start USB
io-usb -duhci -dohci -dehci
waitfor /dev/io-usb

hostname -s QNX_Colibri

# devc-ser8250 -u1 3f8,4 -u2 2f8,3
devc-pty -n 32
pipe
mqueue
random -t
dumper -d /var/dumps

# HID
io-hid -d ps2ser kbd:kbddev:ps2mouse:mousedev -d usb /dev/io-usb/io-usb

# USB media
#sleep 5
#devb-umass disk name=umass
#waitfor /dev/umass0t79
#mount -t qnx4 /dev/umass0t79 /
#waitfor /sbin

#puerto serial
devc-ser8250 -e -b9600 0x1d0003f8,0x23 &
reopen

#start Networking
io-pkt-v4 -de1000 name=en &
if_up -p en0
ifconfig en0 10.0.0.3 netmask 255.255.255.0 
route add default 10.0.0.1

waitfor /dev/socket 5
netmanager &
inetd &
#dhcp.client en0

# mount the software patch media (FAT16)
# waitfor /dev/umass0t7
# mount -t dos /dev/umass0t7 /fs/patches
# waitfor /fs/patches

# mount the software patch media (FAT32)
#waitfor /dev/umass0t12
#mount -t dos /dev/umass0t12 /fs/patches
#waitfor /fs/patches

# Mount HDD
#devb-eide blk auto=partition dos exe=all cam quite
#waitfor /dev/hd0
#mount -t qnx4 /dev/hd0t79 /fs/hdd
# mount -t qnx6 /dev/hd0t179 /fs/hdd
#waitfor /fs/hdd

display_msg Starting Shell ... 
# devc-con -n4
devc-con-hid -n4
waitfor /dev/con1
reopen /dev/con1
[+session] sh

}

Include the current “libc.so”. It will be created as a real file using

its internal “SONAME”, with “libc.so” being a symlink to it. The symlink

will point to the last “libc.so.*” so if an earlier libc is needed

(e.g. libc.so.1) add it before the this line.

libc.so
libm.so
libz.so
libhiddi.so
libusbdi.so

Include all the files for the default filesystems

libcam.so
io-blk.so
cam-disk.so
#fs-qnx4.so
#fs-qnx6.so
#fs-dos.so
#fs-ext2.so
#cam-cdrom.so
#fs-cd.so

USB for console driver

devu-ehci.so
devu-ohci.so
devu-uhci.so
devh-usb.so
devh-ps2ser.so

#Network drivers
devnp-e1000.so
libsocket.so.3
libc.so.3
libexpat.so.2
libwlconfig.so.1

These programs only need to be run once from the boot image.

“data=uip” will waste less memory as the ram from the boot

image will be used directly without making a copy of the data

(i.e. as the default “data=cpy” does). When they have been

run once, they will be unlinked from /proc/boot.

[data=copy]
seedres
pci-bios
devb-eide
#devb-umass
devb-ahci
#devb-mvSata
devb-adpu320
devb-aha8
umass-enum
[search=${MKIFS_PATH}:${QNX_TARGET}/etc] umass-enum.cfg
io-usb
io-hid
#diskboot
slogger
fesh
devc-con
devc-con-hid
devc-pty
waitfor
mount
hostname
pipe
mqueue
random
dumper
sh
sleep
ifconfig
io-pkt-v4
netmanager
inetd
route
if_up
devc-ser8250

binaries needed for debugging

ls

less

pidin

shutdown

slay

vi

usb

cp

These files will be unlinked after the system has started

to release the memory back to the system. They are only

needed during boot. If needed later on, they will be loaded

from the boot device.

unlink_list={
/proc/boot/devb-*
}

Idon’t know what else to do.

Thanks.

:unamused:

It appears you’ve commented out the devb-umass driver in your boot image. This is the usb driver for reading/writing. You also are no longer attempting to start the USB media which is another reason you can’t read/write files.

So assuming you are trying to read/write to your USB boot flash drive (and not a hard disk) you aren’t going to have a lot of luck.

Tim

Hi Tim, thanks.

I uncomment the devb-umass line

USB media

#sleep 5
devb-umass disk name=umass
waitfor /dev/umass0t79

cam-disk.so
fs-qnx4.so
fs-qnx6.so
fs-dos.so
fs-ext2.so
cam-cdrom.so
fs-cd.so

devb-umass

and apear when boot
xpt_configure: No umass interface found

so, how I can start the usb media.

thanks

devb-umass cam pnp ?

And don’t forget to uncomment the lines that do the partition mounting so you get the QNX or Dos file system.

Tim

Tim, thanks, it works ok, no, the file system is qnx, and I can write on it.

Tim, where I can find information about, how install gcc with libraries, as and ld on target(USB), after the installation of qnx.