to use LFNBK
1) You must turn off lfn "tunneling" prior to running lfnbk. This
feature causes lfnbk to fail to remove all long file names. To turn
- Open up the "system" control panel icon
- Click on the "Performance" tab
- Click the "File system" button
- Click on the "Troubleshooting" tab
- Check the "Disable long name preservation for old programs" box
- Press the OK button
- Restart you system
lfnbk version 3.2 and above includes a "tunneling" check that
prevents it from running if this feature is enabled.
If for some reason you want to run lfnbk with tunneling enabled, add
the /FORCE switch to the command line.
**Caution: some older disk utilities will delete files if you use
the /FORCE switch and tunneling is enabled.
2) Prior to running your disk utility run the following in Chicago
at a DOS prompt:
lfnbk /a /b <drive> (use /a to backup hidden and system files!)
3) Run defrag from outside of Chicago. The quickest way to do this
is to hit F5 during the boot process. You should see a plain DOS
prompt instead of the Chicago shell. Then you can safely run the
4) Go back into Chicago and run the following at a DOS prompt:
lfnbk /r <drive>
That's all there is to it! Your long file names should all be
Things you should Know
LFNBK creates a file named "lfnbk.dat" in the root of the drive
processed. This file is needed to restore your long file names,
so don't delete it. It will be deleted by lfnbk during the
restore process if there are no problems.
The restore process restores the long file name for each file
in lfnbk.dat, but the old style 8.3 (short) name is assigned
by Chicago, and may occasionally be changed by this process.
You should run the restore process as soon after running your
disk utility as possible. lfnbk will skip any files it can't
restore, but remember that it saves the state of your long
file names in lfnbk.dat, and expects the name of any file
being restored to be the one found in lfnbk.dat.
If your disk utility complains that it won't run in a
multitasking environment, make sure you don't load any of
the Chicago drivers, such as ifshlp.sys when you boot
into real mode.
If your disk utility complains that it doesn't have enough
memory to read your disk structure, it's possible you have
orphaned directories from previous builds. One place we've
seen a lot of this is in whatever directory your TEMP or
TMP environment variables point to. Usually deleting this
directory (assuming it doesn't contain anything useful!)
and creating a fresh one takes care of the problem.
Nach LFNBK alle Dateien sichern?
selbst gefunden und erprobt, © W.Oestreicher