It may be strange but after only one day I released another beta. Well, not many things have changed (only an hour or two of coding), but an interesting fix has been implemented... It is about charset in filenames. As the way Win3.11 apps interact with LFNs is the same as DOS ones do, the characters of the strings (text) returned by DOSLFN are in the DOS OEM code page. It is just ok for regular characters (below code 127, as a,b,c,d and so on) but extend characters (á,à,é and others) looked strange (as the extended characters code in dos code page and windows ansi character set do not match). It was pretty simple (I got surprised) to fix this: Windows provides two funcs, AnsiToOem and OemToAnsi... just changed my lfn unit... Another bug related to version information in files with LFNs have been fixed too... If someone gets able of fixing the MOST ANNOYING BUG in Calmira LFN, that it hangs when Creating/Renaming folders for the second time with LFNs enabled, PLEASE send to me... I'd be grateful... If you are using or is going to use my modified version, please send your suggestions (alexanrsousa@netscape.net). www.geocities.com/alexanrsousa

Thanks for making public CALLFN beta 4! It is a great program, I've allready downloaded it and plan to start testing. I'll install it over beta 2, which is alredy running on my computer. However, I have to report one bug of beta 2: it runs smoothly over my Windows 3.1, GREEK version, on top of DOS 7.10, but WITHOUT DOSLFN enabled! IF I enable DOSLFN, Win 3.1 GUI + CALLFN beta 2 REFUSE even to start (program freezes in the Windows 3.1 splash screen)! Perhaps I'm doing something wrong, when loading DOSLFN, OR it has to do with the fact that I'm using the Greek version of Win 3.1 (O.K., it's natural, I am in Athens!). I've seen that in CALLFN beta 4 you corrected something having to do with the charset in filenames, DOS code page and Windows ansi set... Could that be the problem? Fixed in beta 4? I'll try beta 4 and post again, reporting how the program reacts along with DOSLFN enabled and the Greek Win 3.1. Meanwhile, one question, just to be sure I'm not doing something wrong: to enable DOSLFN I change to the dir DOSLFN resides (c:\cd win95\command\dosslfn) and type "doslfn". I get a response "program enabled" or something like this. Is this the right way to make things round?

Well I'll try it, hope you can fix the rename bug. I let you know about other bugs since I am a 24 hour user of WFWG 3.11 & Calmira.

I'm not doing something wrong: to enable DOSLFN I change to the dir DOSLFN resides (c:\cd win95\command\dosslfn) and type "doslfn". I get a response "program enabled" or something like this. Is this the right way to make things round? Yes, it is the right way Perhaps I'm doing something wrong, when loading DOSLFN, OR it has to do with the fact that I'm using the Greek version of Win 3.1 Calmira LFN (and any other Calmira I've seen) does not load anything while the Windows logo is shown... This is probably due an error while loading LFNXLAT.VXD (a driver DOSLFN automatically loads when it detects windows starting up). Maybe updating to the lastest version of DOSLFN (0.40, if I remember well) will help. Well I'll try it, hope you can fix the rename bug Fixed it in my home pc :-P I separated the LFN related routines in a DLL and made the main program point to it (LFNFUNCS.DLL)... but now every time i try to copy it gives me an error message (Dynalink error) and halts Calmira LFN... this is probably due a function not exported, or something like... I doubt it is a very difficult bug to fix, but I'm going to be out of town for two days... When I get back I'll work on it. I'm gonna upload it (Calmira LFN 3.3 - not a beta :-) ) as soon as I fix this and update the help files