Installation without a CD drive???

I have some industrial PCs equipped only with Floppy, ZIP & Hard disk
drives. It is not possible to temporarily connect a CD drive to the IDE bus.
I would like to install a full, exclusive QNX6 system onto them for the
purposes of developing an application. The machines have access to a
network, so, if I could get a basic system installed e.g. the equivalent of
installing from qnxrtp_rel_small.iso, the additional ‘bells and whistles’
can be added from a remote repository.

The simplest solution would be to copy the contents of qnxrtp_rel_small.iso
onto a ZIP drive and to modify the boot image used on the CD to mount a ZIP
drive instead of a CD drive. The source code for this boot image does not
appear to be in the public domain(?)

Has anyone any comments on the above or any alternative suggestions?

Jim Douglas

“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:9os4kg$3bi$1@inn.qnx.com

I have some industrial PCs equipped only with Floppy, ZIP & Hard disk
drives. It is not possible to temporarily connect a CD drive to the IDE
bus.
I would like to install a full, exclusive QNX6 system onto them for the
purposes of developing an application. The machines have access to a
network, so, if I could get a basic system installed e.g. the equivalent
of
installing from qnxrtp_rel_small.iso, the additional ‘bells and whistles’
can be added from a remote repository.

The simplest solution would be to copy the contents of
qnxrtp_rel_small.iso
onto a ZIP drive and to modify the boot image used on the CD to mount a
ZIP
drive instead of a CD drive. The source code for this boot image does not
appear to be in the public domain(?)

Has anyone any comments on the above or any alternative suggestions?

Move the IDE harddisk onto standard PC and run the installation from there.

Jim Douglas

“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9oshdn$cgp$1@inn.qnx.com

“Jim Douglas” <> jim@dramatec.co.uk> > wrote in message
news:9os4kg$3bi$> 1@inn.qnx.com> …
I have some industrial PCs equipped only with Floppy, ZIP & Hard disk
drives. It is not possible to temporarily connect a CD drive to the IDE
bus.
I would like to install a full, exclusive QNX6 system onto them for the
purposes of developing an application. The machines have access to a
network, so, if I could get a basic system installed e.g. the equivalent
of
installing from qnxrtp_rel_small.iso, the additional ‘bells and
whistles’
can be added from a remote repository.

The simplest solution would be to copy the contents of
qnxrtp_rel_small.iso
onto a ZIP drive and to modify the boot image used on the CD to mount a
ZIP
drive instead of a CD drive. The source code for this boot image does
not
appear to be in the public domain(?)

Has anyone any comments on the above or any alternative suggestions?


Move the IDE harddisk onto standard PC and run the installation from
there.

I already did that. It’s a real pain. These panel PCs are not designed to be
taken apart.

Jim Douglas

Jim Douglas <jim@dramatec.co.uk> wrote:


I already did that. It’s a real pain. These panel PCs are not designed to be
taken apart.

You could install it on a hardrive on an outside PC, and use Ghost (or some
other tool) to do a Ghost image across the network on the target PC.

This solution also would allow you to do a quick restore incase of hardware
failure (ie. bad drive etc).

-Adam

Did you ever figure out a good way to do this? I have the same problem,
and I don’t have “ghost”, whatever that is. A QNX guy told me to nfs
export a cdrom drive on another networked qnx machine and install from
there, but unfortunately I don’t know how…

Actually I guess my problem is a little different because I have QNX 6.0
B running on the panel PC, but I don’t know how to upgrade to 6.1 from a
remote repository. (my intranet firewall won’t let me connect to the
qnx WWW repository). The way I got QNX 6 installed in the first place
was to install QNX 4 from floppy, then ftp qnxrtp.tar.F (name correct?)
which was a self installing archive for QNX 4. I don’t know if QNX is
still making that available. Anyway, it is a pretty akward route.

Jim Douglas wrote:

I have some industrial PCs equipped only with Floppy, ZIP & Hard disk
drives. It is not possible to temporarily connect a CD drive to the IDE bus.
I would like to install a full, exclusive QNX6 system onto them for the
purposes of developing an application. The machines have access to a
network, so, if I could get a basic system installed e.g. the equivalent of
installing from qnxrtp_rel_small.iso, the additional ‘bells and whistles’
can be added from a remote repository.

The simplest solution would be to copy the contents of qnxrtp_rel_small.iso
onto a ZIP drive and to modify the boot image used on the CD to mount a ZIP
drive instead of a CD drive. The source code for this boot image does not
appear to be in the public domain(?)

Has anyone any comments on the above or any alternative suggestions?

Jim Douglas

Hi Bruce/Jim.

paul.may:
the best way that i`v used in the past to eather mount the large RTP.ISO
image directly on the small RTP install then just point the installer
at that fake CD to install all the rest.

in Jims (others) case is it safe? to assume some form of windows is
installed on his panelPC? machines.

if so then he might get say windows freeware “daemon” to mount
the raw RTP>ISO http://www.daemon-tools.com .

from inside an RTP already installed:
mount -t /fs/hd0-dos-3/qnxrtp.iso /This-Is-The-CD-iso-on-a-windows-Partition
(assuming you have a local DOS drive to copy the ISO to AND
use a real name for that /this-is… bit, just thought i`d make
that clear incase some people didnt quite realise LOL
/cdrom2 would be fine).

