QNX Gurus Please Help. Problems with 6.2 installation.. It's

QNX Newsgroups (Archives) comp.os.qnx
1

Hello all,

I know this is a bit long, but I’ve tried to explain the
problems that I’m having in hopes of getting some help
or advice. Please take the time to read it. I’m in serious
need of help! :slight_smile:

I have probably repeated myself several times, and I appologize
for that. I’m desperate! :0

I am having a problem with QNX Nutrino 6.2 that I
hope someone can help me with,

I first learned about QNX a few years back when
there was talk of the new Amiga OS being built on
top of the QNX kernel. I downloaded the demo disk
and gave it a try. It was quite impressive. It would have
been very nice to have used this kernel for a new
Amiga OS. I really hated it when this planned fizzled
out. This would have been a kick ass combo!

Later on, a year or so ago I purchased AmigaOS_XL
from Haage & Partner which has the AmigaOS running
on top of QNX itself. I really like the AmigaOS, and
my Amiga applications absolutely fly on these two
Athlon XP 2400+ and 2200+ boxes that I have here.
In the meantime I have also learned a fair amount
about QNX.

The AmigaOS_XL package came bundled with QNX Nutrino
6.1. A few weeks ago I thought I would upgrade my setup
to QNX Nutrino 6.2 so I could install and run the newer
apps on QNX like Mozilla for instance.

Let me state at this point that the problem I’m having has
nothing to do with the AmigaOS. It still runs flawlessly on
6.2. The problems are with 6.2 itself.

QNX 6.1 installed and ran flawlessly the whole time I used
it. All of my hardware with the exception of my new Audigy
soundcard are supported by both 6.1 and 6.2. Sound on QNX
nor the AmigaOS are a huge concern for me at the moment,
but I do hope you have support for the Audigy in the future. :slight_smile:

Anyway…

My machine consist of an Abit KX7-333 RAID motherboard,
Athlon XP 2400+, 1.5GB of RAM, GeForce 2 Ti gfx card, etc.
I am not using the RAID controller at this time and it is
disabled. I have replaced the Soundblaster with an Audigy
which leaves all of my other hardware compatible as far as
I can tell. It all worked fine with 6.1.

The other machine has an Abit KX7-333 non RAID motherboard,
Athlon XP 2200+, 512MB RAM, nVidia TNT2 gfx card, etc. The
problems I’m having with 6.2 occur on both machines. They
both have the latest motherboard drivers, BIOS updates, etc.

I like these motherboards, because they are nicely made and do
not have a bunch of built on junk. I consider this a feature. :slight_smile:
They have just the basics. 6 PCI, 1 AGP, PS/2 keyboard and mouse,
Parallel & Serial, and USB. That’s it, nothing else, just the way
I like it.

When I boot QNX 6.1 off the CD it boots using DMA, and when it
is installed it also uses DMA and boots off of .boot. The QNX
6.2 CD boots using DMA and the .boot file too.

However, when I install QNX 6.2 it will not use DMA and it
will not boot using .boot. I have to use .altboot to boot into
QNX. I cannot for the life of me understand this, because QNX
6.1 boots using DMA and .boot both from the CD and on a HD
installation, and QNX 6.2 boots using DMA and .boot from the CD,
but the harddrive installation will not. In fact it doesn’t seem
to even run properly from the CD. I have downloaded the ISO three
times and it is fine. I also tried a copy that someone else had
burned and I get the same results. I do not think it is a problem
with the ISO.

For instance when I boot 6.2 off of CD and Photon comes up, it
boots using DMA and .boot and everything seemed to work fine
until I tried to play an mpg movie either from the internet or
from disk. It says mpegsystem not found, so I thought I’d go ahead
with the full install. 6.1 will play mpeg video perfectly from the
CD and with an installation.

After installing QNX 6.2, it will not boot using DMA and I have
to use .altboot to get the machine to boot into QNX. QNX 6.1 had
no such problem. After a complete install of QNX 6.2 still I cannot
view an mpg movie. Again, here it says mpegsystem not found? But
that is not the end of it.

