file associations

QNX Newsgroups (Archives) qdn.public.qnxrtp.applications
1

message unavailable

2

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:

I tried to create file associations with pfm but I wonder if this
feature works correctly (I mean creating new associations because the
existing ones work).

For example, based on the existing associations, I tried to define .txt
to call ped, but ped is never launched.

Alain.

Please go to our Knowledge Base URL at:
http://support.qnx.com/support/bok/solution.qnx?10122

Make sure you have ‘/usr/photon/bin’ in your path.

  1. Start pfm.
  2. Press F11 OR select Associations from Edit.
  3. Click to add new file association.
  4. Type Pattern: ‘*.txt’, Open ‘ped’, View ‘ped’ and Edit ‘ped’.
  5. Press Done, Done.

–

Marcin Dzieciol
Technical Support
QNX Software Systems Ltd.
Email: <marcind@qnx.com>
3

Previously, Armin Steinhoff wrote in comp.os.qnx, qdn.public.porting, qdn.public.qnxrtp.applications, qdn.public.qnxrtp.devtools:

cross postings are a good tools … as long as it is used sensefully.
Is it possible to limit the number of addressed groups to two ?

And it’s definitely noise, if posted in unrelated NGs …

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

4

“Karsten P. Hoffmann” wrote:

Previously, Armin Steinhoff wrote in comp.os.qnx, qdn.public.porting, qdn.public.qnxrtp.applications, qdn.public.qnxrtp.devtools:
cross postings are a good tools … as long as it is used sensefully.
Is it possible to limit the number of addressed groups to two ?

And it’s definitely noise, if posted in unrelated NGs …

Noise can also be produced by a single posting to
a single (or two) unrelated news group(s) … this
NG is for qnxrtp apps and not for issues like
‘application of cross postings’ :slight_smile:

Armin

5

Armin…

Thanks… I’ll keep this in mind for (near) future research
explorations. I browsed through your web page, and I wonder, which
product in specific are you referring to?

Bests…

Miguel



Armin Steinhoff wrote:

Miguel Simon wrote:

Hi…

Does any one know if there is a such a thing as a two (2) processor
PC104??

We have a solution based on a dual ported memory
board (PC104 board with two
seperate bus interfaces, 32Kb memory, mailbox
interrupts) … two CPU (or more) can communicate
throughout the DPM board ( a Net.dpm driver must
still be ported … but it is not a big issue)

Armin

http://www.steinhoff.de

6

Previously, Armin Steinhoff wrote in qdn.public.qnxrtp.applications:

PLONK

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

7

What do you say we all send 1000 email each to support@lookanswer.com

“Support” <support@lookanswer.com> wrote in message
news:94q64k$1ak$1@inn.qnx.com…

Hello,

Began the operation mail tools of the system LookAnswer. In what it
differs
from other mail systems? Read below.
Come and evaluate! - > http://mailto.com.ua

Setupping Outlook Express:
http://mailto.com.ua/help/en/out/> ,
Setupping The Bat!:
http://mailto.com.ua/help/en/bat/
Setupping Netscape Communicator 6 and Mozilla 0.7:
http://mailto.com.ua/help/en/net/

