|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Please forgive me if this has been discussed here, but I'm rather
at my wits' end to figure out what is going on, and didn't see this
mentioned here, so I figure it's something wrong on my end.
I'm trying to download and install the Linux binary of POV-Ray 3.5
onto my RedHat 7.3 system. However, each time I try, gzip complains
about CRC errors in the file. (It complains also over the source
file.) As nearly as I can tell, there is no corruption, since the
byte count of my downloaded file agrees with that shown on the
server, and I've tried this with two different FTP clients as well
as via HTTP transfer with Mozilla, but I get the same results each
time.
I went so far as to think that perhaps RedHat had done something to
gzip (the installed version is 1.3.3, which according to FSF is a
beta), so I downloaded and installed gzip 1.2.4 straight from gnu.org,
with the same results.
Can anyone shed some light on why I am unable to un-gzip the archive
files?
--
Steve Martin, CPBE CBNT
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e05df92@news.povray.org> , Steve Martin <ecp### [at] bellsouthnet>
wrote:
> I'm trying to download and install the Linux binary of POV-Ray 3.5
> onto my RedHat 7.3 system. However, each time I try, gzip complains
> about CRC errors in the file. (It complains also over the source
> file.) As nearly as I can tell, there is no corruption, since the
> byte count of my downloaded file agrees with that shown on the
> server, and I've tried this with two different FTP clients as well
> as via HTTP transfer with Mozilla, but I get the same results each
> time.
This won't help you if you are accessing it via some proxy server. Make
sure you really get the file from povray.org. The files on povray.org are
known to be OK and have been downloaded successfully by thousands of users
without problems. So the problem is somewhere on your side, and the only
person who can help you is, well, you.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> This won't help you if you are accessing it via some proxy server. Make
> sure you really get the file from povray.org.
I got 'em from ftp.povray.org each time.
> The files on povray.org are
> known to be OK
I assumed they were, else there would have been great screaming
before me.
> So the problem is somewhere on your side, and the only
> person who can help you is, well, you.
Sorta thought so. <sigh...>
--
Steve Martin, CPBE CBNT
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I got 'em from ftp.povray.org each time.
Don't know why this should happen, but apparently
there's some wierd interaction between my firewall
and the Netplex server... I downloaded the source
tarball from a mirror, and it unpacked just fine.
--
Steve Martin, CPBE CBNT
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Maybe you're getting the file in ascii mode somehow?
Post a reply to this message
|
|
| |
| |
|
|
From: Steve Martin
Subject: Re: Problems with POV 3.5 Linux - Solved
Date: 23 Dec 2002 06:58:30
Message: <3e06fa66@news.povray.org>
|
|
|
| |
| |
|
|
Apache wrote:
> Maybe you're getting the file in ascii mode somehow?
Well, I thought of that immediately, but an ascii
transfer would change the byte count as CR/LF pairs
are mucked with. The byte count matches, though.
The really confusing thing, though, is that if I view
the file with "less", it lists all the directories and
files in the tar archive (as if I had done a "ls -l"
on the directory tree). This tells me that it can at
least partially un-gzip the file, but I never could
manually un-gzip it.
Oh, well, it's all academic now, anyway, as I was able
to get the archive from the mirror unpacked successfully.
When I feel like messing with it, I'll do a hex dump of
both and find out what got corrupted. ("cmp" reports a
diff in the files somewhere along line 162, char # 38xxx,
so there's at least one diff in the two that's causing a
problem.)
--
Steve Martin, CPBE CBNT
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|