When I boot and just let it go where it should be using DMA and
…boot which QNX 6.1 has no problems with, it stops after Detected
EIDE. Scanning for devices and says one of three things:

It says:

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to locate fs-pkg.
(The .diskroot file shows empty…btw?)

or

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to find library.

or
Diskroot file for root not found on any filesystem.
Starting with safemode.
Spawn of binsh failed. No such file or directory.

Most of the time I get the first one…unable to locate fs-pkg.
After anyone of these it just stops completely.

However it boots fine using .altboot, but still it will not play
mpeg videos as it says it cannot fine mpegsystem. Something is
wrong with its libraries once it is installed and I don’t know
what it is! :confused:

All of this is very strange, and I have installed 6.2 around 6
times now, using 4 different CDs burnt with different ISOs. They
all do the exact same thing when installed, althought all the CDs
boot using DMA and .boot. Again, no mpeg videos can be viewed using
any of them from CD nor when installed. It is always mpegsystem
cannot be found.

Before I forget it, I have tried the installs with and without the
updates 6.2 updates. The result is the same. 6.2 still doesn’t
install properly or work properly itself. However, the AmigaOS runs
just fine with the exception of having no sound due to the Audigy,
and with 6.2 I lost support for the mouse wheel while using the
AmigaOS and apps. That is strange in itself because it works fine
while using QNX 6.1.

I do realize that the AmigaOS_XL package was done with QNX 6.1,
but again the AmigaOS is not the problem. With the exception of
losing the wheel on the mouse with 6.2 it runs perfectly and is
much faster than any of my real Amigas.All of my image and rendering
apps for the Amiga are lightening fast! My problem is something
with QNX and I cannot figure out what the problem is. :0

I could always go back to 6.1, because I know it will boot using
DMA and .boot, but since your company made the change in the way
the packages are installed, I cannot take advantage of things like
Mozilla, etc. I really don’t understand why the change in
installation was made, but I guess there is a reason? If the
installer hadn’t changed, I could probably use Mozilla, etc.
with 6.1?

I saw on a post on here that there is a Mozilla for 6.1 but it is
in tar.gz format, and I’m not sure how to install such a package in
QNX. At this point, if the installer doesn’t install it I’m lost. :confused:
Any help as to how to install these tar.gz packages would be greatly
appreciated as well.

Anyway, I have tried to rename .boot to .altboot and .altboot to
…boot, so I don’t have to grab that ESC key before it tries to
boot up using DMA and .boot. The machines are both really fast
on bootup. :slight_smile:

I have not been able to rename either of those files to avoid
having to grab that key. I have tried to mount the QNX partition
in Mandrake Linux in hopes that I could rename those files from
there but I haven’t had any success with that either.

Does anyone have any thoughts on what might be going wrong with the
6.2 installation?

Why 6.2 will not use DMA and boot using .boot when QNX 6.1 does?
And why does it boot using .boot from the CD?

Why are the libraries like the mpegsystem it claims it cannot find
not installing properly?

Why it claims it cannot find the fs-pkg? Etc…

Is there any possible way for me to revert back to 6.1 and get
the new packages installed using the old installer? Someone on
the AmigaOS_XL mailing list claimed they had been able to do it
by creating another repository? Is this even possible?

I still don’t understand the installation package change. :confused:
It does kinda foul the works up with 6.1. Perhaps there is a reason
for the change?

Also, is there any way for me to rename .boot and .altboot so I
don’t have to try to catch the ESC key if it continues to refuse
to boot using DMA and .boot? Apparently they cannot be renamed while
QNX is running, and I’ve not been able to get to them while it is
not running.

