mkifs boot floppies

Is there a way via the standard command line utilities (strip ?)
to duplicate mkifs’es strip the usage and headers feature ?

I bumped up against the PC BIOS >640K boot image limit. But then I
started copying extra utils on the other 800K left on the floppy.

But I would like to try to fit a little bit more.

anyone have a suggestion for stripping off the leading #[media] ?

I’ve tried- file=${media###[media]}

Michael J. Ferrador <n2kra@orn.com> wrote in message
news:Voyager.010401155024.14245920B@aptiva.localdomain

Here are the scripts I’ve built up - so far.

I was attempting to create a pseudo-attribute #[media] that gets
parsed by bld2flp. So by editing the .build file you can move
a file from the boot image to boot media or back.

I have discoved that you can use full pathnames, no problems,
in a build file (I have parsed PATH’s before, but by changing
IFS=: -so I’m not sure what it would have done in an inner
for dir in grep PATH -while an outer- for file in media

plus the PATH in the build file looked not easy to isolate)

bld2flp takes a .build file w/o the .build extension

Previously, Michael J. Ferrador wrote in qdn.public.qnxrtp.installation:
Is there a way via the standard command line utilities (strip ?)
to duplicate mkifs’es strip the usage and headers feature ?

I bumped up against the PC BIOS >640K boot image limit. But then I
started copying extra utils on the other 800K left on the floppy.

But I would like to try to fit a little bit more.

strip -o /dev/fd0/$file -p $file

But do I have to be careful which files to strip,
and how do I strip the usage sections ?

I’m received:
Path=0 - i82077
target=0 lun=0 Direct-Access(0) - fdc i82077 Rev:
Unable to access “/dev/fd0” (2)
mount: can’t mount /proc/boot (type qnx4)
mount: Possible reason: Invalid argument

It is true: /dev/cd0 exist, but /dev/hd0 & /dev/fd0 aren’t present after
start from floppy :frowning:
All EIDE devices are visible during driver’s start, but:
ls /dev
con1 console mem shmem tty
con2 kbd null text zero

Whats wrong?

Sergey Zhukov.

“Michael J. Ferrador” <n2kra@orn.com> ???/??? ? ??? ???:
news:Voyager.010410180718.1159201A@aptiva.localdomain

latest updates are attached

file=${media###[media]}
base=basename $file

strip -R QNX_usage -o /dev/fd0/$base -p $file

Previously, Michael J. Ferrador wrote in qdn.public.qnxrtp.installation:
anyone have a suggestion for stripping off the leading #[media] ?

I’ve tried- file=${media###[media]}

Michael J. Ferrador <> n2kra@orn.com> > wrote in message
news:> Voyager.010401155024.14245920B@aptiva.localdomain> …

I was attempting to create a pseudo-attribute #[media] that gets
parsed by bld2flp. So by editing the .build file you can move
a file from the boot image to boot media or back.

I have discoved that you can use full pathnames, no problems,
in a build file (I have parsed PATH’s before, but by changing
IFS=: -so I’m not sure what it would have done in an inner
for dir in grep PATH -while an outer- for file in media

plus the PATH in the build file looked not easy to isolate)

bld2flp takes a .build file w/o the .build extension

strip -R QNX_usage -o /dev/fd0/$base -p $file

Previously, Michael J. Ferrador wrote in
qdn.public.qnxrtp.installation:
Is there a way via the standard command line utilities (strip ?)
to duplicate mkifs’es strip the usage and headers feature ?

I bumped up against the PC BIOS >640K boot image limit. But then I
started copying extra utils on the other 800K left on the floppy.

But I would like to try to fit a little bit more.

strip -o /dev/fd0/$file -p $file

But do I have to be careful which files to strip,
and how do I strip the usage sections ?