Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!draken!d88-eli
From: d88-eli@nada.kth.se (Erik Liljencrantz)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Directory Problems
Message-ID: <2641@draken.nada.kth.se>
Date: 1 Jan 90 15:22:41 GMT
References: <111700189@uxa.cso.uiuc.edu>
Reply-To: d88-eli@nada.kth.se (Erik Liljencrantz)
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 17

In article <111700189@uxa.cso.uiuc.edu> sfn20715@uxa.cso.uiuc.edu writes:
>[...]      Because of this,
>programs like XTree, when looking for all of the files on disk will find
>\tp5\source and then \tp5\source\tp5\source\tp5\source\tp5\source (you get
>the idea), and then crash, proclaiming "too many files."

I helped a friend at work with exactly this problem just a couple of days ago.
CHKDSK will trap that recursiveness of the directorytree, and you are able
to convert it to a file (use chkdsk /f). This file is probably empty and
you can delete it. Chkdsk will also find lost clusters on the disk,
which is also converted to files. This might be the case if your original
directory (/tp5/source) contained any files.

Check the manual for further information about chkdsk (I'm not saying RTFM!
The information often is there, but it's often tricky to find with no clues...)
-- 
Erik Liljencrantz     | "No silly quotes!!"
d88-eli@nada.kth.se   |  Embraquel D. Tuta