Any help would be appreciated. I have tried to get help with this
on the AmigaOS_XL mailing list, but have had no luck yet. Others
have upgraded to QNX 6.2 for the same reasons as myself. To be able
to continue to run the AmigaOS and apps, and to take advantage of
the newer apps for QNX. Some have had no problems and othes have
had problems similar to mine and even worse like TCP/IP issues, etc.
which they did not have using 6.1.

QNX 6.1 seems to work perfectly for everyone, and for some reason
6.2 seems like it is a hit and miss. No one is having any trouble
with the AmigaOS running on 6.2! AmigaOS runs perfectly with
the exception of the loss of the use of the mouse wheel upon installing
6.2, Otherwise it works like a charm.

The problems people are having are with QNX 6.2. I would really
like to figure out what is going on, and why it doesn’t seem to
install properly, why it will not boot using 'DMA when 6.1 does
(others are having this problem as well), Again this is very
strange because the 6.2 CD boots using DMA and .boot and so does 6.1,
but 6.2 will not do it once installed?

All of my hardware as far as I know is suppoted by QNX. 6.1 had
no problems with it, and with the exctption of the Audigy in one
machine, nothing else has changed.

Some people have speculated that QNX does not like VIA chipsets?
6.1 had no problems with my Abit KX7-333 RAID motherboard nor
the other KX7-333 without RAID. Other than different harddrives,
one mobo having RAID and the other not the computers are basically
identical and QNX 6.2 doesn’t work right on either one of them,
while 6.1 works flawlessly. Again, the updates on your pages do
not solve the problems.

The DMA is really not a huge issue, however it is something that
I do not understand why it is doing it. To me it seems as if 6.2
is not installing properly for some strange reason, but also some
things do not work properly boothing from the CD like mpeg videos,
while there is no problem whatsoever with 6.1. It is driving me
crazy. :slight_smile:

I think it would be nice to be able to reinstall or upgrade
QNX without wiping everything on the harddrive or partition out.
I do back all my Amiga stuff up, but still it would be nice if it
didn’t wipe everything out. Is this even possible?

I really enjoy being able to run all my Amiga apps and the AmigaOS on
QNX, but I also enjoy tinkering with QNX. I just wish I could figure
out what the heck is wrong with 6.2. :confused:

I’m writing this using YAM for the AmigaOS running on QNX 6.2
right now. The AmigaOS is fine, but again something is not right
with QNX 6.2.

Any help would be greatly appreciated if anyone has the time.
Before I forget, is there any planned support for the Audigy card in
the future? I would really like to get 6.2 right, because I do enjoy
tinkering with it, and I want to learn more about. It is a very nice
OS! :slight_smile:

Thanks in advance,

Lee Trice

2

Short answer:
Read the 6.2 release notes.
URL:http://www.qnx.com/support/releasenotes/momentics_62r.html#ISSUES

Longer answer:

turk@gulftel.com sed in <3E21B9E9.6000202@gulftel.com>:

6.1 boots using DMA and .boot both from the CD and on a HD
installation, and QNX 6.2 boots using DMA and .boot from the CD,
but the harddrive installation will not. In fact it doesn’t seem

What do you make believe that CD boot, and 6.1, is using DMA?

I believe 6.2 CD and boot-floppy had /.boot as non-DMA.
HDD installation will have /.boot for DMA, so “CD will boot but not HDD”
was a FAQ on 6.2. (Or forseen as it’s mentioned in relnotes)

And I doubt that even 6.1 was running with DMA; it only fellback to
PIO so “it works”.
Official method to know if it’s DMA was “benckmark it”.
(did devb-eide -vvvvv spit DMA modes? not tested…)

Or I may be missing some important point as
your post is way too long to wade through.

kabe

3

TLT <turk@gulftel.com> wrote:

My machine consist of an Abit KX7-333 RAID motherboard,
…
When I boot QNX 6.1 off the CD it boots using DMA, and when it
is installed it also uses DMA and boots off of .boot. The QNX
6.2 CD boots using DMA and the .boot file too.
…
However, when I install QNX 6.2 it will not use DMA and it
will not boot using .boot. I have to use .altboot to boot into
QNX. I cannot for the life of me understand this, because QNX
6.1 boots using DMA and .boot both from the CD and on a HD
installation, and QNX 6.2 boots using DMA and .boot from the CD,
but the harddrive installation will not.

