<<Either: the software is not looking it up correctly. If that were the case,you would not be the only person seeing this problem.>>
How do you know that I am the ONLY one seeing the problem? You know that I am the ONLY one REPORTING it. The problem right now is very difficult to characterize, because there seems to be very contradictory evidence about where it is located--it is difficult to reproduce--you really don't know where it is--your first explanation was wrong--but what you must be absolutely clear about is that I am telling you the exact precise truth--to the extent that it is possible I am telling you exactly what is going on.
So when I say I made no changes in those tables, I mean it--I in no way edited the PC mapping entries in the FILE menu--I looked at them and reported them to you--so if that is your tentative explanation, you need to put it out of your mind, because you are wasting your time and my time , and the time of anyone else who might be experiencing this problem at some point by holding on to it--unless the software itself is altering them--in which case, other people would be seeing this, wouldn't they?
I have been here before, countless times--I understand the inclination to not believe someone--anyone--when they report a bug, particulalrly one that is difficult to pin down--but this one behaved precisely as I have said and has evolved in exactly the way I related it. It may seem illogical, it may be difficult to explain, but my description is as close to the exact truth as I can get it.
<< <<The change(s) that occurred only occurred since the final release, and did not occur on the beta versions nor (as far as I know) on the various frec versions. >>
That would be easy enough to test, just by reloading v5.6 for a bit to try it out. I think you'll find that it affects any server you run on that computer.>>
It is unclear if you are right about this--the problems seemed to have morphed into a new set of problems quite independent of my change to 5.6--and the problem is now the same on all three servers that I can try--my two servers here, and yours at SI--namely that text files are not uploaded correctly when Windows is set to not display extensions, and do upload correctly when it is set to do so. You can examine a file so uploaded to YOUR SITE--NOT MINE--in my mailbox.
I have no idea why the problem is different now--since it is the weekend, I cannot try out the computers in the faculty offices to see if things have similarly changed there and if the workaround (showing the extensions) works for them. I am uncomfortable about leaving a problem that has spontaneously "disappeared" without any good explanation, particularly when that problem was so reproducible (reproducible enough for you yourself to observe it and suggest a possible fix) because experience shows that such problems have a way of resurfacing and biting you on the ass.
The fact is that it occurred, and that, for whatever reasons, it has been replaced by this new lesser evil--namely that files do not upload properly when windows is set to hide the extensions if you are using tfclient4 (this doesnt happen with tfclient3.1)
This new problem applies as well to Gif files. Again--if you don't believe me check--ON YOUR SERVER--your new uploads folder and my mail folder--you will find the identical gif file uploaded with and without the extensions hidden. The file with the hidden extension will have zero size
This problem seems tractable--tfclient needs to know that the extensions are missing and append them and send the proper name to the server so that it will recognize them.
But I caution you that when I get to the faculty computers sometime next week, for all I know, problem number one may still be there. I am uncomfortable because I dont think this has been sorted out.
