Archived from groups: microsoft.public.windowsxp.perform_maintain (
More info?)
Hi, Steph.
> Now I get it with the SFN and LFN. Fubnny, I tought that DOS was
> completelly
> out of the system since Win 2000! I guess I was wrong!
Yes, MS-DOS is completely gone (except just enough to let WinXP create an
MS-DOS boot floppy). But Win2K and WinXP include an emulator that many
consider "a better DOS than DOS". In WinXP, just click Start | All Programs
| Accessories | Command Prompt, or Start | Run and enter Cmd.exe. This will
open what I call a "DOS" window, with "DOS" in quotes to emphasize that it
is not true MS-DOS. In this window, nearly all the old familiar MS-DOS
commands will work just about like they always did. And most of the old
MS-DOS applications will still run, the exceptions being those that
manipulated the hardware directly (like games, especially), because WinXP
deals with hardware through the HAL (Hardware Abstraction Layer), which
MS-DOS never heard of, and won't allow direct manipulation by those
programs.
As I said and Wes explained much better, each file must have a valid 8.3
filename. If the LFN qualifies as an SFN, then it is used; otherwise, an
SFN that qualifies under the old familiar 8.3 rules is created and stored in
the directory, in addition to the LFN. Long File Name is a slight misnomer
because some very short names don't qualify. For example, "A FILE" is only
6 characters, but one of them is a space, which MS-DOS would not allow, so
the SFN "afile~1" is created. See for yourself. Type: md "a file". Dir
will show "a file" (without the quotes). Dir /x will show both "a file" and
"afile~1".
> But what do we want to know from the SFN?
The reason I asked you to type dir /x was to see if any illegal characters
were hiding within the apparently valid filenames "Windows" and "0". The
results you posted show that no such tricks exist. Your 0, 4, 6, etc.,
files are just that: very large files with those very short names within
the Windows folder.
So now all you have to do is (a) delete those files that are taking up 1.4
GB each of your hard drive space, and (b) figure out what is causing such
files to be created in the first place. Have you tried the ideas that David
Candy has posted in the other sub-thread?
RC
--
R. C. White, CPA
San Marcos, TX
rc@corridor.net
Microsoft Windows MVP
"Steph." <Steph@discussions.microsoft.com> wrote in message
news:C4F87B9C-70B4-4578-98D7-6DCF792889FD@microsoft.com...
> Hi RC!
>
> Now I get it with the SFN and LFN. Fubnny, I tought that DOS was
> completelly
> out of the system since Win 2000! I guess I was wrong!
>
> Anyway, I am quoting your original question asking me what SFN I could see
> and here are the results.
>
> /*What is the SFN for WINDOWS\0, for example?
> If you still don't see the SFN for WINDOWS\*, then please tell us what you
> DO see with dir C:\ /x /a. We would expect the SFN
> to
> also be WINDOWS, of course; if it isn't then we SURE want to know that!*/
>
> /*Once you know the SFN of \WINDOWS\0, for example, it should
> be a simple
> matter to see the contents of that file or folder, using dir with the /s
> or
> other switches, if it is a folder, or the Type or Edit command if it is a
> file. */
>
> 2005-01-24 20:19 1 408 450 560 0
> 2005-01-24 20:20 0 0.log
> 2005-01-24 20:19 1 408 450 560 4
> 2005-01-24 20:19 1 408 450 560 6
> 2005-01-24 20:19 1 408 450 560 8
> 2005-01-24 20:19 1 408 450 560 9
> 2005-01-24 20:19 1 408 450 560 S
> 2005-01-24 20:19 1 408 450 560 Y
>
> But what do we want to know from the SFN?
>
> And the /s command produced the following:
> C:\>dir /s /a windows\0
> Volume in drive C is WINDOWS
> Volume Serial Number is 38BF-EE85
>
> Directory of C:\windows
>
> 2005-01-24 20:19 1 408 450 560 0
> 1 File(s) 1 408 450 560 bytes
>
> Total Files Listed:
> 1 File(s) 1 408 450 560 bytes
> 0 Dir(s) 1 142 890 496 bytes free
>
>
>
>
http://pages.videotron.com/steph1/first_page
F31676C-86DB-4D9C-88AD-9C09379A3F1D@microsoft.com,
Facebook
Twitter
Instagram