There is at least one VIA chipset that has DMA issues. I had one on
the motherboard I had and had to replace it. I did a quick search
for the KT333 chipset on your motherboards, and there are problems
reported with it and DMA on linux, to the tune where the RedHat 7.x
distributions lock DMA OFF for that chipset.

Now, let me explain why DMA worked in 6.1 but failed in 6.2

The disk drivers in 6.1 were only able to run at DMA-2, which as it
happens, does not tickle any of the DMA bugs in the VIA chipsets
that have the DMA bug. In 6.2 they “fixed” this and the drivers are
now capable of running at DMA-5. Unfortunatly this is where the
buggy behaviour occurs.

There are only two solutions for you.

  1. run without DMA
  2. replace the motherboard with one that has a functioning chipset

I know that isn’t what you wanted to hear, but that is the reality
of it. Perhaps in a future version of QNX the disk drivers will
provide more control of DMA than just on/off, and allow you to set
the actual level of DMA used. If/when that happens, you will be
able to use DMA-2 on these systems.

My reccomendation is to replace the motherboards. They should be
the cheapest component in the system. :slight_smile:

Cheers,
Camz.

4

Looking at the docs for devb-eide in the Helpview, I noticed that there
is a “udma=mode” command line to override the DMA level. If the system
is stable enough, maybe you could tweak /boot/build/qnxbasedma.build to
force DMA level down to 2? You would change the “diskboot” line to
something like this:

[pri=10o] PATH=/proc/boot diskboot -b1 -D1 -odevc-con,-n4 -o
“devb-eide,eide udma=2”

And then rebuild your .boot file (“mkifs /boot/build/qnxbasedma.build
/.boot”). Although I’m worried that diskboot might not add the new
options to command line properly. In which case, devb-eide will probably
ignore them and your only alternative is to remove diskboot and manually
do what it does (not pretty, but do-able).

Good Luck!
Daryl Low

camz@passageway.com wrote:

TLT <> turk@gulftel.com> > wrote:

My machine consist of an Abit KX7-333 RAID motherboard,

…

When I boot QNX 6.1 off the CD it boots using DMA, and when it
is installed it also uses DMA and boots off of .boot. The QNX
6.2 CD boots using DMA and the .boot file too.

…

However, when I install QNX 6.2 it will not use DMA and it
will not boot using .boot. I have to use .altboot to boot into
QNX. I cannot for the life of me understand this, because QNX
6.1 boots using DMA and .boot both from the CD and on a HD
installation, and QNX 6.2 boots using DMA and .boot from the CD,
but the harddrive installation will not.


There is at least one VIA chipset that has DMA issues. I had one on
the motherboard I had and had to replace it. I did a quick search
for the KT333 chipset on your motherboards, and there are problems
reported with it and DMA on linux, to the tune where the RedHat 7.x
distributions lock DMA OFF for that chipset.

Now, let me explain why DMA worked in 6.1 but failed in 6.2

The disk drivers in 6.1 were only able to run at DMA-2, which as it
happens, does not tickle any of the DMA bugs in the VIA chipsets
that have the DMA bug. In 6.2 they “fixed” this and the drivers are
now capable of running at DMA-5. Unfortunatly this is where the
buggy behaviour occurs.

There are only two solutions for you.

  1. run without DMA
  2. replace the motherboard with one that has a functioning chipset

I know that isn’t what you wanted to hear, but that is the reality
of it. Perhaps in a future version of QNX the disk drivers will
provide more control of DMA than just on/off, and allow you to set
the actual level of DMA used. If/when that happens, you will be
able to use DMA-2 on these systems.

My reccomendation is to replace the motherboards. They should be
the cheapest component in the system. > :slight_smile:

