More DiskOnChip Problems

QNX Newsgroups (Archives) qdn.public.qnx4
1

At the risk of repeating myself, I am re-posting this request (no flames
please). I think y’all thought I was asking the same question twice before,
where I really have (had) two separate DiskOnChip issues: Here’s the second
one:

I have successfully installed QNX 4.25D on a Versalogic VL-586-1 CPU,
EPM-SVGA-2 Video, VL-FD1-1 Floppy, VL-HD1-540 Hard drive and 8 mb DiskOnChiP
(DOC) (Basically you build a base system on the DOC using a QNX device
driver for access, then copy over the required files and utilities.)

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp & cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the install
util should be loading the license I get an error stating: “Unable to access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x” “pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

o I have confirmed the Photon install floppies by using them to install Ph
to a hard drive
o Versalogic confirmed that the DOC is an exact simulation of a hard drive
and their should be NO ifferences.

New info:
o The same problem occurs w/TCP install floppies
o Neither M-Sys nor Versalogic has been able to break ground on this problem
o I can’t get this system to ‘see’ the CD Rom drive either!!!

Any ideas?

Ray L.

2

Ray LaBrecque <ray.labrecque@gretag.imaging.com> wrote:

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp & cmp
a file 1000 times…)

Is /fd0 the floppy /dev/fd0 mentioned later or what?

o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the install
util should be loading the license I get an error stating: “Unable to access
drive: No such device or address”

This seems like the floppy drive really isn’t there. Are your
tests above really access the floppy disk?

What happend if you use the “license” utility - does it access
the floppy?


o I have confirmed the Photon install floppies by using them to install Ph
to a hard drive

On the same system with the same floppy drive?

o I can’t get this system to ‘see’ the CD Rom drive either!!!

By running Fsys.eide or what?

Regards

William Morris
wrm@innovation-tk.com

3

Hi Ray,

Your best move is really to install to a harddrive then copy the
required files over to the DOC. However lets see what your OS
image is and your sysinit file (please post). Also the output of
sin ar once the system is running.

Also, just to check, the DOC is only 8Megs? If so you won’t be able
to do a stock install directly to that, esp when you already have the
OS installed on it. How much space is left on the DOC?

Thanks

Erick.


Ray LaBrecque <ray.labrecque@gretag.imaging.com> wrote:

At the risk of repeating myself, I am re-posting this request (no flames
please). I think y’all thought I was asking the same question twice before,
where I really have (had) two separate DiskOnChip issues: Here’s the second
one:

I have successfully installed QNX 4.25D on a Versalogic VL-586-1 CPU,
EPM-SVGA-2 Video, VL-FD1-1 Floppy, VL-HD1-540 Hard drive and 8 mb DiskOnChiP
(DOC) (Basically you build a base system on the DOC using a QNX device
driver for access, then copy over the required files and utilities.)

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp & cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the install
util should be loading the license I get an error stating: “Unable to access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x” “pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

o I have confirmed the Photon install floppies by using them to install Ph
to a hard drive
o Versalogic confirmed that the DOC is an exact simulation of a hard drive
and their should be NO ifferences.

New info:
o The same problem occurs w/TCP install floppies
o Neither M-Sys nor Versalogic has been able to break ground on this problem
o I can’t get this system to ‘see’ the CD Rom drive either!!!

Any ideas?

Ray L.

4

Previously, Ray LaBrecque wrote in qdn.public.qnx4:

[…]
o Versalogic confirmed that the DOC is an exact simulation of a hard drive
and their should be NO ifferences.

FWIW, I was under the impression that flash memory devices won’t let you write to the middle of a file. Something about the way flash stores data…?

  • Pete
5

“Hardware Support Account” <hw@qnx.com> wrote in message
news:9r6j8i$1hg$2@nntp.qnx.com…

Hi Ray,

Your best move is really to install to a harddrive then copy the
required files over to the DOC. However lets see what your OS
image is and your sysinit file (please post). Also the output of
sin ar once the system is running.

OS Image (doc2000):

–
sys/boot
$ boot -v

sys/Proc32
$ Proc32 -l 1

sys/Slib16
$ Slib16

sys/Slib32
$ Slib32

/bin/Fsys
$ Fsys

/bin/Fsys.diskonchip
$ Fsys.diskonchip

/bin/mount
$ mount -p/dev/tffs0 /dev/tffs0t77 /

/bin/sinit
$ sinit TERM=qnx

sysinit.1:

–
sleep 1
echo “”
echo “sysinit.1”
echo “New Target CPU”
echo “DiskOnChip Flash File System”
echo “”

set -i
export TZ=est05edt04,M4.1.0/2,M10.5.0/2
rtc -l hw

Dev &
Dev.ansi -Q -n 9 &
reopen //0/dev/con1

Dev.ser &
Dev.par &
Dev.pty &

Serial port parameter settings

stty baud=9600 bits=8 stopb=1 par=none </dev/ser1
stty baud=9600 bits=8 stopb=1 par=none </dev/ser2

Fsys.floppy &
mount /dev/fd0 /fd0 &
Dosfsys a=/dev/fd0 &

Pipe &
emu87 &

#Net -n8 &
#Net.ether1000 -p320 -l1 &
#netmap -f

#license -R1
license -r

nameloc &

export PHWMEXIT=1

echo “”
echo “DiskOnChip: QNX Initialization Completed.”
echo “”

tinit -T /dev/con* -t /dev/con1 &

sin ar output:

–
PID USER NAME ARGUMENTS
1 System Proc32 -l 1
3 System Slib32
4 System Fsys
5 System Fsys.diskonchip
8 System Not available.
16 System Dev
19 System Dev.ansi -Q -n 9
21 System Dev.ser
22 System Dev.par
23 System Dev.pty
27 System Fsys.floppy
30 System Dosfsys a=/dev/fd0
31 System Pipe
39 System nameloc
40 System nameloc
41 System tinit -T /dev/con1 /dev/con2 /dev/con3 /dev/con4
/dev/con5 /dev/con6 /dev/con7 /dev/con8 /dev/con9 -t /dev/con1
42 root -sh
50 root sin ar


