Hi all, Is it possible, booting with a DOS Network Boot Disk, to VIEW AND COPY files WITH LFN from mapped LAN drives, i.e. files from a NT 4 or Windows 200x Server, to a local FAT drive? ex: * Boot from DOS Network Boot Diskette * NET USE N: \\server\share (NT 4 or Win 200x servers ) * copy N:\Dir\FileWithLFN.txt C:\*.* (C: is local hard drive with FAT16 or FAT32 partition) * Have now a file named C:\FileWithLFN.txt I tried Wengier's Standard MS-DOS 7.10 Boot Disk (great job, really) and added LANMAN for DOS network software: LFN are seen only on local FAT drives, not on mapped LAN drives (only short mangled names). Can anyone tell me if it actually works with a Boot Disk having MS-DOS 7.10 + MSClient 3.0 for DOS? Is there any solution? I suppose my question is for Wengier but of course help from anyone else will be welcome!

Hi progman! LFNs on local FAT (FAT12/16/32) drives are supported directly of course. In order to view and copy LFN (Long File Names) on LAN drives, DOS must be able to physically access to the sectors of the LAN drive. However, neither direct drive access nor LFN call is supported on DOS network drives mounted by M$ Client 3.0, since M$ Client 3.0 is too old (it was released *before* LFN APIs were introduced). Therefore, it's not possible to access LFN on MSCLIENT 3.0 mapped LAN drives directly. Nevertheless, there are a few alternatives to copy LFNs on the LAN drives that you can try, such as: 1. Zip the LFN files needed to be copied using a LFN-compatible packer (e.g. PKZIP 2.50), and tranfer the zipped file to another PC on the network, then unzip the files using a LFN-compatible unpacker (e.g. PKUNZIP 2.50) on that PC. 2. Use some LFN-compatible network drive mappers or network file tranfer programs instead of MSCLIENT 3.0, such as IPXCOPY 2.7 (tranfer files via the standard IPX protocol, with LFN support [-lfn]). 3. Contact M$ and see if they are willing to release an updated version of MSCLIENT for DOS with full LFN support. BTW: A page about LFN for DOS is currently being built up. I'm going to list as many LFN-compatible programs (modern DOS programs) as possible on the page. Good luck! --------------- Long Live DOS!

Hi Wengier, Thanks for your answer, you saved me a lot of time. Unfortunately solutions 1. and 2. cannot be used in the context i'm working with. So i will try solution 3. and ask the question to M$ Bill next time he calls me. More seriously my need is to find a 10.3 file name among many others 10.3 files on the mapped LAN device. The 10 chars long file name is an identifier typed by the user of the Boot Disk, then i add the .3 file extension and must copy *this* 10.3 file from LAN to the C: FAT local hard disk drive (On C: it could be a short name, no problem with that, lfn is only mandatory on LAN drive). Without any solution to directly copy lfn from LAN, i will program a small exe scanning all the files on my LAN mapped drive and find the good one with its contents: the 10 chars identifier is also *inside* the file. When its short name is found, i can copy it to C:. My only fear is about the response time... Before trying that, there is may be another way: your solution 2. is not possible for me because my LAN context is full TCP/IP on M$ Win NT or Win 200x srvers, so no IPX protocol: Do you know any other "LFN-compatible network drive mappers" running in this LAN context? Thanks a lot.

Hi progman, As far as I know, the answer for your last question is NO unfortunately. Most programs vendors seem to have an incorrect impression that DOS doesn't support LFN, so they never released "LFN-compatible network drive mappers for DOS". --------------- Long Live DOS!

Hi Wengier, Ok, that's clear for me now, no use to test a lot of "exotics" DOS networks layers, i will write that small scanning program. Tanks again and Long Live DOS!