Cheers,
Camz.

5

It is meant to be empty. The mere presence of the file tells diskboot
that this file system is supposed to be the “root” read-write file
system. If it finds two file systems with /.diskroot, it will ask which
one you want mounted as “/”. All other regular file systems end up under
“/fs”.

Daryl Low

cyberbot@softhome.net wrote:

Do you by any chance know why the file /.diskroot is empty? I imagine
that is why I get the messages below and the one above. The file
contains nothing! :confused:

6

camz@passageway.com wrote:

TLT <> turk@gulftel.com> > wrote:

Thanks for the reply Camz. :slight_smile:

There is at least one VIA chipset that has DMA issues. I had one on
the motherboard I had and had to replace it. I did a quick search
for the KT333 chipset on your motherboards, and there are problems
reported with it and DMA on linux, to the tune where the RedHat 7.x
distributions lock DMA OFF for that chipset.

Mandrake 9.0 seems to be fine with the mobo. Go figure! :confused:


Now, let me explain why DMA worked in 6.1 but failed in 6.2

The disk drivers in 6.1 were only able to run at DMA-2, which as it
happens, does not tickle any of the DMA bugs in the VIA chipsets
that have the DMA bug. In 6.2 they “fixed” this and the drivers are
now capable of running at DMA-5. Unfortunatly this is where the
buggy behaviour occurs.

There are only two solutions for you.

  1. run without DMA
  2. replace the motherboard with one that has a functioning chipset

Well apparently /.altboot once it is installed is non-DMA. I have tried
to rename /.boot to /.altboot and /.altboot to /.boot in hopes that I
won’t have to grab the ESC key on each bootup. I haven’t been able to
do so. It seems that I can’t write them while QNX is running. I’m not
really competent on QNX, but I’m trying to learn. I like it! :slight_smile:

I’ve even tried mounting the QNX filesystem in Mandrake in hopes of
being able to rename them from there and do the switch, but I haven’t
been sucessful with that either. :0

Do you know how I can rename the two files so that the machine think
that /.altboot is infact /.boot. I’ve been told this could be done, but
I have been unable to do so. It was never really explained to me, other
than it can be done. :confused:

Anyway…the DMA isn’t bothering me that much, and I can live happily
using non-DMA, but I’d like to rename those two files so it will just
boot up without having to grab the ESC key each time.

What is really bugging me is that when I try to boot using /.boot which
I’m assuming is DMA I get one of three error messages. They are:

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to locate fs-pkg.

(The .diskroot file shows empty…btw?)I can view all of the QNX files
from the AmigaOS using Directory Opus Magellan and the .diskroot file
just shows as an empty file, as it does in the QNX File Manager. What
would be causing this, and what size should it be? How can I repair
or replace this file with one that is correct?

or

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to find library.

(I’m not sure what library it is referring to. It might be the
mpegsystem which it cannot find to play mpeg video?)

or
Diskroot file for root not found on any filesystem.
Starting with safemode.
Spawn of /bin/sh failed. No such file or directory.

(Here again the strange thing is that /bin/sh does exist!)

Most of the time I get the first one…unable to locate fs-pkg.
After anyone of these it just stops completely. Any thoughts on
why it would not be able to locate the fs-pkg as well.

The only other thing I’ve notices is than when trying to play mpeg video
QNX 6.2 fails, again 6.1 works perfectly. 6.2 tells me that mpegsystem
cannot be found. The same thing happens even using Mozilla, it looks for
the mpegplugin but the video never shows. I’m assuming this is bacause
QNX cannot find its own mpegsystem. Would that be right, and what could
be causing this to happen. It seems that things are just not installing
properly to me. :confused:

I know that isn’t what you wanted to hear, but that is the reality
of it.

My reccomendation is to replace the motherboards. They should be
the cheapest component in the system. > :slight_smile:

I am happy to hear anything, and to get some advice from anyone. I could
and might replace the mobo. It wouldn’t be that big of a deal, but on
the other hand I can live without using DMA. I would just like to be
able to change /.boot to /.altboot and /.altboot to /.boot so I don’t
have to try and catch the ESC key. Also, I would like to figure out
why mpeg video will not play in 6.2 as well. It works perfectly in 6.1.
:confused: Also, I don’t understand why the /.diskroot file is empty.

I wanted to upgrade to 6.2 to be able to use Mozilla, AbiWord, etc. Does
anyone know if there is any possible way to install the newer packages
like these and other can be installed on 6.1. I know the package
installer has changed (I don’t understand why…btw), but if there was a
possibilty of installing these on 6.1 please let me know.

I read on another thread here that there is a Mozilla available for 6.1.
In checking on it, I find it compressed using tar.gz. Could you or
anyone tell me the proper way to install packages that are not in the
installer format? I have no problem unarching them, I just don’t know
how to manually install something on the QNX OS at this point in time!

QNX 6.1 ran flawlessly and everything worked fine. I could always go
back to 6.1, but if there is no way to install the newer packages it
would be a shame to have to do so. I really like things like Mozilla,
AbiWord, phPostal, etc.

Thanks again for the information and advice. I really appreciate it. If you
or anyone else could help me with the other problems mentioned above I
would be overjoyed! :slight_smile:


Cheers,
Camz.

7

<cyberbot@softhome.net> wrote in message
news:3E2306A6.1010100@softhome.net…

camz@passageway.com > wrote:
TLT <> turk@gulftel.com> > wrote:

Thanks for the reply Camz. > :slight_smile:

There is at least one VIA chipset that has DMA issues. I had one on
the motherboard I had and had to replace it. I did a quick search
for the KT333 chipset on your motherboards, and there are problems
reported with it and DMA on linux, to the tune where the RedHat 7.x
distributions lock DMA OFF for that chipset.

Mandrake 9.0 seems to be fine with the mobo. Go figure! :confused:


Now, let me explain why DMA worked in 6.1 but failed in 6.2

The disk drivers in 6.1 were only able to run at DMA-2, which as it
happens, does not tickle any of the DMA bugs in the VIA chipsets
that have the DMA bug. In 6.2 they “fixed” this and the drivers are
now capable of running at DMA-5. Unfortunatly this is where the
buggy behaviour occurs.

There are only two solutions for you.

  1. run without DMA
  2. replace the motherboard with one that has a functioning chipset

Well apparently /.altboot once it is installed is non-DMA. I have tried
to rename /.boot to /.altboot and /.altboot to /.boot in hopes that I
won’t have to grab the ESC key on each bootup. I haven’t been able to
do so. It seems that I can’t write them while QNX is running. I’m not
really competent on QNX, but I’m trying to learn. I like it! > :slight_smile:

I’ve even tried mounting the QNX filesystem in Mandrake in hopes of
being able to rename them from there and do the switch, but I haven’t
been sucessful with that either. :0

Do you know how I can rename the two files so that the machine think
that /.altboot is infact /.boot. I’ve been told this could be done, but
I have been unable to do so. It was never really explained to me, other
than it can be done. :confused:

Copy them instead of rename them. These special files can only be
overwritten. So:

cp /.boot /myboot

cp /.altboot /.boot

cp /myboot /.altboot

Anyway…the DMA isn’t bothering me that much, and I can live happily
using non-DMA, but I’d like to rename those two files so it will just
boot up without having to grab the ESC key each time.

What is really bugging me is that when I try to boot using /.boot which
I’m assuming is DMA I get one of three error messages. They are:

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to locate fs-pkg.

These are mostly because the scanning of harddisk is faliured.

-xtang

(The .diskroot file shows empty…btw?)I can view all of the QNX files
from the AmigaOS using Directory Opus Magellan and the .diskroot file
just shows as an empty file, as it does in the QNX File Manager. What
would be causing this, and what size should it be? How can I repair
or replace this file with one that is correct?

