Comments for Helix Player Project
Looks like it needs some work
Tried downloading it multiple times...
[root@thecheat xchat]# ./realplay-0.4.0.186-linux-2.2-libc6-gcc32-i586.bin
Extracting files for RealPlayer installation.......
xxextract.tmp: Data integrity error when decompressing.
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Broken pipe
Re: Helix Player w/RealVideo is now RealPlayer (again)
> See the Helix Player vs. RealPlayer FAQ
> for more details on this.
no, really, see the Helix Player vs. RealPlayer FAQ (player.helixcommunity....)
/me checks link this time
Helix Player w/RealVideo is now RealPlayer (again)
We previously included RealAudio, RealVideo, and other RealNetworks' proprietary components as part of Helix Player. This has now changed:
The Helix Player 1.0 is the completely dual licensed, both open source (RPSL) and commercial community source (RCSL), media player and thus contain no non-open source components. It plays open source formats, like Ogg Vorbis and Theora (www.xiph.org) and SMIL 2.0 (www.w3.org/AudioVideo).
The RealPlayer 10 (freshmeat.net/projects...) for Linux builds on top of the Helix Player and will include RealAudio, RealVideo, MP3, Macromedia Flash, MPEG-4(fee-based) and other non-open source components.
See the Helix Player vs. RealPlayer FAQ for more details on this.
I wonder what it will be named?
... I wonder what they will name the RealPlayer that works on Linux??? ;-)
Re: Looks like it needs some work
> Tried downloading it multiple times...
>
> [root@thecheat xchat]#
> ./realplay-0.4.0.186-linux-2.2-libc6-gcc32-i586.bin
>
> Extracting files for RealPlayer
> installation.......
> xxextract.tmp: Data integrity error when
> decompressing.
> Input file = (stdin), output
> file = (stdout)
>
> It is possible that the compressed
> file(s) have become corrupted.
> You can use the -tvv option to test
> integrity of such files.
>
> You can use the `bzip2recover' program
> to attempt to recover
> data from undamaged sections of
> corrupted files.
>
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting
> now
> Broken pipe
I've downloaded the .bin installer about 5 times, each time the md5sum comes out to e31382279a8b4d21534be9c3d687424f , which is different than the README. This happened before, perhaps it was uploaded incorrectly.