Wierdness when FTPin to Windows

Peter T. Breuer standard endings,

I think I've found an explantion for what's happening - that's if I understand RFC 354 correctly.

buttuming I've understood that RFC correctly, when you put FTP into ASCII mode the sending machine will convert the file from it's own format to ARPANET ASCII, and the receiving machine will convert from APARNET ASCII to whatever format it likes.

So when we do the send the linux box converts to ARPANET ASCII (hence the inflated byte count) and the receiving box, thinking that it is a unix box, promptly swops the ARPANET ASCII end-of-line sequence for the unix LF. So the file ends up the same size and in the same format.

Which is OK except the people who want to run their machine in this mode also want their files to have the native windows CR-LF at the end of each line. Which suggests that they haven't thought things through very well.

Anyhoo... we're going to have "pre convert" the file and then send it to the remote machine. The option is to tell them to turn off the unix emulation and wait to see what else breaks and where.

My thanks to all of you who took the time to respond.