or

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to find library.

(I’m not sure what library it is referring to. It might be the
mpegsystem which it cannot find to play mpeg video?)

or
Diskroot file for root not found on any filesystem.
Starting with safemode.
Spawn of /bin/sh failed. No such file or directory.

(Here again the strange thing is that /bin/sh does exist!)

Most of the time I get the first one…unable to locate fs-pkg.
After anyone of these it just stops completely. Any thoughts on
why it would not be able to locate the fs-pkg as well.

The only other thing I’ve notices is than when trying to play mpeg video
QNX 6.2 fails, again 6.1 works perfectly. 6.2 tells me that mpegsystem
cannot be found. The same thing happens even using Mozilla, it looks for
the mpegplugin but the video never shows. I’m assuming this is bacause
QNX cannot find its own mpegsystem. Would that be right, and what could
be causing this to happen. It seems that things are just not installing
properly to me. :confused:

I know that isn’t what you wanted to hear, but that is the reality
of it.

My reccomendation is to replace the motherboards. They should be
the cheapest component in the system. > :slight_smile:

I am happy to hear anything, and to get some advice from anyone. I could
and might replace the mobo. It wouldn’t be that big of a deal, but on
the other hand I can live without using DMA. I would just like to be
able to change /.boot to /.altboot and /.altboot to /.boot so I don’t
have to try and catch the ESC key. Also, I would like to figure out
why mpeg video will not play in 6.2 as well. It works perfectly in 6.1.
:confused: Also, I don’t understand why the /.diskroot file is empty.

I wanted to upgrade to 6.2 to be able to use Mozilla, AbiWord, etc. Does
anyone know if there is any possible way to install the newer packages
like these and other can be installed on 6.1. I know the package
installer has changed (I don’t understand why…btw), but if there was a
possibilty of installing these on 6.1 please let me know.

I read on another thread here that there is a Mozilla available for 6.1.
In checking on it, I find it compressed using tar.gz. Could you or
anyone tell me the proper way to install packages that are not in the
installer format? I have no problem unarching them, I just don’t know
how to manually install something on the QNX OS at this point in time!

QNX 6.1 ran flawlessly and everything worked fine. I could always go
back to 6.1, but if there is no way to install the newer packages it
would be a shame to have to do so. I really like things like Mozilla,
AbiWord, phPostal, etc.

Thanks again for the information and advice. I really appreciate it. If
you
or anyone else could help me with the other problems mentioned above I
would be overjoyed! > :slight_smile:


Cheers,
Camz.

8

cyberbot@softhome.net wrote:

Daryl Low wrote:

Thanks Daryl for the information. I have now successfully done a copy
over of /.boot and /.altboot so I don’t have to grab the ESC key so
that now /.altboot is recognized as /.boot.

Glad that it worked for you.

I see that you are from QNX. Do you have any idea why the Photon Media
Player will not play mpeg videos? 6.1 worked like a charm, but since
upgrading to 6.2 everytime I try to play or view an mpegvideo I get a
message telling that says "Can’t load plugin ‘mpegsystem.so’.Even
Mozilla will not play mpeg videos, it says loading mpeg plugin and then
just dies.I’m assuming this is a result of QNX not being able to find
and/or laod mpegsystem.so? I have no idea why this is happening. 6.1
was flawless.

Also, I’d like to ask you if there is an audio library that supports
Audigy soundcards. If not perhaps in the future?

Unfortunately, my area of expertise is file systems. I’ll ask somebody
who might know (our CODEC / Media guy).

Daryl Low

9

Xiaodan Tang wrote:

cyberbot@softhome.net> > wrote in message
news:> 3E2306A6.1010100@softhome.net> …

Do you know how I can rename the two files so that the machine think
that /.altboot is infact /.boot. I’ve been told this could be done, but
I have been unable to do so. It was never really explained to me, other
than it can be done. :confused:

Copy them instead of rename them. These special files can only be
overwritten. So:

