Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi everybody especially alexsanrs, as you know (hope) am a 24 hours, 100% time, from here to the moon, lover and user of WFWG & Calmira.
Callfn has this problems:
Crash when you try to send a file to the bin.
When you rename a file, the name appears in high case, I dont like this.
And the long (I mean LONG) flenames are cutted in both sides and it not permit the entire reading of the name. I do like the names appears in two lines.
I know it is harder to make CalLFN but meanwhile it be still with this bugs I wont se it.
Anyway, maybe am doing the things wrong, please someone tell me step by step how to install doslfn, where can I download and make it works, cause long filenames only appears in CalLFN an not in the prompt (dir). Thanks for your time.
P.D. When CalLFN be ok I'll tranlate to spanish and danish.

Except for the corrupted file "callfnin.zip" (Calmira LFN wiith installer) there also seems to be some problem with thw "callfn.zip" file (Calmira LFN without installer). When contents of the file are unzipped in proper directory, and IF Calmira LFN is made the active shell (in replacement of Program Manager), system returns an error message: "unable to find LFNFUNCS.DLL". Then, system collapses - return to the DOS prompt! Of course, LFNFUNCS.DLL exists in reality - I cannot understand why the system ignores it...

"unable to find LFNFUNCS.DLL"
You need to copy this file to the Windows System directory (C:\windows\system)When you rename a file, the name appears in high case, I dont like this
This only happens if you are renaming a file that is really in Upper Case (most likely it does not have a long file name), I may change this later but due a bug in doslfn (ex, if you rename "WINDOWS" to "Windows", the resulting short name will be "WINDOW~2", instead of keeping the "WINDOWS" short name) I will probably not change this to avoid messing the short names.And the long (I mean LONG) flenames are cutted in both sides and it not permit the entire reading of the name
This is due the original design of the file list. In the original Calmira, if you mark to show 4DOS descriptions as captions, and the file has a very long description, the same thing will happen.cause long filenames only appears in CalLFN an not in the prompt
Long file names will only appear in the DOS prompt if the Dos shell is LFN aware, and this is not the case of, for example, MS-DOS 6 shell. To see LFNs at prompt with these LFN unaware DOSes you will need a third part shell (as 4DOS), and I recomend getting something as a LFN aware version of Norton System Works or the ScanDisk that is bundled with DOS 7 and a disk defragment tool from another LFN aware DOS.I'll try to solve the BIN issue, but my Win3.11 installation is messed up and I am changing my motherboard (getting a decent ASUS one in place of a nasty PCChips M810LR), so it may take some time

Well alexanrs keep the good working, your project is fantastic I apologize for being so rude in this topic but I am a DOS 6.22/WFWG3.11/CalmiraLFN lover as everybody in this forum an it MUST work perfectly as old systems always do.
Regards

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |