"neo002244" <neo002244@hotmail.com> wrote in message
news:6727e22f.0308131930.6c3858e6@posting.google.c om...
> > Someone in this newsgroup suggested that you should always reply to a
post
> > by replying at the end of it - it makes it easier for others to read the
> > history by starting from the top (oldest thread) and paging down to the
> > newest thread... Just a suggestion, hope you don't mind...
> >
> > anyway... its interesting that you say that you found the problem only
> > occurs for gifs and not jpgs - I'm wondering if you have a filesystem
> > problem - That might sound crazy but I've got the bones of about 2,500
> > images that I've saved over time - I burned them to disk and found I
could
> > only read the jpgs - not the gifs... I then ftp'd the images from my
linux
> > server to my windoze box and found again that I could not view the gifs
> > (though I had some of the originals on my windoze box and they could be
> > viewed so I could be sure the problem did not originate on my windoze
box).
> >
> > I've yet to find out the cause for this - but I suggest you try and ftp
a
> > handful of images to your box and then try and view them... see if you
get
> > the same problems and thus rule out the apache/php as the source of your
> > problem.
> >
> > and just in case... I'm running SuSE Linux 7.1, kernal 2.4.0-4Gb (about
a
> > year or more old)...
>
> Randall,
>
> It seems that there are some issues with GIFs when you transfer them
> from Windows to Linux. I FTPed the corrupted GIF file to Windows and I
> couldn't view it. I would think that there has to be someone out there
> who has had GIF issues with Linux. I hope to resolve this issue in the
> near future. In the meantime, I am amazed at the fact that I can't
> seem to find more info concerning this problem.

True... It might be worth while making a post in one of the linux ng's - in
addition, I don't know if you know but officially, the license (or the
alogritm used) to make GIF files is owned by Unisys hence the reason why the
GD graphics library, among others, have dropped support and instead moved to
PNG type files (which are supposed to offer better compression in addition
to all the other advantages of a GIF file).

I'm glad that you've at least replicated the problem via ftp which should
therefore rule out PHP from being the culprit... If you make a post in one
of the linux ng's I think you will eventually find the answer - if not, I'll
drop you a byte if I find out but at the moment its low priority on my todo
list since I'm pretty sure the problem is external to PHP...

cheers
randelld