Also, just to check, the DOC is only 8Megs? If so you won’t be able
to do a stock install directly to that, esp when you already have the
OS installed on it. How much space is left on the DOC?

442 kbytes (6%)
I know a stock install will not fit, I am copying only what I need, then I
intend to pare that down to what I really need… I have no way to quantify
what I really need w/o experimentation and the few articles I have found in
the knowledge database. I wanted to do the ‘install’ of Photon, then remove
the excess. I am using a script to copy the required QNX files, and realize
that I will have to cull a lot out of there as well.

For some history: we currently have a embedded (flash) system based on a
ZiatechCPU that is obsolete. We are replacing that with a Versalogic, and I
had hoped to have the build be less convoluted than the Ziatech system (what
a mess!!!). So be my desire to ‘install’ what I could then pare it back.

I started by doing the script copy of QNX files, then a script copy of the
Photon files, and a sysinit script that started Photon manually (just like
the Ziatech system) but something was not right there (Ph wouldn’t start
correctly) and I decided to try the ‘clean’ install instead. Maybe I’ll
have to give up on this silly idea and just treat the new system like an
embedded system (VBG).

So just to fill out the histerical :wink: stuffL here are the scripts I used for
the QNX and Photon files, as well as the Photon based sysinit:

QNX Files

–
#!/bin/ksh
set -v

#ifdef __USAGE

Copy needed files to DiskOnChip for Generic QNX Installation

No application specific implementations from this script.

#%C [options]

-v verbose

To create a logfile of this script:

use: copy2doc 2>&1 | tee copy2doc.log

#endif

while getopts v opt $*
do
case $opt in
v) set -x;;
*) echo; echo
use $0
exit 1;;
esac
done

Setups Begin

--------------------------------------------------------------------

Node number where input files exist (i.e. the server)

src=//$1

Destination directory

typically: /mnt/doc

dest=$2

--------------------------------------------------------------------

Create target directories

mkdir $dest/bin
mkdir $dest/etc
mkdir $dest/etc/config
mkdir $dest/etc/config/trap
mkdir $dest/etc/config/absf
mkdir $dest/etc/licenses
mkdir $dest/etc/version
mkdir $dest/home
mkdir $dest/usr
mkdir $dest/usr/lib
mkdir $dest/usr/lib/terminfo
mkdir $dest/usr/lib/terminfo/a
mkdir $dest/usr/lib/terminfo/q
mkdir $dest/usr/lib/terminfo/t
mkdir $dest/usr/lib/terminfo/v
mkdir $dest/usr/bin

QNX Required files

cp $src/bin/Dosfsys $dest/bin
cp $src/bin/Fsys.floppy $dest/bin
cp $src/bin/Fsys.ide $dest/bin
cp $src/bin/Input $dest/bin
cp $src/bin/Mouse $dest/bin
cp $src/bin/Pipe $dest/bin
cp $src/bin/cat $dest/bin
cp $src/bin/chkfsys $dest/bin
cp $src/bin/clock $dest/bin
cp $src/bin/cp $dest/bin
cp $src/bin/date $dest/bin
cp $src/bin/df $dest/bin
cp $src/bin/du $dest/bin
cp $src/bin/echo $dest/bin
cp $src/bin/emu387 $dest/bin
cp $src/bin/emu87 $dest/bin
cp $src/bin/emu87_16 $dest/bin
cp $src/bin/emu87_32 $dest/bin
cp $src/bin/fdisk $dest/bin
cp $src/bin/find $dest/bin
cp $src/bin/grep $dest/bin
cp $src/bin/inputtrap $dest/bin
cp $src/bin/license $dest/bin
cp $src/bin/login $dest/bin
cp $src/bin/logout $dest/bin
cp $src/bin/ls $dest/bin
cp $src/bin/pax $dest/bin
cp $src/bin/mkdir $dest/bin
cp $src/bin/more $dest/bin
cp $src/bin/mount $dest/bin
cp $src/bin/mousetrap $dest/bin
cp $src/bin/mv $dest/bin
cp $src/bin/nameloc $dest/bin
cp $src/bin/net* $dest/bin
cp $src/bin/Net* $dest/bin
cp $src/bin/ps $dest/bin
cp $src/bin/pwd $dest/bin
cp $src/bin/rm $dest/bin
cp $src/bin/rmdir $dest/bin
cp $src/bin/rtc $dest/bin
cp $src/bin/sh $dest/bin
cp $src/bin/shutdown $dest/bin
cp $src/bin/sin $dest/bin
cp $src/bin/sinit $dest/bin
cp $src/bin/slay $dest/bin
cp $src/bin/sleep $dest/bin
cp $src/bin/stty $dest/bin
cp $src/bin/sync $dest/bin
cp $src/bin/tinit $dest/bin
cp $src/bin/umask $dest/bin
cp $src/bin/use $dest/bin
cp $src/bin/vedit $dest/bin

cp $src/etc/group $dest/etc
cp $src/etc/issue $dest/etc
cp $src/etc/install $dest/etc
cp $src/etc/logo.F $dest/etc
cp $src/etc/passwd $dest/etc
cp $src/etc/profile $dest/etc
cp $src/etc/shadow $dest/etc
cp $src/etc/termcap $dest/etc

cp $src/etc/config/sysinit $dest/etc/config
cp $src/etc/config/netmap $dest/etc/config

cp $src/etc/config/absf/absf.2 $dest/etc/config/absf/absf.1

Use a slightly modified sysinit file

cp /usr/local/doc/sysinit.tff $dest/etc/config/sysinit.1
cp $src/etc/config/altsysinit $dest/etc/config/altsysinit