cp /.boot /myboot

cp /.altboot /.boot

cp /myboot /.altboot

Thanks Xiaodan. Now I have this problem solved! I appreciate it! :slight_smile:

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to locate fs-pkg.

These are mostly because the scanning of harddisk is faliured.

-xtang

Do you by any chance know why the file /.diskroot is empty? I imagine
that is why I get the messages below and the one above. The file
contains nothing! :confused:

Diskroot file for root not found on any filesystem.
Starting with safemode.
Unable to find library.

(I’m not sure what library it is referring to. It might be the
mpegsystem which it cannot find to play mpeg video?)

or

Diskroot file for root not found on any filesystem.
Starting with safemode.
Spawn of /bin/sh failed. No such file or directory.

(Here again the strange thing is that /bin/sh does exist!)

But all of this seems to be happening because of the empty /.diskroot
file. :confused:

Thanks again for the info on copying over the files instead of renaming
them to get them changed. It’s much appreciated! :slight_smile:

10

Daryl Low wrote:

Thanks Daryl for the information. I have now successfully done a copy
over of /.boot and /.altboot so I don’t have to grab the ESC key so
that now /.altboot is recognized as /.boot.

I see that you are from QNX. Do you have any idea why the Photon Media
Player will not play mpeg videos? 6.1 worked like a charm, but since
upgrading to 6.2 everytime I try to play or view an mpegvideo I get a
message telling that says "Can’t load plugin ‘mpegsystem.so’.Even
Mozilla will not play mpeg videos, it says loading mpeg plugin and then
just dies.I’m assuming this is a result of QNX not being able to find
and/or laod mpegsystem.so? I have no idea why this is happening. 6.1
was flawless.

Also, I’d like to ask you if there is an audio library that supports
Audigy soundcards. If not perhaps in the future?

Anyway…

Thanks again Daryl for the information. :slight_smile:


It is meant to be empty. The mere presence of the file tells diskboot
that this file system is supposed to be the “root” read-write file
system. If it finds two file systems with /.diskroot, it will ask which
one you want mounted as “/”. All other regular file systems end up under
“/fs”.

Daryl Low

11

I see that you are from QNX. Do you have any idea why the Photon Media
Player will not play mpeg videos? 6.1 worked like a charm, but since
upgrading to 6.2 everytime I try to play or view an mpegvideo I get a
message telling that says "Can’t load plugin ‘mpegsystem.so’.Even
Mozilla will not play mpeg videos, it says loading mpeg plugin and then
just dies.I’m assuming this is a result of QNX not being able to find
and/or laod mpegsystem.so? I have no idea why this is happening. 6.1
was flawless.

Also, I’d like to ask you if there is an audio library that supports
Audigy soundcards. If not perhaps in the future?

You need to symlink in libcpp.so.2 to libcpp.so.2a or nab this copy
of the binary: http://qnx.wox.org/qnx/libcpp.so.2a.gz.

The mpeg lib needs that shared lib and it was missed during the packaging of
NC for 6.2.0.

chris

–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

12

Chris McKillop wrote:

I see that you are from QNX. Do you have any idea why the Photon Media
Player will not play mpeg videos?

You need to symlink in libcpp.so.2 to libcpp.so.2a or nab this copy
of the binary: > http://qnx.wox.org/qnx/libcpp.so.2a.gz> .

The mpeg lib needs that shared lib and it was missed during the packaging of
NC for 6.2.0.

Thanks Chris for this info. I snagged the library and all is well with
the playing of mpeg video again. I appreciate the help.

Also, I would like to thank everyone who has offered advice. Thanks to
you all I have solved every issue that I had with 6.2, and now nderstand
that the empty /.diskroot was not the cause of my problems. Doh…

QNX 6.2 is now running like a charm, the AmigaOS is smokin’, and if I
had sound for the Audigy all would be perfect!!! :stuck_out_tongue:

Again, thanks everyone!