it also seems that RTP mount doesn`t like the .ISO in a sub dir eather
so place it on a top dir somewere before mounting.

if you dont have a local DOS drive to place the full RTO.ISO on,
but can access a remote windows machine
then it MIGHT be possible to CIFS that machines drives THEN mount as above?
allowing for the CIFS mount entry inplace of /fs/hd?whatever/qnxrtp.iso
i didnt try this (CIFS then mount)but give it a go, it cant heart.

fs-cifs -a -b //windows2:192.168.0.9:/c /allansC user password &
fs-cifs -a -b //windows2:192.168.0.9:/d /allansD user password &
fs-cifs -a -b //windows2:192.168.0.9:/e /allansE user password &

for instance, remembering to replace my windows2?:192.168.0.9:/?
and allans? with your relevent info.

from a PanelPC with windows 98se installed:
(what are these ? spec,size,price ect, perhaps useful
for a small VHS size RTP based router,DHCPD,telnetD,FTPD, more ?,
doest RTP even have a working native DHCPD,router(d?),DNS server demon?)

as above BUT you need to use Daemon to first grab the small windows
install off the full RTP.ISO and install that into a binary image
inside windows (my prefered way to use and backup RTP)
or to a seperate drive partition before mounting a fakeISO to
get the full RTP developers apps ect.


as another option that might work for some:
as for useing ghost, while that MIGHT work?, (its written in Vbasic
and i`v had it crash for me and showing its true colours on several
important jobs, Drive ImagePro seems far better at not crashing when
you least want it to, so that makes DIP way above Ghost IMO, although
that to is written in a BASIC (i seem to remember it crashed once,
i personally dont consider BASIC a reliable language for such a
critical app such as drive imaging least of all Microsoft basic).

id have thought that
its would be far better to simply use RTP binary images inside
a dos formated drive if your into testing/changing RTP drive content
on a regular basis.

cant get simpler than making a 640meg sized RTP image that can be written
to 80 min cdrw , if someone EVER decides to write an RTP mount command
that can packet write to standard CDRW drives then i could have portable
self contained RTP setups for almost any situation.

as long as you have a close enough speced desktop windows machine to
your targets (GFXs,netcard ect)and you are able to transfer the
c:/program files/qnx*/boot/fs files to your target dos formated c drive
and edit its config.sys to start the RTP image, or d,e,f,whatever drives
you see fit to have in the DT/target machines.

this way only the desktop machine needs windows installed so as to
create your first working RTP image, the targets only need a dos formated
drive (i assume that an openDOS of some form would work ? just as well
if you dont want to be bothered with/have MS copywrite ?).

on a related note:
anyone willing and able to write eather/or an RTP style MOUNT command
that is able to mount any/all these formats as read/write extensions
to the RTP platform filesystem,and make it generally available to
interested users (perhaps even the source to help others learn how
they might also produce interesting/useful original apps/extensions
to the RTP platform rather than concentrate on turning RTP into Linux
by porting ALL *nix apps as is to RTP.

…hdf, amiga UAE hardfile in this binary image format
hardfile=access,secs,heads,reserved,bsize,file
(see the UAE opensource how they make hard disc image)

…adf, amiga UAE floppyFile i.e straight binary image (900k total)
of any real amiga floppy (mostly 880k but can be high density
or even custom sizes) again see UAE source for insight.

…lha, popular amiga/other crunched/packed file format

…zip as above but mostly wintel although used also on amiga

…gz Ect
as a mount point for the RTP or perhaps another way i might note have
mentioned here?.

of all the above id rate the .hdf and .zip as the most usable to me/others
given that now AmigaXL RTP exists, although i`v wanted these for a lot
longer (i DO like my CED finest editor ever,Thor worlds best and only
Email/News/…/FIDO/QWK/ABBS/HIPPO/BBBS/OMEN/UQWK_SOUP/UUCP reader LOL)
and sid2 classic amiga filemanager .

it might be nice if someone also saw fit to take the RTP binaryImage format
and build a tool to read/write to any RTPhardfile image inside windows,
or make an Amiga device driver so we could mount them inside
amiga dos (weather real or emulated/simulated amiga).

lastly, on a totally unrelated matter while i remember to ask,
does anyone know of a freeware TelnetD demon that works on windows 98SE ?

i want to be able to access several remote win98se machines though telnet
FROM an RTP and master windows machine hence they need telnetD demons on
them before i can run dos scripts (Wget and other dos type remote control).


Did you ever figure out a good way to do this? I have the same problem,
and I don’t have “ghost”, whatever that is. A QNX guy told me to nfs
export a cdrom drive on another networked qnx machine and install from
there, but unfortunately I don’t know how…

Actually I guess my problem is a little different because I have QNX 6.0
B running on the panel PC, but I don’t know how to upgrade to 6.1 from a
remote repository. (my intranet firewall won’t let me connect to the
qnx WWW repository). The way I got QNX 6 installed in the first place
was to install QNX 4 from floppy, then ftp qnxrtp.tar.F (name correct?)
which was a self installing archive for QNX 4. I don’t know if QNX is
still making that available. Anyway, it is a pretty akward route.

Jim Douglas wrote:

I have some industrial PCs equipped only with Floppy, ZIP & Hard disk
drives. It is not possible to temporarily connect a CD drive to the IDE
bus. I would like to install a full, exclusive QNX6 system onto them for
the purposes of developing an application. The machines have access to a
network, so, if I could get a basic system installed e.g. the equivalent of
installing from qnxrtp_rel_small.iso, the additional ‘bells and whistles’
can be added from a remote repository.

The simplest solution would be to copy the contents of qnxrtp_rel_small.iso
onto a ZIP drive and to modify the boot image used on the CD to mount a ZIP
drive instead of a CD drive. The source code for this boot image does not
appear to be in the public domain(?)

Has anyone any comments on the above or any alternative suggestions?

Jim Douglas

Paul May, Manchester, UK,
Phoenix Core © 1999, Phoenix Developer Consortium © 2000, Team Phx © 1999
Phinixi Technologies International LTD © 2000, Phinixi © 2000