Use the ‘new’ license method

license $src/etc/licenses $dest/etc/licenses

cp $src/.licenses $dest/
cp $src/.lastlogin $dest/

cp $src/etc/version/* $dest/etc/version

cp $src/usr/bin/crttrap $dest/usr/bin
cp $src/usr/bin/freeze $dest/usr/bin
cp $src/usr/bin/gunzip $dest/usr/bin
cp $src/usr/bin/id $dest/usr/bin
cp $src/usr/bin/kedit $dest/usr/bin

cp $src/bin/shutdown $dest/usr/bin/sd

cp $src/usr/lib/less.hlp $dest/usr/lib

cp /usr/local/doc/root.profile $dest/.profile
cp /usr/local/doc/.veditrc $dest/home/.veditrc
cp /usr/local/doc/.vedit.cfg $dest/home/.vedir.cfg

cp $src/usr/lib/terminfo/terminfo.src $dest/usr/lib/terminfo

cp $src/usr/lib/terminfo/a/ansi $dest/usr/lib/terminfo/a

cp $src/usr/lib/terminfo/q/qansi $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-g $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-m $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-t $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-w $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/q/qnx $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnx2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnx4 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxm $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxs2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt4 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxtmono $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxw $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/q/qvt101 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qvt102 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qvt108 $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/t/test $dest/usr/lib/terminfo/t

cp $src/usr/lib/terminfo/v/vi200-f $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/viewpoint $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/visual $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt100 $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt100-am $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt102 $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt102-am $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt52 $dest/usr/lib/terminfo/v

32 bit drivers…

cp $src/bin/Dev32 $dest/bin
cp $src/bin/Dev32.ansi $dest/bin
cp $src/bin/Dev32.par $dest/bin
cp $src/bin/Dev32.pty $dest/bin
cp $src/bin/Dev32.ser $dest/bin

16 bit drivers…

cp $src/bin/Dev16 $dest/bin
cp $src/bin/Dev16.ansi $dest/bin
cp $src/bin/Dev16.par $dest/bin
cp $src/bin/Dev16.pty $dest/bin
cp $src/bin/Dev16.ser $dest/bin

Remove pre-existing symbolic links

cd $dest/bin
rm -f Dev
rm -f Dev.ansi
rm -f Dev.con
rm -f Dev.ditto
rm -f Dev.par
rm -f Dev.pty
rm -f Dev.ser

(Re)Establish symbolic links

cd $dest/bin
ln -s Dev32 Dev
ln -s Dev32.ansi Dev.ansi
ln -s Dev.ansi Dev.con
ln -s Dev.ansi Dev.ditto
ln -s Dev32.par Dev.par
ln -s Dev32.pty Dev.pty
ln -s Dev32.ser Dev.ser

Photon Files

–
#!/bin/sh
set -v

Copy files required for Photon v1.13c

Mods:

18oct01 rel Genesis from Ziatech op/sys setup files

-

Setups Begin

--------------------------------------------------------------------

Node number where input files exist (i.e. the server)

srcnode=//$1

Destination directory

typically: /mnt/doc

dest=$2

Base directory from Op/Sys part number

typically: 43112012.001

pndir=$3

Where the input files for processes and application support reside

srcpath=$srcnode/englab/prod/OpSys/$pndir

--------------------------------------------------------------------

Create required directories

mkdir $dest/etc/config/trap
mkdir $dest/etc/config/absf

mkdir $dest/usr/bin

mkdir $dest/usr/photon
mkdir $dest/usr/photon/bin
mkdir $dest/usr/photon/bin/crt

mkdir $dest/usr/photon/font
mkdir $DEST/usr/photon/pallette
mkdir $dest/usr/photon/translations

Photon utils and applications

cp $srcnode/qnx4/photon/bin/Photon $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/phlib_s11 $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/Aplib_s11 $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/pwm $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/pterm $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/phfontphf $dest/usr/photon/bin

cp $srcnode/usr/bin/ph $dest/usr/bin

Elo Touch Screen calibration utility

cp $srcnode/qnx4/photon/bin/calib $dest/usr/photon/bin

Touch screen coordinate data file

#cp $srcpath/560/etc/config/absf/absf.1 $dest/etc/config/absf
cp /etc/config/absf/absf.2
$dest/etc/config/absf/absf.1

Cirrus graphics drivers

#cp $srcnode/qnx4/graphics/drivers/Pg.cirrblit $dest/usr/photon/bin
#cp $srcnode/qnx4/graphics/drivers/cirrusbios.ms $dest/usr/photon/bin/crt

Chips graphics driver and mode switcher

cp $srcnode/qnx4/graphics/drivers/Pg.chipsdc $dest/usr/photon/bin
cp $srcnode/qnx4/graphics/drivers/chipsbios.ms $dest/usr/photon/bin/crt

Font files

cp $srcnode/qnx4/photon/font/* $dest/usr/photon/font

Use a slightly modified sysinit file

cp $dest/etc/config/sysinit.1
$dest/etc/config/sysinit.1.base
cp /usr/local/doc/sysinit.tff.new $dest/etc/config/sysinit.1


sysinit.1 w/Photon

–
echo “”
echo “sysinit.1”
echo “New Target CPU-”
echo “DiskOnChip Flash File System”
echo “”

set -i
export TZ=est05edt04,M4.1.0/2,M10.5.0/2
rtc -l hw

Dev &
Dev.ansi -Q -n 9 &

reopen //0/dev/con1

Dev.ser &
Dev.par &
Dev.pty &

Serial port parameter settings

stty baud=9600 bits=8 stopb=1 par=none </dev/ser1
stty baud=9600 bits=8 stopb=1 par=none </dev/ser2

Fsys.floppy &
mount /dev/fd0 /fd0 &
Dosfsys a=/dev/fd0 &

Pipe &
emu87 &

#Net -n8 &
#Net.ether1000 -p320 -l1 &
#netmap -f

#license -R1
license -r

nameloc &

#tinit -T /dev/con* -t /dev/con1 &
tinit -T /dev/con* -c “login -p root” -t con1 con2 &

sleep 1

Photon setup…

export PHOTON_PATH=/usr/photon

export PHOTON=/dev/photon
export PHFONT=/dev/phfont

export PHSTART=1
export PHWMEXIT=1

export ABLANG=en_US
export ABLPATH=/usr/photon/translations

export PATH=$PATH:$PHOTON_PATH/bin

sleep 3

#/usr/photon/bin/Photon &
Photon &

Input kbd -R fd -d/dev/kbd msoft fd -d/dev/ser1&
Input smartset -b 9600 fd -d/dev/ser2&

/usr/photon/bin/phfontphf -E normal -M &

Settings & mode switcommands w/Versalogic EVGA card

/usr/photon/bin/Pg.chipsdc -HNqnx/crt -g800x600x16 -A0xF8000000,0x1000000 -W
B1600 -WR0 -WM0x0006,5,0,0,0x00100000
/usr/photon/bin/chipsbios.ms -i0x114 -A0xF8000000 -S0x01000000 -M0x0006,5,0,
0,0x00100000

/usr/photon/bin/pwm -SWT &

sleep 1

/usr/photon/bin/pterm


Well, is this posting long enough yet?

Thanks and keep the ideas rolling!!!

Ray L.

Thanks

Erick.


Ray LaBrecque <> ray.labrecque@gretag.imaging.com> > wrote:
At the risk of repeating myself, I am re-posting this request (no flames
please). I think y’all thought I was asking the same question twice
before,
where I really have (had) two separate DiskOnChip issues: Here’s the
second
one:

I have successfully installed QNX 4.25D on a Versalogic VL-586-1 CPU,
EPM-SVGA-2 Video, VL-FD1-1 Floppy, VL-HD1-540 Hard drive and 8 mb
DiskOnChiP
(DOC) (Basically you build a base system on the DOC using a QNX device
driver for access, then copy over the required files and utilities.)

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp &
cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the
install
util should be loading the license I get an error stating: “Unable to
access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x”
“pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

o I have confirmed the Photon install floppies by using them to install
Ph
to a hard drive
o Versalogic confirmed that the DOC is an exact simulation of a hard
drive
and their should be NO ifferences.

New info:
o The same problem occurs w/TCP install floppies
o Neither M-Sys nor Versalogic has been able to break ground on this
problem
o I can’t get this system to ‘see’ the CD Rom drive either!!!

Any ideas?

Ray L.

6

“Operating System Tech Support” <os@qnx.com> wrote in message
news:9r6i72$15j$1@nntp.qnx.com…

“Ray LaBrecque” <> ray.labrecque@gretag.imaging.com> > wrote in message
news:9r524m$1h3$> 1@inn.qnx.com> …

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp &
cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the
install
util should be loading the license I get an error stating: “Unable to
access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x”
“pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

What is the prefix of the DOC (ie how does it appear in the /dev
directory).

/tffs0 or /tffs0t77
I’m not sure which is the prefix you are after…

-Adam

7

“William Morris” <wrm@innovation-tk.com> wrote in message
news:9r6i7d$11d$1@inn.qnx.com…

Ray LaBrecque <> ray.labrecque@gretag.imaging.com> > wrote:
o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp &
cmp
a file 1000 times…)

Is /fd0 the floppy /dev/fd0 mentioned later or what?

One and the same, just depends on the point of reference.

o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the
install
util should be loading the license I get an error stating: “Unable to
access
drive: No such device or address”

This seems like the floppy drive really isn’t there. Are your
tests above really access the floppy disk?

Yes.
cp test.txt /fd0
cmp test.txt /fd0/test.txt
And after the 1000 interations, test.txt is on the floppy


What happend if you use the “license” utility - does it access
the floppy?

It seems to.
i.e. no errors reported and it asks for the next lixense volume just like
normal…

o I have confirmed the Photon install floppies by using them to install
Ph
to a hard drive

On the same system with the same floppy drive?

Yes

o I can’t get this system to ‘see’ the CD Rom drive either!!!

By running Fsys.eide or what?

Using the QNX distribution/install/upgrade CD and associated boot floppy,
the auto detect sequence fines everything BUT the CD.

Regards

William Morris
wrm@innovation-tk.com

8

“Pete DiMarco” <peted@ifspurity.NOSPAM.com> wrote in message
news:Voyager.011024105447.182A@node1…

Previously, Ray LaBrecque wrote in qdn.public.qnx4:
[…]
o Versalogic confirmed that the DOC is an exact simulation of a hard
drive
and their should be NO ifferences.

FWIW, I was under the impression that flash memory devices won’t let
you write to the middle of a file. Something about the way flash stores

data…?

But, this isn’t flash: it’s a DiskOnChip from M-Sys. I presume it si
nonvolatile ram or something similiar…

  • Pete
9

Previously, Ray LaBrecque wrote in qdn.public.qnx4:

“Pete DiMarco” <> peted@ifspurity.NOSPAM.com> > wrote in message
news:Voyager.011024105447.182A@node1…
Previously, Ray LaBrecque wrote in qdn.public.qnx4:
[…]
o Versalogic confirmed that the DOC is an exact simulation of a hard
drive
and their should be NO ifferences.

FWIW, I was under the impression that flash memory devices won’t let
you write to the middle of a file. Something about the way flash stores
data…?

But, this isn’t flash: it’s a DiskOnChip from M-Sys. I presume it si
nonvolatile ram or something similiar…

Nope, it is flash. It contains BIOS extensions that implement a flash
filesystem (which M-Systems calls TrueFFS). The firmware hides the
details of the flash implementation (block writes, wear leveling,
bad block management, block reclamation, etc).

We are using 8MB DOC’s with QNX4 and Photon on an instrument without
much trouble.

10

“Ray LaBrecque” <ray.labrecque@gretag.imaging.com> wrote in message
news:9r524m$1h3$1@inn.qnx.com…

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp &
cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the
install
util should be loading the license I get an error stating: “Unable to
access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x” “pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

What is the prefix of the DOC (ie how does it appear in the /dev directory).

-Adam

11

“Ken Schumm” <kwschumm@IH8SPAMqsolv.com> wrote in message
news:Voyager.011024120741.16124A@dilbert…

Previously, Ray LaBrecque wrote in qdn.public.qnx4:

“Pete DiMarco” <> peted@ifspurity.NOSPAM.com> > wrote in message
news:Voyager.011024105447.182A@node1…
Previously, Ray LaBrecque wrote in qdn.public.qnx4:
[…]
o Versalogic confirmed that the DOC is an exact simulation of a hard
drive
and their should be NO ifferences.

FWIW, I was under the impression that flash memory devices won’t
let
you write to the middle of a file. Something about the way flash stores
data…?

It’s complicated but can be done. QNX flash file system doesn’t allow this,
last time I check. But DOC have their own firmware/driver and they
support this feature.

But, this isn’t flash: it’s a DiskOnChip from M-Sys. I presume it si
nonvolatile ram or something similiar…


Nope, it is flash. It contains BIOS extensions that implement a flash
filesystem (which M-Systems calls TrueFFS). The firmware hides the
details of the flash implementation (block writes, wear leveling,
bad block management, block reclamation, etc).

It’s doesn’t have anything to do with BIOS extensions (QNX4 doesn’t
use BIOS). It’s handle by firmware inside the DOC.

We are using 8MB DOC’s with QNX4 and Photon on an instrument without
much trouble.

12

Mario Charest <mcharest@clipzinformatic.com> wrote:

It’s doesn’t have anything to do with BIOS extensions (QNX4 doesn’t
use BIOS). It’s handle by firmware inside the DOC.

(Off topic) is it always true that QNX doesn’t use the BIOS?
I had inferred from the thread on Fdisk and disk size that the QNX
filesystems get disk geometry information from the BIOS.

Not much use here I know…
Regards

William Morris
wrm@innovation-tk.com

13

“William Morris” <wrm@innovation-tk.com> wrote in message
news:9r93he$ke3$1@inn.qnx.com…

Mario Charest <> mcharest@clipzinformatic.com> > wrote:
It’s doesn’t have anything to do with BIOS extensions (QNX4 doesn’t
use BIOS). It’s handle by firmware inside the DOC.

(Off topic) is it always true that QNX doesn’t use the BIOS?
I had inferred from the thread on Fdisk and disk size that the QNX
filesystems get disk geometry information from the BIOS.

I beleive this information is stored in some memory space setup by the
BIOS, hence in this perticular case QNX doesn’t call BIOS
function,but rather peeks at some memory location. This is an
educated assumption from my part :wink:

Not much use here I know…
Regards

William Morris
wrm@innovation-tk.com

14

Ray LaBrecque <ray.labrecque@gretag.imaging.com> wrote:

“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r6j8i$1hg$> 2@nntp.qnx.com> …
Hi Ray,

Your best move is really to install to a harddrive then copy the
required files over to the DOC. However lets see what your OS
image is and your sysinit file (please post). Also the output of
sin ar once the system is running.

OS installed on it. How much space is left on the DOC?

442 kbytes (6%)
I know a stock install will not fit, I am copying only what I need, then I
intend to pare that down to what I really need… I have no way to quantify
what I really need w/o experimentation and the few articles I have found in
the knowledge database. I wanted to do the ‘install’ of Photon, then remove
the excess. I am using a script to copy the required QNX files, and realize
that I will have to cull a lot out of there as well.

For some history: we currently have a embedded (flash) system based on a
ZiatechCPU that is obsolete. We are replacing that with a Versalogic, and I
had hoped to have the build be less convoluted than the Ziatech system (what
a mess!!!). So be my desire to ‘install’ what I could then pare it back.

I started by doing the script copy of QNX files, then a script copy of the
Photon files, and a sysinit script that started Photon manually (just like
the Ziatech system) but something was not right there (Ph wouldn’t start
correctly) and I decided to try the ‘clean’ install instead. Maybe I’ll
have to give up on this silly idea and just treat the new system like an
embedded system (VBG).

I don’t see another way, as with only 442K of space left you don’t even have
enough room for phlib_s11. Not to mention your graphics driver which is about
~120K in size.

Here is what I would do (you don’t have to do this, this is just my suggestion) :slight_smile:

  • You should already have a fully running system with QNX and Photon on your
    HOST system before you start. This should include all the products you will
    want on your TARGET system.

Step 1: Install the OS

  • On your HOST system, make a new 8MB partition on your harddrive, or to the size
    of the space that is available on your TARGET system.
  • Initalize the partition and start to copy over manually the minimum files that
    you will need (e.g. tools, config files, binarys…).
  • At this point you should be able to boot from your 8MB partition on your HOST
    system. To boot from your 8MB partition, use the fdisk utility and set the boot
    flag to the 8MB partition.

Step 2: Install TCP/IP

  • Still on your HOST system, you will start to copy over the minmum files that you
    will need. Just enough to get TCP/IP going. It will be a bit of experimentation,
    but it shouldn’t be too bad. Just make sure that you look at the docs and see what
    config files are needed for the components you want to install.

  • An easy way to find out which binarys you will need, is to type ‘sin’ on your HOST
    system and see what is running. Somethings will be different (e.g. gfx driver and
    network driver).

Step 3: Install Photon

  • Using the same method used above, install the bits and pieces that you will need.
    Good things to look at will be the Docs. They will explain what config files you
    will need as well. Remember your drivers are stored in /qnx4/graphics directory.

  • Good knowledge base entries like this:

http://qdn.qnx.com/support/bok/solution.qnx?6453

Will also help alot.

  • Try booting from your 8MB partition and see how things run.


    Step 4: Copy it to your TARGET system.

  • Use a DOC reader in your HOST system and mount the DOC. Then copy all the files
    from your 8MB partition on your HOST system to the DOC. Move the DOC to your target
    system. If everything went smoothly then you should have your target system setup
    and running!


    Take care.

Erick.

So just to fill out the histerical > :wink: > stuffL here are the scripts I used for
the QNX and Photon files, as well as the Photon based sysinit:

QNX Files

–
#!/bin/ksh
set -v

#ifdef __USAGE

Copy needed files to DiskOnChip for Generic QNX Installation

No application specific implementations from this script.

#%C [options]

-v verbose

To create a logfile of this script:

use: copy2doc 2>&1 | tee copy2doc.log

#endif

while getopts v opt $*
do
case $opt in
v) set -x;;
*) echo; echo
use $0
exit 1;;
esac
done

Setups Begin

--------------------------------------------------------------------

Node number where input files exist (i.e. the server)

src=//$1

Destination directory

typically: /mnt/doc

dest=$2

--------------------------------------------------------------------

Create target directories

mkdir $dest/bin
mkdir $dest/etc
mkdir $dest/etc/config
mkdir $dest/etc/config/trap
mkdir $dest/etc/config/absf
mkdir $dest/etc/licenses
mkdir $dest/etc/version
mkdir $dest/home
mkdir $dest/usr
mkdir $dest/usr/lib
mkdir $dest/usr/lib/terminfo
mkdir $dest/usr/lib/terminfo/a
mkdir $dest/usr/lib/terminfo/q
mkdir $dest/usr/lib/terminfo/t
mkdir $dest/usr/lib/terminfo/v
mkdir $dest/usr/bin

QNX Required files

cp $src/bin/Dosfsys $dest/bin
cp $src/bin/Fsys.floppy $dest/bin
cp $src/bin/Fsys.ide $dest/bin
cp $src/bin/Input $dest/bin
cp $src/bin/Mouse $dest/bin
cp $src/bin/Pipe $dest/bin
cp $src/bin/cat $dest/bin
cp $src/bin/chkfsys $dest/bin
cp $src/bin/clock $dest/bin
cp $src/bin/cp $dest/bin
cp $src/bin/date $dest/bin
cp $src/bin/df $dest/bin
cp $src/bin/du $dest/bin
cp $src/bin/echo $dest/bin
cp $src/bin/emu387 $dest/bin
cp $src/bin/emu87 $dest/bin
cp $src/bin/emu87_16 $dest/bin
cp $src/bin/emu87_32 $dest/bin
cp $src/bin/fdisk $dest/bin
cp $src/bin/find $dest/bin
cp $src/bin/grep $dest/bin
cp $src/bin/inputtrap $dest/bin
cp $src/bin/license $dest/bin
cp $src/bin/login $dest/bin
cp $src/bin/logout $dest/bin
cp $src/bin/ls $dest/bin
cp $src/bin/pax $dest/bin
cp $src/bin/mkdir $dest/bin
cp $src/bin/more $dest/bin
cp $src/bin/mount $dest/bin
cp $src/bin/mousetrap $dest/bin
cp $src/bin/mv $dest/bin
cp $src/bin/nameloc $dest/bin
cp $src/bin/net* $dest/bin
cp $src/bin/Net* $dest/bin
cp $src/bin/ps $dest/bin
cp $src/bin/pwd $dest/bin
cp $src/bin/rm $dest/bin
cp $src/bin/rmdir $dest/bin
cp $src/bin/rtc $dest/bin
cp $src/bin/sh $dest/bin
cp $src/bin/shutdown $dest/bin
cp $src/bin/sin $dest/bin
cp $src/bin/sinit $dest/bin
cp $src/bin/slay $dest/bin
cp $src/bin/sleep $dest/bin
cp $src/bin/stty $dest/bin
cp $src/bin/sync $dest/bin
cp $src/bin/tinit $dest/bin
cp $src/bin/umask $dest/bin
cp $src/bin/use $dest/bin
cp $src/bin/vedit $dest/bin

cp $src/etc/group $dest/etc
cp $src/etc/issue $dest/etc
cp $src/etc/install $dest/etc
cp $src/etc/logo.F $dest/etc
cp $src/etc/passwd $dest/etc
cp $src/etc/profile $dest/etc
cp $src/etc/shadow $dest/etc
cp $src/etc/termcap $dest/etc

cp $src/etc/config/sysinit $dest/etc/config
cp $src/etc/config/netmap $dest/etc/config

cp $src/etc/config/absf/absf.2 $dest/etc/config/absf/absf.1

Use a slightly modified sysinit file

cp /usr/local/doc/sysinit.tff $dest/etc/config/sysinit.1
cp $src/etc/config/altsysinit $dest/etc/config/altsysinit

Use the ‘new’ license method

license $src/etc/licenses $dest/etc/licenses

cp $src/.licenses $dest/
cp $src/.lastlogin $dest/

cp $src/etc/version/* $dest/etc/version

cp $src/usr/bin/crttrap $dest/usr/bin
cp $src/usr/bin/freeze $dest/usr/bin
cp $src/usr/bin/gunzip $dest/usr/bin
cp $src/usr/bin/id $dest/usr/bin
cp $src/usr/bin/kedit $dest/usr/bin

cp $src/bin/shutdown $dest/usr/bin/sd

cp $src/usr/lib/less.hlp $dest/usr/lib

cp /usr/local/doc/root.profile $dest/.profile
cp /usr/local/doc/.veditrc $dest/home/.veditrc
cp /usr/local/doc/.vedit.cfg $dest/home/.vedir.cfg

cp $src/usr/lib/terminfo/terminfo.src $dest/usr/lib/terminfo

cp $src/usr/lib/terminfo/a/ansi $dest/usr/lib/terminfo/a

cp $src/usr/lib/terminfo/q/qansi $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-g $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-m $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-t $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qansi-w $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/q/qnx $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnx2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnx4 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxm $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxs2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt2 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxt4 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxtmono $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qnxw $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/q/qvt101 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qvt102 $dest/usr/lib/terminfo/q
cp $src/usr/lib/terminfo/q/qvt108 $dest/usr/lib/terminfo/q

cp $src/usr/lib/terminfo/t/test $dest/usr/lib/terminfo/t

cp $src/usr/lib/terminfo/v/vi200-f $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/viewpoint $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/visual $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt100 $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt100-am $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt102 $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt102-am $dest/usr/lib/terminfo/v
cp $src/usr/lib/terminfo/v/vt52 $dest/usr/lib/terminfo/v

32 bit drivers…

cp $src/bin/Dev32 $dest/bin
cp $src/bin/Dev32.ansi $dest/bin
cp $src/bin/Dev32.par $dest/bin
cp $src/bin/Dev32.pty $dest/bin
cp $src/bin/Dev32.ser $dest/bin

16 bit drivers…

cp $src/bin/Dev16 $dest/bin
cp $src/bin/Dev16.ansi $dest/bin
cp $src/bin/Dev16.par $dest/bin
cp $src/bin/Dev16.pty $dest/bin
cp $src/bin/Dev16.ser $dest/bin

Remove pre-existing symbolic links

cd $dest/bin
rm -f Dev
rm -f Dev.ansi
rm -f Dev.con
rm -f Dev.ditto
rm -f Dev.par
rm -f Dev.pty
rm -f Dev.ser

(Re)Establish symbolic links

cd $dest/bin
ln -s Dev32 Dev
ln -s Dev32.ansi Dev.ansi
ln -s Dev.ansi Dev.con
ln -s Dev.ansi Dev.ditto
ln -s Dev32.par Dev.par
ln -s Dev32.pty Dev.pty
ln -s Dev32.ser Dev.ser

Photon Files

–
#!/bin/sh
set -v

Copy files required for Photon v1.13c

Mods:

18oct01 rel Genesis from Ziatech op/sys setup files

-

Setups Begin

--------------------------------------------------------------------

Node number where input files exist (i.e. the server)

srcnode=//$1

Destination directory

typically: /mnt/doc

dest=$2

Base directory from Op/Sys part number

typically: 43112012.001

pndir=$3

Where the input files for processes and application support reside

srcpath=$srcnode/englab/prod/OpSys/$pndir

--------------------------------------------------------------------

Create required directories

mkdir $dest/etc/config/trap
mkdir $dest/etc/config/absf

mkdir $dest/usr/bin

mkdir $dest/usr/photon
mkdir $dest/usr/photon/bin
mkdir $dest/usr/photon/bin/crt

mkdir $dest/usr/photon/font
mkdir $DEST/usr/photon/pallette
mkdir $dest/usr/photon/translations

Photon utils and applications

cp $srcnode/qnx4/photon/bin/Photon $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/phlib_s11 $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/Aplib_s11 $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/pwm $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/pterm $dest/usr/photon/bin
cp $srcnode/qnx4/photon/bin/phfontphf $dest/usr/photon/bin

cp $srcnode/usr/bin/ph $dest/usr/bin

Elo Touch Screen calibration utility

cp $srcnode/qnx4/photon/bin/calib $dest/usr/photon/bin

Touch screen coordinate data file

#cp $srcpath/560/etc/config/absf/absf.1 $dest/etc/config/absf
cp /etc/config/absf/absf.2
$dest/etc/config/absf/absf.1

Cirrus graphics drivers

#cp $srcnode/qnx4/graphics/drivers/Pg.cirrblit $dest/usr/photon/bin
#cp $srcnode/qnx4/graphics/drivers/cirrusbios.ms $dest/usr/photon/bin/crt

Chips graphics driver and mode switcher

cp $srcnode/qnx4/graphics/drivers/Pg.chipsdc $dest/usr/photon/bin
cp $srcnode/qnx4/graphics/drivers/chipsbios.ms $dest/usr/photon/bin/crt

Font files

cp $srcnode/qnx4/photon/font/* $dest/usr/photon/font

Use a slightly modified sysinit file

cp $dest/etc/config/sysinit.1
$dest/etc/config/sysinit.1.base
cp /usr/local/doc/sysinit.tff.new $dest/etc/config/sysinit.1



sysinit.1 w/Photon

–
echo “”
echo “sysinit.1”
echo “New Target CPU-”
echo “DiskOnChip Flash File System”
echo “”

set -i
export TZ=est05edt04,M4.1.0/2,M10.5.0/2
rtc -l hw

Dev &
Dev.ansi -Q -n 9 &

reopen //0/dev/con1

Dev.ser &
Dev.par &
Dev.pty &

Serial port parameter settings

stty baud=9600 bits=8 stopb=1 par=none </dev/ser1
stty baud=9600 bits=8 stopb=1 par=none </dev/ser2

Fsys.floppy &
mount /dev/fd0 /fd0 &
Dosfsys a=/dev/fd0 &

Pipe &
emu87 &

#Net -n8 &
#Net.ether1000 -p320 -l1 &
#netmap -f

#license -R1
license -r

nameloc &

#tinit -T /dev/con* -t /dev/con1 &
tinit -T /dev/con* -c “login -p root” -t con1 con2 &

sleep 1

Photon setup…

export PHOTON_PATH=/usr/photon

export PHOTON=/dev/photon
export PHFONT=/dev/phfont

export PHSTART=1
export PHWMEXIT=1

export ABLANG=en_US
export ABLPATH=/usr/photon/translations

export PATH=$PATH:$PHOTON_PATH/bin

sleep 3

#/usr/photon/bin/Photon &
Photon &

Input kbd -R fd -d/dev/kbd msoft fd -d/dev/ser1&
Input smartset -b 9600 fd -d/dev/ser2&

/usr/photon/bin/phfontphf -E normal -M &

Settings & mode switcommands w/Versalogic EVGA card

/usr/photon/bin/Pg.chipsdc -HNqnx/crt -g800x600x16 -A0xF8000000,0x1000000 -W
B1600 -WR0 -WM0x0006,5,0,0,0x00100000
/usr/photon/bin/chipsbios.ms -i0x114 -A0xF8000000 -S0x01000000 -M0x0006,5,0,
0,0x00100000

/usr/photon/bin/pwm -SWT &

sleep 1

/usr/photon/bin/pterm



Well, is this posting long enough yet?

Thanks and keep the ideas rolling!!!

Ray L.


Thanks

Erick.


Ray LaBrecque <> ray.labrecque@gretag.imaging.com> > wrote:
At the risk of repeating myself, I am re-posting this request (no flames
please). I think y’all thought I was asking the same question twice
before,
where I really have (had) two separate DiskOnChip issues: Here’s the
second
one:

I have successfully installed QNX 4.25D on a Versalogic VL-586-1 CPU,
EPM-SVGA-2 Video, VL-FD1-1 Floppy, VL-HD1-540 Hard drive and 8 mb
DiskOnChiP
(DOC) (Basically you build a base system on the DOC using a QNX device
driver for access, then copy over the required files and utilities.)

o The DOC boots to QNX cleanly
o Can access /fd0 from DOC w/o ANY errors (set up a script loop to cp &
cmp
a file 1000 times…)
o The hard drive is NOT configured in when I boot to DOC
o I have Photon MicroGui install floppies, NOT a CD
o When I try to install Photon from floppy I get total failure:

I insert Floppy #1 and type: install /dev/fd0 but, when the
install
util should be loading the license I get an error stating: “Unable to
access
drive: No such device or address” then the “Restoring the archive…”
message is displayed followed by continual “pax: Ready for volume x”
“pax:
Type “go” when ready to proceed (or “quit” to abort):” prompts.

o I have confirmed the Photon install floppies by using them to install
Ph
to a hard drive
o Versalogic confirmed that the DOC is an exact simulation of a hard
drive
and their should be NO ifferences.

New info:
o The same problem occurs w/TCP install floppies
o Neither M-Sys nor Versalogic has been able to break ground on this
problem
o I can’t get this system to ‘see’ the CD Rom drive either!!!

Any ideas?

Ray L.

15

Previously, Mario Charest wrote in qdn.public.qnx4:

[…]



Nope, it is flash. It contains BIOS extensions that implement a flash
filesystem (which M-Systems calls TrueFFS). The firmware hides the
details of the flash implementation (block writes, wear leveling,
bad block management, block reclamation, etc).

It’s doesn’t have anything to do with BIOS extensions (QNX4 doesn’t
use BIOS). It’s handle by firmware inside the DOC.

Sure it does. The DOC is detected via the BIOS scan, and code on the
DOC runs at that time to install BIOS extensions. If it’s not detected
during the BIOS scan, or there’s an address conflict in the BIOS area,
it could cause problems.

I never said that QNX used the BIOS extensions. I said that the firmware
on the DOC hides the details of the flash implementation.

16

“Ken Schumm” <kwschumm@IH8SPAMqsolv.com> wrote in message
news:Voyager.011025090625.238B@dilbert…

Previously, Mario Charest wrote in qdn.public.qnx4:

[…]



Nope, it is flash. It contains BIOS extensions that implement a flash
filesystem (which M-Systems calls TrueFFS). The firmware hides the
details of the flash implementation (block writes, wear leveling,
bad block management, block reclamation, etc).

It’s doesn’t have anything to do with BIOS extensions (QNX4 doesn’t
use BIOS). It’s handle by firmware inside the DOC.

Sure it does. The DOC is detected via the BIOS scan, and code on the
DOC runs at that time to install BIOS extensions. If it’s not detected
during the BIOS scan, or there’s an address conflict in the BIOS area,
it could cause problems.

That’s not what I’m was trying to say. What I meant is that the BIOS
is not use by QNX4 for read write access. What you are talking about
is the boot process before QNX even starts.


I never said that QNX used the BIOS extensions. I said that the firmware
on the DOC hides the details of the flash implementation.

Look like we are saying the same thing. But your english sounds better then
mine :wink:

17

Previously, Mario Charest wrote in qdn.public.qnx4:

“Ken Schumm” <> kwschumm@IH8SPAMqsolv.com> > wrote in message
news:Voyager.011025090625.238B@dilbert…
Previously, Mario Charest wrote in qdn.public.qnx4:

[…]

That’s not what I’m was trying to say. What I meant is that the BIOS
is not use by QNX4 for read write access. What you are talking about
is the boot process before QNX even starts.

Right you are.

Look like we are saying the same thing. But your english sounds better then
mine > :wink:

At least you can speak several languages. I’ve forgotten most of
my high school german :frowning: I’ll have to take a trip to Europe to
brush up one of these days.

18

“Ray LaBrecque” <ray.labrecque@gretag.imaging.com> wrote in message
news:9r713p$9r3$1@inn.qnx.com…

“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9r6j8i$1hg$> 2@nntp.qnx.com> …
Also, just to check, the DOC is only 8Megs? If so you won’t be able
to do a stock install directly to that, esp when you already have the
OS installed on it. How much space is left on the DOC?

442 kbytes (6%)

I’m not sure if you could even start to fit photon with 442 Kb left on you
DOC. Perhaps that’s is a problem.

-Adam