https://community.hpe.com/t5/operating-system-openvms/using-nftw32/m-p/3559787#M49315 Dom,<BR /><BR />I can't answer your NFT question, but have you<BR />considered using C-Kermit/Kermit-95?<BR /><BR /><A href="http://www.columbia.edu/kermit/" target="_blank">http://www.columbia.edu/kermit/</A><BR /><BR />Dave<BR /> Tue, 07 Jun 2005 20:22:55 GMT David B Sneddon 2005-06-07T20:22:55Z https://community.hpe.com/t5/operating-system-openvms/using-nftw32/m-p/3559786#M49314 Thanks for all the advice on my last question. It helped, but I now think there are other considerations on the network as a whole that stops PW from working up to snuff.<BR /><BR />My work around, since I don't have shares anymore, is to use the Network File Transfer program, NFTW32. This works great going from the VAX to a PC, but the other way I get funny results.<BR /><BR />After a few tests, my best guess is that NFT assumes I need a Variable Length record on the VAX, and so gives my two extra bytes every so often. I noticed that NFT comes with options, so I checked off "Fixed Records", gave a Max Record size of 530, and an allocation in blocks. Now the program hangs.<BR /><BR />Any ideas?<BR /><BR />Dom Tue, 07 Jun 2005 17:41:26 GMT https://community.hpe.com/t5/operating-system-openvms/using-nftw32/m-p/3559786#M49314 Dominic Olivastro 2005-06-07T17:41:26Z https://community.hpe.com/t5/operating-system-openvms/using-nftw32/m-p/3559787#M49315 Dom,<BR /><BR />I can't answer your NFT question, but have you<BR />considered using C-Kermit/Kermit-95?<BR /><BR /><A href="http://www.columbia.edu/kermit/" target="_blank">http://www.columbia.edu/kermit/</A><BR /><BR />Dave<BR /> Tue, 07 Jun 2005 20:22:55 GMT https://community.hpe.com/t5/operating-system-openvms/using-nftw32/m-p/3559787#M49315 David B Sneddon 2005-06-07T20:22:55Z