message unavailable
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public qnx.* groups
Bummer.
At least you could leave the original description at the end.
kabe
You are right!
I really don’t understand what happenned to the QNX community !?!
Alain.
kabe@sra-tohoku.co.jp a écrit:
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public qnx.* groups
Bummer.At least you could leave the original description at the end.
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:4010C1D5.6030307@icbt.com…
You are right!
I really don’t understand what happenned to the QNX community !?!
What is it you don’t understand?
Alain.
kabe@sra-tohoku.co.jp > a écrit:
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public
qnx.* groups
Bummer.At least you could leave the original description at the end.
I think the community is particularly silent this year!
Alain.
Mario Charest a écrit:
“Alain Bonnefoy” <> alain.bonnefoy@icbt.com> > wrote in message
news:> 4010C1D5.6030307@icbt.com> …
You are right!
I really don’t understand what happenned to the QNX community !?!
What is it you don’t understand?
Alain.kabe@sra-tohoku.co.jp > a écrit:
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public
qnx.* groups
Bummer.At least you could leave the original description at the end.
\
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:4014BB7D.2000104@icbt.com…
I think the community is particularly silent this year!
Other medium such as www.qnxzone.com www.openqnx.com (and more) IIRC have
develop recently that dilutes the voice of the community.
Plus the old timer aren’t has vocal as they use too.
Alain.
Mario Charest a écrit:
“Alain Bonnefoy” <> alain.bonnefoy@icbt.com> > wrote in message
news:> 4010C1D5.6030307@icbt.com> …
You are right!
I really don’t understand what happenned to the QNX community !?!
What is it you don’t understand?
Alain.kabe@sra-tohoku.co.jp > a écrit:
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public
qnx.* groups
Bummer.At least you could leave the original description at the end.
\
Mario Charest a écrit:
“Alain Bonnefoy” <> alain.bonnefoy@icbt.com> > wrote in message
news:> 4014BB7D.2000104@icbt.com> …
I think the community is particularly silent this year!
Other medium such as > www.qnxzone.com > > www.openqnx.com > (and more) IIRC have
develop recently that dilutes the voice of the community.
Not so sure most of the qnxzone forums didn’t see any post for the last
30 days.
About openqnx it could be interesting to discuss on this forum about
openqnx developments but I think it’s wasting resource (and time) to
discuss there or elsewhere about strictly qnx subject.
But that’s my point of view.
Alain.
Plus the old timer aren’t has vocal as they use too.
Alain.Mario Charest a écrit:
“Alain Bonnefoy” <> alain.bonnefoy@icbt.com> > wrote in message
news:> 4010C1D5.6030307@icbt.com> …
You are right!
I really don’t understand what happenned to the QNX community !?!
What is it you don’t understand?
Alain.kabe@sra-tohoku.co.jp > a écrit:
Instead of installing the new “charter” for new newsgroups,
all of the qdn.* charters were clobbered to
This group is read-only. Please see inn.qnx.com for available public
qnx.* groups
Bummer.At least you could leave the original description at the end.
\
Mario Charest postmaster@127.0.0.1 wrote:
Other medium such as > www.qnxzone.com > > www.openqnx.com > (and more) IIRC have
develop recently that dilutes the voice of the community.
there also other language qnx forums active, such as
qnx.org.ru, www.qnx-fr.com, cn.openqnx.com, etc.
5000 Euro Belohnung / 5000 Euro Reward --------------------------------------Ich biete eine Belohnung von 5000 Euro wenn mir jemand verraetwie ein Streetgame (International Money Game) die Leute um den Spieler herrum beeinflusst.Ich stecke in genau diesem Unfug drin und irgendjemand manipuliertalle Leute, denen ich begegne und Radio bzw. Fernsehprogramme, dieich beobachte.I offer a reward of 5000 Euro if anybody tells me how a streetgame(International Money Game) manipulates the people around the player.I’m currently trapped in something like that and somebody manipulateseverybody I meet and radio or TV programs I watch or listen to.http://www.fastenrath.net/, http://slashdot.org/~fastenrath/Bernhard FastenrathSteinfelder Gasse 1, 50670 Koeln, Germanyfon: +49-173-5166326fax: +49-69-13306976636email: fasten@hrs.com
Moved to qnx.cafe 
Igor Kovalenko <kovalenko@attbi.com> wrote:
“Robert Krten” <> rk@parse.com> > wrote in message
news:c5n5ar$6fg$> 1@inn.qnx.com> …
Mario Charest postmaster@127.0.0.1 wrote:“Robert Krten” <> rk@parse.com> > wrote in message
news:c5m3na$9cv$> 1@inn.qnx.com> …
I’m about to start investigating flash corruption on behalf of three
distinct customers; I don’t have very many details right at this point,
but the general consensus is that these devices “work just fine” under
Windows CE, DOS, and other OS’s, and “experience corruption” when used
with QNX 6. That’s all the “hard facts” I have at this point.The purpose of this post is to solicit input from the field on flash
corruption – I’m looking for things like model numbers, flash
technology
used, usage patterns when it failed, and whether this is a QNX
6-specific
problem or not (as far as you are able to tell). I’ll summarize the
results and analysis as much as I’m able to when given possible NDA
constraints etc.Maybe first thing is to upgrade to the lastest flash file system which
is
support to me more resiliant.Push the (perhaps repaired) car back up the hill and see if it does it
again? >I guess if QSS took to time to write/design a new flash file system is
because the old one wasn’t so resiliant after all >I’m working the other side of the house, Mario. I’ve given up my “cowboy
programming” ways (for this contract). One of the customers is a medical
instrument supplier, and it’s simply not an option to “just upgrade” in
the (perhaps vain) hope that it will help – there really should be a
documented quality process which the OS vendor follows, listing all of the
bugs, which versions they were found in, which versions they were fixed
in,
customer impacts, yaddy yaddy yaddy.
If QSSL had this (and I’m only guessing they don’t) then it would be a
simple matter to just jump in and say “Yes, the following flash corruption
issues were fixed in component X in version B”.THEN AND ONLY THEN would it make sense to upgrade component X from
version
A to version B, knowing that bugs J, K, and L were fixed in version B.
Well now. You obviously haven’t been working that side of the house long
enough >
No, I’m still enjoying myself
As you progress toward SEI CMM5 and then CMMI organisation model, you
eventually get to the point of really hating the stuff, because process
engineers required to maintain certain illusions and appearances starts to
outnumber the actual developers. They gonna be busy predicting how many
defects of each severity you will have at certain time on your next project
that you haven’t come up with yet.
As with anything, there’s a spectrum; I’ve worked on military contracts
where it’s more like what you describe. This one is about 80% of the way
there. Funny story: my father worked in SQA at BNR (now Nortel) and actually
did just that – predicted when a bug would be found in the (then flagship)
DMS-100 software. This after the VP had declared that there are no more bugs
and the software is “done”. Sure enough, my dad’s prediction came to pass
to the day Needless to say, that department was soon disbanded.
That said, a proper source control system integrated with defect tracking
and build labeling is a requirement for any respectable software company.
Yup.
That means capability to reproduce any officially released build at any
time.
Yup. Or at least archive all the source and binaries for all officially
released builds, so that you can at least refer to them and track down
problems.
Beyond that, a company employing about 40 actual developers and just
over a hundred total employees neither can afford nor really needs all the
yaddy yaddy. It can do better with more agile software processes. That
should not cloud the fact that it might indeed benefit from having a process
at all >
Yup.
P.S. Sorry for the rant – I’m doing traceability matrices from
functional
specifications to system architecture to detailed software design docs –
you
just get into that mindset after a while. It’s not all bad, some of it is
sorely needed in other areas of software development. For the long answer
of “why?” see:http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html
Scary stuff indeed, and I’m in the same building. >
There are also plenty of answers in line of “why not” and no shortage of
interesting books on the subject.
Don’t get too carried away with the dark side of force >
I’ll try not to
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
Wojtek Lerch wrote:
“Masquerading”? How could you possibly mistake a thread titled
“Don’t buy from Mindready” as a relevant technical issue? >
I didn’t say I was fooled into believing it was technical from the
title - that’s silly.
But this is about whether it tried to fool you, not about whether it
succeeded.
The intent of the thread (or it’s title) wasn’t to fool anyone. It was
to hijack the newsgroup for an off topic discussion for either personal
or commercial gain. If you’re concerned about my use of English, I
suggest moving the discussion elsewhere.
If you saw me in a women’s washroom, would that automatically prove that
I’m masquerading as a woman, or would that depend on my clothes and hair
style and makeup (if any)? >
Actually, to be more on point; if you where in any washroom here (male
or female) standing in front of the toilet, complaining about some
manufacturer of fuzzy toilet covers, I’d say you where masquerading as
someone with a ‘job’ to do.
\
Cheers,
Adam
QNX Software Systems
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster
“John Nagle” <nagle@downside.com> wrote in message
news:dg9m6s$hdg$1@inn.qnx.com…
[Moved to qnx.cafe - JN]
Igor Kovalenko wrote:
In general sense, yes. But QNX is so well known for
unwillingness/inability to react to more subtle signs that their
market/customers send them, it often takes a sledgehammer to make a hint.There’s a book anyone above the call center level in customer
service or marketing needs to read: “A Complaint is a Gift”.http://www.amazon.com/exec/obidos/tg/detail/-/1881052818
The author makes a crucial point, which needs to be
clearly understood by customer service people. It’s this:For every customer who complains, there are about eight
to ten other customers who don’t complain, but NEVER
BUY FROM YOU AGAIN.Yes, each complaint represents ten lost customers.
If you’re getting complaints, you’re losing
customers at a high rate. It’s not enough to make the
complainer happy. The underlying problem must be fixed.
Otherwise, the customer drain will not stop. A complaint
must be treated as a warning of a serious problem.
And first think you realized when you get a real job is that things never
quite work like in the book.
Perhaps this is part of why, at the last Embedded Systems
Conference in San Francisco, the real-time Linux companies,
MonteVista and Lynuxworks, had huge booths with heavy traffic,
while QNX had a tiny booth in the back with few visitors.John Nagle
Team Overbot
[Moved to qnx.cafe - JN]
Igor Kovalenko wrote:
In general sense, yes. But QNX is so well known for unwillingness/inability
to react to more subtle signs that their market/customers send them, it
often takes a sledgehammer to make a hint.
There’s a book anyone above the call center level in customer
service or marketing needs to read: “A Complaint is a Gift”.
http://www.amazon.com/exec/obidos/tg/detail/-/1881052818
The author makes a crucial point, which needs to be
clearly understood by customer service people. It’s this:
For every customer who complains, there are about eight
to ten other customers who don’t complain, but NEVER
BUY FROM YOU AGAIN.
Yes, each complaint represents ten lost customers.
If you’re getting complaints, you’re losing
customers at a high rate. It’s not enough to make the
complainer happy. The underlying problem must be fixed.
Otherwise, the customer drain will not stop. A complaint
must be treated as a warning of a serious problem.
Perhaps this is part of why, at the last Embedded Systems
Conference in San Francisco, the real-time Linux companies,
MonteVista and Lynuxworks, had huge booths with heavy traffic,
while QNX had a tiny booth in the back with few visitors.
John Nagle
Team Overbot
Mario Charest wrote:
“John Nagle” <> nagle@downside.com> > wrote in message
If you’re getting complaints, you’re losing
customers at a high rate. It’s not enough to make the
complainer happy. The underlying problem must be fixed.
Otherwise, the customer drain will not stop. A complaint
must be treated as a warning of a serious problem.
And first think you realized when you get a real job is that things never
quite work like in the book.
So, the lose rate is curbed by the necessity of the tools and the cost of using alternatives.
Evan
John Nagle wrote:
…
Perhaps this is part of why, at the last Embedded Systems
Conference in San Francisco, the real-time Linux companies,
MonteVista and Lynuxworks, had huge booths with heavy traffic,
while QNX had a tiny booth in the back with few visitors.
John…
I did get a T-shirt that says “QNX” or something…
Regards…
Miguel.
John Nagle
Team Overbot
As we come up on the DARPA Grand Challenge, we’re still
struggling with Mindready. We own three embedded computers;
the vehicle needs two to operate fully, although it can limp
along with one. The machines are from Tri-M, and are NOVA
Pentium 4 computers, supposedly “ruggedized” and priced
accordingly.
So far, every one of these machines has broken at least once.
We just got one back from repair (which requires shipping them to
Port Coquitlam, BC), and had to send another one out the same day.
They don’t fail while being driven around; they just fail, for
no visible reason, usually at powerup. Failure usually
means the fans turn, but there’s no VGA output and booting does
not take place. And they’ve come back from repair with
FireWire and serial ports broken.
We need a valid Mindready LLA license on only one machine.
The problem is getting a valid license and a working machine
together at the same time. We can’t tell if the FireWire port
is working until we license the machine, and then it’s too late
to transfer the license. We actually own four Mindready licenses;
two for development and two for the vehicle. I’m trying to
purchase another license, but can’t get Mindready sales on the
phone. And they close in 90 minutes. Another day lost.
The total cost of ownership on this stuff is very high. Every
hardware failure means days of downtime, even if you have spares.
John Nagle
Team Overbot
I presume this: http://www.tri-m.com/products/icp/nova8890.html
It sounds like you are using a supplied chassis w/power supply. It might not fit mechanically but try plugging in a standard PC power supply the next time one of the Novas stops working.
Evan
I presume this: http://www.tri-m.com/products/icp/nova8890.html
It sounds like you are using a supplied chassis w/power supply. It might not fit mechanically but try plugging in a standard PC power supply the next time one of the Novas stops working.
Evan
I presume this: http://www.tri-m.com/products/icp/nova8890.html
It sounds like you are using a supplied chassis w/power supply. It might not fit mechanically but try plugging in a standard PC power supply the next time one of the Novas stops working.
Evan
Evan Hillas wrote:
I presume this: > http://www.tri-m.com/products/icp/nova8890.html
It sounds like you are using a supplied chassis w/power supply. It
might not fit mechanically but try plugging in a standard PC power
supply the next time one of the Novas stops working.
Evan
It’s not the power supply. Tri-M is trying to figure out
what’s failing.
The problem seems to be airflow related; the packaging
and fan positioning really don’t match the motherboard
well.
John Nagle