Advertisement

There's no such thing as a stupid question, but they're the easiest to answer.
Login
Search

Advertisement

Search Search
Search for:
Tech Support Guy > > >

bootex.txt?


(!)

Fankle's Avatar
Fankle Fankle is offline
Member with 65 posts.
THREAD STARTER
 
Join Date: Jan 2005
Location: Philadelphia, PA, USA
Experience: Intermediate
02-Oct-2006, 10:50 AM #1
bootex.txt?
Hello,
I am not worried about this file, I know it is a log file of some sort, but my question lies in what exactly is it from? On my flash drive I have this file and its contents are as follows:
Code:
Checking file system on E:
The type of the file system is FAT.

The volume is dirty.
Volume Serial Number is EC78-5E19
Windows has checked the file system and found no problems.

   2062254080 bytes total disk space.
       917504 bytes in 24 hidden files.
      5472256 bytes in 167 folders.
   1191051264 bytes in 1560 files.
    864813056 bytes available on disk.

        32768 bytes in each allocation unit.
        62935 total allocation units on disk.
        26392 allocation units available on disk.
What does it mean by the volume is dirty? Where does this file come from? Why not on my C drive (local hard disk)? Any help is appreciated, thank you.
ozrom1e's Avatar
Computer Specs
Member with 11,849 posts.
 
Join Date: May 2006
Experience: Advanced
02-Oct-2006, 11:05 AM #2
Apparently it is from running chkdsk on the drive when doing the task below make sure you tell it to do the drive for the thumb drive and make sure the thumb drive is in the USB port.

Click on the Start menu and open the run dialog.
2. Type "cmd" and return (without quotes)
3. Next type "fsutil dirty query <letter of drive that ckdsk keeps checking>" (for example, C
4. If the returned message indicates that the volume is dirty, go to step 5
5. Next type "chkdsk <drive letter> /f /x"
6. After that finishes, repeat step 3.
7. If the volume is no longer dirty, reboot and chkdsk should not reappear.

The "fsutil dirty query" reports the current state of the flag.
"Chkdsk /f" forces Chkdsk to run whether or not the flag is dirty--- it's a way to ensure that errors are fixed, regardless of what the flag says.
"Chkdsk /x" goes a little further and helps ensure that any files that were left open get closed; it actually implies "/f" so you don't need the /f if you're using /x .
With either /f or /x, at the end of the run, Chkdsk should set the flag to clean
__________________
I still use my Osborne 01 with a 300 Baud modem all the time.

I was always taught to respect my elders, but it keeps getting harder to find one.

Heaven goes by favorites, If it didn't then your dog would get in first. Amen.
As Seen On

BBC, Reader's Digest, PC Magazine, Today Show, Money Magazine
WELCOME TO TECH SUPPORT GUY!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.


(clock)
THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Search Tech Support Guy

Find the solution to your
computer problem!




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools


WELCOME
You Are Using: Server ID
Trusted Website Back to the Top ↑