What is it?

  1. The mail server of the LookAnswer service, is free tools and grants
    services to everyone, who requires them. A distinctive feature of granted
    tools, is the support of domains, hosted on ‘Lafour’ ( > http://la4.net > ),
    i.e. You completely freely can register mail boxes inside the domain, for
    example: you have registered the domain lastname.com, but for entirety of
    all positive sensations, there is no mail box, which would sound so:
    firstname@lastname.com> , now it is accessible and is free. To receive one
    or
    several mail boxes in the domain, even if you are in the other city or
    state, in DNS it is necessary to a zone of your domain to register MX of
    our
    mail system:

IN MX 10 mx1.mailto.com.ua.

After execution of the above-stated procedure, please, send the
application
for a mail box > support@lookanswer.com > and our mail system will be ready
for
registration of mail boxes in your domain. The access to registration of
mail boxes is realized by input login and password.

Registration
2. For registration in the form it is necessary to indicate yours login,
to
select one of ten domains: > http://la4.net> , > http://la.uz> , > http://la.kz> ,
http://mailto.com.ua> , and romantics domains
http://la.ro> , > http://adam.la.ro> , > http://eva.la.ro> , > http://cat.la.ro> ,
http://lion.la.ro> , > http://life.la.ro> , to indicate your name and twice to
enter the password. On pressing the button ‘Register’ your mail box with a
quota in 5 megabytes is created. At exceeding a quota, you can not receive
the new letters, while some of the old letters are not be deleted by you.

Aliases
3. We represent to you possibility to use the mail address in the domain,
if
it hosted on la4.net. For obtaining such box it is necessary at first to
register in one of ten mail domains, enter the system and to go under the
links Options / Aliases. Here you can create alias in the domain, i.e. if
you have registered to yourselves the mail address > name@mailto.com.ua > and
you have site site.la4.net, you can make so that the mail sent on
name@site.la4.net > came on name@selected_domain. You can create arbitrary
quantity of aliases, delete and edit them. If alias in any domain has been
created first time, the mail on this address will be accepted next day.

Mail servers
4. Except for web of the interface we offer possibility to receive mail on
POP3 and IMAP4 to protocols. For this purpose in your mail program it is
necessary to indicate as the server of incoming mail mailto.com.ua. The
login name is formed as follows: if your address > name@la4.net> , instead of
a
login name in the mail program it is necessary to specify la4_net-name,
the
principle of construction of a name in other domains is similar. Also we
offer possibility to send the letters by your favourite mail program. The
unique condition, presented to the mail agent, is support SMTP with
authentification. Our mail server (mailto.com.ua) maintains LOGIN, PLAIN
and
CRAM-MD5 methods of authentification. We had verified Netscape Messagener
(LOGIN), MS Outlook (PLAIN) and TheBat! (PLAIN and CRAM-MD5) mail agents.

Thank.
If you have additional questions, sent it to support service:
support@lookanswer.com

8

What do you say we all send 1000 email each to > support@lookanswer.com

I have a nice little windows based email bomb program……We
used it
to test our qmail setup on our new linux server and not to send out this
junk…:slight_smile:

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
9

Can I have it.

“Lee R. Copp” <Lee.R.Copp@MichiganScientific.com> wrote in message
news:94s3ct$6av$2@inn.qnx.com…

What do you say we all send 1000 email each to > support@lookanswer.com

I have a nice little windows based email bomb program……We
used it
to test our qmail setup on our new linux server and not to send out this
junk…> :slight_smile:

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ > http://www.michiganscientific.com
~ mailto:> <Lee.R.Copp@MichiganScientific.com>
10

Can I have it.

Let me know where to send it…It is around 200k zipped so I’m not
going to post it here…

~ Lee R. Copp
~ Project Engineer (EE/ME)
~ Michigan Scientific Corp.
~ 321 East Huron St.
~ Milford, MI 48381
~ 248-685-3939 x109 (V), 248-684-5406 (Fx)
~ http://www.michiganscientific.com
~ mailto:<Lee.R.Copp@MichiganScientific.com>
11

John,

I am cross-posting this into the applications newsgroup because I
think that it is more likely to be seen by the correct developers
there. Please continue the discussion there.

I can understand your frustration. The phplay (or “Media Player”)
application is in the process of being depricated because of it
being relatively difficult to maintain and not architected for
future expansion. You find yourself in the unenviable possition
of being between an old difficult to use player and a new one
which hasn’t got nearly as many miles on it, but shows a lot more
potential.

I don’t remember if it was an MPEG-1 file, but I can guarantee you
that I have seen at least a few video-only mpeg files running under
phplay which worked fine. I do remember that the developer had to
make some changes in order to make them work. Since it was a
different developer who designed and implemented the mmedia libraries
which are used by mmplay, it is entirely possible that a similar
change needs to be made. I don’t have as much experience with the
new system, so I can’t really comment. I would recommend that you
make a small-ish MPEG-1 that shows the problem and make it available
for people in this group to take a look at (ex. ftp). If you have
already done so, please post where it is in your reply as I didn’t
see it in any previous posting and that saves having to search.

As mentioned by Frank Liu in a separate thread, the md5sum utility
is include on the 3rd Party CD. I think that it is in the
“GNU File Utilities” (or something like that). It is not the latest
version, but it does do the job.I started porting the “GNU core
utilities” a while back, but I discovered (as you did) that it wasn’t
100% straight-forward, so I have put it on a back-burner and haven’t
looked at it since. If you do manage to get it ported, please let us
know and we will see about getting it included in a future 3rd Party
CD release.

–
James MacMillan

John Nagle wrote:

We’ve been trying to log video from our robot vehicle to disk
under QNX. We’ve lost a week on this so far due to
QNX defects.

  1. Media Player is badly broken. It won’t even play
    the official MPEG 1 test files properly. It
    skips to the last frame. Apparently nobody ever
    tested it on a video-only file, and it’s using
    the audio track to time the video file.

  2. A QNX employee suggested using “mmplay”. That’s
    worse. It won’t play any video files. Maybe
    it insists we have to have audio hardware to play
    a video file, or it wants video hardware with
    overlay capabiilty. But the messages that
    come out don’t explicitly say that. Often it
    just core dumps. (Of course, QNX doesn’t fully support
    any video hardware we have. Most of our machines
    have Via S3 Savage video chipsets, and QNX doesn’t
    support any versions of that in current production.
    Only obsolete hardware of that family is supported.
    Like everybody else, we’re running in VESA mode.
    Despite having purchased hardware for QNX which appeared, from
    the supported hardware list, to be supported.)

  3. We’ve tried to port the free “ffmpeg” libraries to QNX.
    These libraries are supposedly used by shipping QNX
    applications and have supposedly been ported to QNX.
    But the changes for QNX hae not been put back into the
    publicly available sources. “libavcodec” and “libavformat”
    build, but the output
    has artifacts. I’ve tried to build the test suite
    for “ffmpeg”, but that wants “md5sum”, which is
    missing from QNX.

  4. Trying to build the “GNU core utilities” to make “md5sum”
    fails under QNX because “configure” won’t run. It prints
    “configure: error: could not determine
    how to read list of mounted filesystems”. So we can’t
    build “md5sum”. So we can’t build the tests for
    the codecs. So we can’t diagnose the codec problem.
    None of which we should have to be doing in the
    first place.

A serious problem with QSSL is that it relies on free software tools,
but doesn’t do the work to make sure they work right.
QNX’s so-called “multimedia support” is mostly a front end on free
software.
Necessary QNX-related changes required often don’t make it back
into the master sources. So users can’t rely on the open
source community for support. Users can’t simply build
free software for QNX using publicly available sources.
Support, in the form of timely fixes from QSSL, is of course
nonexistent. We have never received any delivered fix
for any reported defect in QNX whatsoever. Even for
major defects confirmed by multiple other users.

Working around defects like this in QNX has cost us two
to three months over the last year. Time we didn’t have.
John Nagle
Team Overbot

12

We are pleased that QSSL understands our frustration.
We of course have an absolute deadline of 8 March 2004,
and every day we spend on things like this reduces our
chances of meeting that deadline. We have thus abandoned
all attempts to play video on QNX and will play our
video files on other operating systems. We are concentrating
on making the encoding side work on QNX, using the libavcodec and
libavformat libraries. If QSSL would like to work on the
player side, that would be appreciated.

A useful library of MPEG test streams can be found at

ftp://ftp.tek.com/tv/test/streams/

Any player that cannot play everything in that set of
test data is obviously defective.

Thank you for your interest in Team Overbot.

John Nagle
Team Overbot


James MacMillan wrote:

John,

I am cross-posting this into the applications newsgroup because I
think that it is more likely to be seen by the correct developers
there. Please continue the discussion there.

I can understand your frustration. The phplay (or “Media Player”)
application is in the process of being depricated because of it
being relatively difficult to maintain and not architected for
future expansion. You find yourself in the unenviable possition
of being between an old difficult to use player and a new one
which hasn’t got nearly as many miles on it, but shows a lot more
potential.

I don’t remember if it was an MPEG-1 file, but I can guarantee you
that I have seen at least a few video-only mpeg files running under
phplay which worked fine. I do remember that the developer had to
make some changes in order to make them work. Since it was a
different developer who designed and implemented the mmedia libraries
which are used by mmplay, it is entirely possible that a similar
change needs to be made. I don’t have as much experience with the
new system, so I can’t really comment. I would recommend that you
make a small-ish MPEG-1 that shows the problem and make it available
for people in this group to take a look at (ex. ftp). If you have
already done so, please post where it is in your reply as I didn’t
see it in any previous posting and that saves having to search.

As mentioned by Frank Liu in a separate thread, the md5sum utility
is include on the 3rd Party CD. I think that it is in the
“GNU File Utilities” (or something like that). It is not the latest
version, but it does do the job.I started porting the “GNU core
utilities” a while back, but I discovered (as you did) that it wasn’t
100% straight-forward, so I have put it on a back-burner and haven’t
looked at it since. If you do manage to get it ported, please let us
know and we will see about getting it included in a future 3rd Party
CD release.

–
James MacMillan

John Nagle wrote:

We’ve been trying to log video from our robot vehicle to disk
under QNX. We’ve lost a week on this so far due to
QNX defects.

  1. Media Player is badly broken. It won’t even play
    the official MPEG 1 test files properly. It
    skips to the last frame. Apparently nobody ever
    tested it on a video-only file, and it’s using
    the audio track to time the video file.

  2. A QNX employee suggested using “mmplay”. That’s
    worse. It won’t play any video files. Maybe
    it insists we have to have audio hardware to play
    a video file, or it wants video hardware with
    overlay capabiilty. But the messages that
    come out don’t explicitly say that. Often it
    just core dumps. (Of course, QNX doesn’t fully support
    any video hardware we have. Most of our machines
    have Via S3 Savage video chipsets, and QNX doesn’t
    support any versions of that in current production.
    Only obsolete hardware of that family is supported.
    Like everybody else, we’re running in VESA mode.
    Despite having purchased hardware for QNX which appeared, from
    the supported hardware list, to be supported.)

  3. We’ve tried to port the free “ffmpeg” libraries to QNX.
    These libraries are supposedly used by shipping QNX
    applications and have supposedly been ported to QNX.
    But the changes for QNX hae not been put back into the
    publicly available sources. “libavcodec” and “libavformat”
    build, but the output
    has artifacts. I’ve tried to build the test suite
    for “ffmpeg”, but that wants “md5sum”, which is
    missing from QNX.

  4. Trying to build the “GNU core utilities” to make “md5sum”
    fails under QNX because “configure” won’t run. It prints
    “configure: error: could not determine
    how to read list of mounted filesystems”. So we can’t
    build “md5sum”. So we can’t build the tests for
    the codecs. So we can’t diagnose the codec problem.
    None of which we should have to be doing in the
    first place.

A serious problem with QSSL is that it relies on free software tools,
but doesn’t do the work to make sure they work right.
QNX’s so-called “multimedia support” is mostly a front end on free
software.
Necessary QNX-related changes required often don’t make it back
into the master sources. So users can’t rely on the open
source community for support. Users can’t simply build
free software for QNX using publicly available sources.
Support, in the form of timely fixes from QSSL, is of course
nonexistent. We have never received any delivered fix
for any reported defect in QNX whatsoever. Even for
major defects confirmed by multiple other users.

Working around defects like this in QNX has cost us two
to three months over the last year. Time we didn’t have.
John Nagle
Team Overbot

13

John Nagle wrote:

We are pleased that QSSL understands our frustration.
We of course have an absolute deadline of 8 March 2004,
and every day we spend on things like this reduces our
chances of meeting that deadline. We have thus abandoned
all attempts to play video on QNX and will play our
video files on other operating systems. We are concentrating
on making the encoding side work on QNX, using the libavcodec and
libavformat libraries. If QSSL would like to work on the
player side, that would be appreciated.

A useful library of MPEG test streams can be found at

ftp://ftp.tek.com/tv/test/streams/

Any player that cannot play everything in that set of
test data is obviously defective.

Thank you for your interest in Team Overbot.

John Nagle
Team Overbot


James MacMillan wrote:

Hi,

Perhaps you can try vlc (www.videolan.org). The release 0.4.5 compiles
and works under QNX.
I’ve tried it with several video files found under
ftp://ftp.tek.com/tv/test/streams/ and it works fine.

Best regards

14

Thanks. We’ll look at that when we have more free time.

It’s discouraging to see QNX listed in 14th place and under
“there is no binary”. Obviously, almost nobody uses this
thing on QNX. I don’t really have time to debug this.

John Nagle

Pierre AUBERT wrote:

John Nagle wrote:

We are pleased that QSSL understands our frustration.
We of course have an absolute deadline of 8 March 2004,
and every day we spend on things like this reduces our
chances of meeting that deadline. We have thus abandoned
all attempts to play video on QNX and will play our
video files on other operating systems. We are concentrating
on making the encoding side work on QNX, using the libavcodec and
libavformat libraries. If QSSL would like to work on the
player side, that would be appreciated.

A useful library of MPEG test streams can be found at

ftp://ftp.tek.com/tv/test/streams/

Any player that cannot play everything in that set of
test data is obviously defective.

Thank you for your interest in Team Overbot.

John Nagle Team Overbot


James MacMillan wrote:



Hi,

Perhaps you can try vlc (> www.videolan.org> ). The release 0.4.5 compiles
and works under QNX.
I’ve tried it with several video files found under
ftp://ftp.tek.com/tv/test/streams/ > and it works fine.

Best regards

15

“James MacMillan” <jamesm@qnx.com> wrote in message
news:btfblt$j9g$2@nntp.qnx.com…

John,

I am cross-posting this into the applications newsgroup because I
think that it is more likely to be seen by the correct developers
there. Please continue the discussion there.

I can understand your frustration. The phplay (or “Media Player”)
application is in the process of being depricated because of it
being relatively difficult to maintain and not architected for
future expansion. You find yourself in the unenviable possition
of being between an old difficult to use player and a new one
which hasn’t got nearly as many miles on it, but shows a lot more
potential.

I don’t remember if it was an MPEG-1 file, but I can guarantee you
that I have seen at least a few video-only mpeg files running under
phplay which worked fine. I do remember that the developer had to
make some changes in order to make them work. Since it was a
different developer who designed and implemented the mmedia libraries
which are used by mmplay, it is entirely possible that a similar
change needs to be made. I don’t have as much experience with the
new system, so I can’t really comment. I would recommend that you
make a small-ish MPEG-1 that shows the problem and make it available
for people in this group to take a look at (ex. ftp). If you have
already done so, please post where it is in your reply as I didn’t
see it in any previous posting and that saves having to search.

As mentioned by Frank Liu in a separate thread, the md5sum utility
is include on the 3rd Party CD. I think that it is in the
“GNU File Utilities” (or something like that). It is not the latest
version, but it does do the job.I started porting the “GNU core
utilities” a while back, but I discovered (as you did) that it wasn’t
100% straight-forward, so I have put it on a back-burner and haven’t
looked at it since. If you do manage to get it ported, please let us
know and we will see about getting it included in a future 3rd Party
CD release.

–
James MacMillan

John Nagle wrote:
We’ve been trying to log video from our robot vehicle to disk
under QNX. We’ve lost a week on this so far due to
QNX defects.

  1. Media Player is badly broken. It won’t even play
    the official MPEG 1 test files properly. It
    skips to the last frame. Apparently nobody ever
    tested it on a video-only file, and it’s using
    the audio track to time the video file.

The Media Player (phplay) uses the “old multimedia package” (Pre 6.2.1).
An mpegvideo-only file would be handled by the mpegvideo plugin.
This plugin is based on the “xing software decoder” and has been tested.
This plugin doesn’t try to synchronize to any audio track.

  1. A QNX employee suggested using “mmplay”. That’s
    worse. It won’t play any video files. Maybe
    it insists we have to have audio hardware to play
    a video file, or it wants video hardware with
    overlay capabiilty. But the messages that
    come out don’t explicitly say that. Often it
    just core dumps. (Of course, QNX doesn’t fully support
    any video hardware we have. Most of our machines
    have Via S3 Savage video chipsets, and QNX doesn’t
    support any versions of that in current production.
    Only obsolete hardware of that family is supported.
    Like everybody else, we’re running in VESA mode.
    Despite having purchased hardware for QNX which appeared, from
    the supported hardware list, to be supported.)

mmplay uses the “new multimedia architecture” introduced with rtp 6.2.1.
A video card with overlay capability is needed to display video under 6.2.1.
This limitation has been removed with rtp 6.3.0.

under rtp 6.3.0 the window_writer.so filter support:

  • blitting to video overlay (fastest )
  • blitting from offscreen memory
  • blitting from share memory
  • blitting from memory
  • rgb8, rgb16, rgb24, rgb32 video output
  1. We’ve tried to port the free “ffmpeg” libraries to QNX.
    These libraries are supposedly used by shipping QNX
    applications and have supposedly been ported to QNX.
    But the changes for QNX hae not been put back into the
    publicly available sources. “libavcodec” and “libavformat”
    build, but the output
    has artifacts. I’ve tried to build the test suite
    for “ffmpeg”, but that wants “md5sum”, which is
    missing from QNX.

the “ffmpeg” library that has been ported to rtp 6.2.1 is
“libavcodec.so”.
this library is based on the ffmpeg.0.4.6 source tree and compiles
without any problem under qnx.
Just untar the archive, run the configure script and type make.
No changes in any sources files of libavcodec.so has been made.

  1. Trying to build the “GNU core utilities” to make “md5sum”
    fails under QNX because “configure” won’t run. It prints
    “configure: error: could not determine
    how to read list of mounted filesystems”. So we can’t
    build “md5sum”. So we can’t build the tests for
    the codecs. So we can’t diagnose the codec problem.
    None of which we should have to be doing in the
    first place.

Since you don’t have a video card with overlay capability,
you have never used mmplay to play video streams and thus
have never loaded the ff_mpegv_decoder.so filter.
this filter is a dll that links against the ffmpeg
“libavcodec.so” library mentionned above.
ff_mpegv_decoder.so is just one out of many filters that the new multimedia
architecture implements.

Regards,
Angelo.

A serious problem with QSSL is that it relies on free software tools,
but doesn’t do the work to make sure they work right.
QNX’s so-called “multimedia support” is mostly a front end on free
software.
Necessary QNX-related changes required often don’t make it back
into the master sources. So users can’t rely on the open
source community for support. Users can’t simply build
free software for QNX using publicly available sources.
Support, in the form of timely fixes from QSSL, is of course
nonexistent. We have never received any delivered fix
for any reported defect in QNX whatsoever. Even for
major defects confirmed by multiple other users.

Working around defects like this in QNX has cost us two
to three months over the last year. Time we didn’t have.
John Nagle
Team Overbot