That is the biggest prob i encountered also... QNX seems like a great OS, but sadly it does virtually have no software at all  :-( Even BeOS seems to have more.. atleast the last time i checked

It's a shame that QNX isn't more popular, it's way better than  Linux IMO, at least from a user perspective.

There's a few links to repositories on the QNX site  here.

QNX is nice in terms of performance and design, but...

The available range of software is very limited, and ports tend to lag behind most other versions. Driver support tends to be rather limited too (a situation which gets worse if you want more than the generic functions available to various devices).

QNX would make a decent desktop system if QSSL saw that as a priority and so pumped some more resources into it. However, the QNX RTOS is really intended as a developer's system to support development of applications for the QNX core business (embedded systems etc.). As such, you won't get the kind of features you will find on other systems, like fully featured 3D drivers, support for all sorts of peripherals, built-in component drivers etc.

For me, QNX never made it past the "cute but not very useful" barrier, which is a shame.

OT:

Nightcrawler wrote:

-edit: BTW didn't Gateway or whoever mean to base their AmigaOS on QNX? I seem to remember something like that...

Yep... then they suddenly switched to Linux... it was weird. Then those plans were scrapped. QNX could have make a very good core for the next generation AmigaOS, from what I read around that time.

Link here and here.

Whats the difference between the versions of qnx? I had one once, but i dont think it liked my card or something, cause it was very very very slow. I think it was QNX 4 or something... whats neutrino all about? what are all these QNXs?

After the Gatemiga paper switch to Linux, QNX the company predicated its moves to work on a user desktop on phase5 partnership. When phase5 no longer showed any ability to pursue its part of the partnership, QNX still had some hope that it could leverage its plans toward a self-hosted DEVELOPMENT desktop to dovetail with a sustained climb toward multi-hardware-platform user desktop amenities, including improvements on Amiga-specific concepts such as datatyping, and process managers providing compatibility layer/APIs, and  some more efforts to widen the application base beyond *nux/nix ports.

But when less and less Amiga community interest was shown because a lot of the Amiga-conversant developer base they hoped would participate - with a need for a deep partner(s) with phase5-level skills - was instead being drawn toward Amiga DE development, they began to prioritize differently, leveraging the demand they enjoyed in telecom, aerospace, mobileGT, and industrial and embedded even more than before.

Because of breakdown in negotiations between Amino (now the new Amiga Inc) and QNX (QNX could see no realistic business plan from Amino and did not like the Amino approach toward relationship-building), Tao was hastily chosen to keep from dieing stillborne - either because (1) Amiga Inc didn't do its homework in looking for an alternative that would do what they claimed they wanted to do at Gateway2000, or (2) they had no real intentions to deal with the desktop and the home gateway concepts, instead just wanting to string the community along while they made further inroads with developers.

This really sapped the development pool and momentum QNX was interested in that would have complimented the *nixy types pretty much guaranteed by POSIX compliance, and the embedded developers who were already working with the older QNX (pre-6.x) codebase. After alpha and beta testing and some early apps ports it became obvious to Phoenix that some of us had to look for major finance and talent to build on QNX for our needs. Indeed, most of us preferred QNX for modern desktop potential and for embedded spinoffs.

Fortunately, after dealing with sharks of various tooth size and not wanting to sell all our work for loss of control the VC sharks insisted on, we saw that Genesi was forming and had a strong interest in multi-OS work, and in both desktop and embedded work. Just in time, from my perspective!

Today its pretty obvious that Tao's multiplatform approach was designed for other uses entirely, and it seems a shame that QNX's multiplatform approach wasn't finally to get more desktop emphasis. But QNX itself has done very well in expanding its base and its potential, which only seems to intersect the desktop for the average user slightly.

Phoenix still has people doing QNX stuff, and Genesi is involved in making sure QNX is ported and that a business relationship with QNX is thereby developed. QNX is waiting for Peg2 after having ported to Peg1. When Peg2 porting and testing is done (should go fairly quickly given the speed of getting it happening with Peg1) it will be time to seriously consider product using the two.

Nightcrawler :  I am particularly interested in the paragraph quoted above. Will this be a straight port, or will there be any "amigafication" done to it? Should I stop waiting for Aone lite/micro/whatever, and start waiting for PegII instead?

It'll be a port of QNX as it stands today. It's unlikely that any Amigafication will take place at the beginning. Genesi already has MorphOS for that. QNX on the other hand has established itself as suitable for mission critical use and provides developers of embedded and industrial solutions with pretty much all that is needed to build totally robust products.

At the start at least, the main thing is to make the Pegasos product line available to companies and developers who already use QNX, or consider it when spec'ing product designs.

You can still wait for Peg2 though : }}} - and it won't be long, maybe a couple weeks. I think the initial 1500 that have been required elsewhere are probably just about done.

Oh, and two days running - still impressed

QNX is getting into the 99.999% reliability category, which may smack of marketing, but has some basis in reality ; } ...And this can happen in transparent networking on a variety of hardware including SMP machines.

Do check out the URLs that were provided earlier in the thread, in spite of the non-consumer-desktop emphasis (as a developer desktop it excels, partly because of their involvement in eclipse), there are a variety of applications that developers have brought over to use QNX in place of other nixxy systems because they prefer the smaller footprint, the performance, and the microkernel architecture.

Glad you are liking it, Nightcrawler : }  QNX has a lot of great people so I always enjoy seeing some appreciation of their efforts.