IIS 5 FTP MGET lowercases filenames

[JohnGray]

When I use the FTP command "get" to transfer a file called UPPERCAS.TST from an IIS 5.0 server to my PC, it arrives as UPPERCAS.TST. If I use "mget" it arrives as uppercas.tst.

There are a number of related TechNet articles, such as Q231876, Q194909, Q147621, but these all say to get this result you have to set a particular registry value "LowercaseFiles" to 1 - and it isn't even present on the IIS 5.0 server! In fact the result seems to be the exact opposite of what Microsoft says should happen! <img src=/S/brickwall.gif border=0 alt=brickwall width=25 height=15>

Has anyone met a similar problem? The case of the filename is important because it is intended that the production transfer will eventually be to a Unix box, which cares about such trivialities...

[jscher2000]

No personal experience. My guess is that IIS 5 has the old case insensitive behavior for MGET as its default, and that's why none of those articles refer to IIS 5.

The way I read LowercaseFiles Parameter Does Not Affect GET/MGET Commands (Q194909), the parameter affects only the FTP service's ability to find the file, and does not determine how the client will save it. Possibly MGET gives the client an all-lowercase name because in Windows file systems, case is not significant?

[JohnGray]

Thanks for your response! I agree that there is no mention of IIS 5 in any of these articles, which is slightly surprising, I would say.

I was hoping for some degree of consistency between the results of GET and MGET, but it seems that I am doomed to failure here. There seems to be a similar problem with the LS command, where doing LS UPPERCAS.TST returns uppercas.tst, and LS lowercas.tst returns the expected lowercas.tst.

The question now really seems to be: how can I preserve the case of the filename between source and target (it could, of course, start in MiXeD CaSe...)?

[jscher2000]

Sounds as though if you know the original case, GET is better, but more testing probably is needed to confirm that.