Files system is still incomplete? Why

Similar Questions

• DRM data files is stored in the file system

  Hello team, in DRM I have 2 or 3 applications originally created 2 months ago. Now, I'm getting issue in DB space such as the data files are created the Local file system. Names of sample files are as below.

  
  

  / ddtrg7/Oracle/product/112/DBS/DRM_DATA

  /ddtrg7/oracle/product/112/dbs/DRM_INDEX

  /ddtrg7/oracle/product/112/dbs/DRM_PROPS

  /ddtrg7/oracle/product/112/dbs/DRM_TRANS

  /ddtrg7/oracle/product/112/dbs/DTRSPECDRM_DATA

  /ddtrg7/oracle/product/112/dbs/DTRSPECDRM_INDEX

  /ddtrg7/oracle/product/112/dbs/DTRSPECDRM_PR

  /ddtrg7/oracle/product/112/dbs/DTRSPECDRM_TRANS

  /ddtrg7/oracle/product/112/dbs/DTRDRM_DATA

  /ddtrg7/oracle/product/112/dbs/DTRDRM_INDEX

  /ddtrg7/oracle/product/112/dbs/DTRDRM_PROPS

  /ddtrg7/oracle/product/112/dbs/DTRDRM_TRANS

  
  

  We see in the newspapers that the tablespaces and data files have been created in ASM diskgroup even during the installation period. I think that since "/ dmtng7/oracle/product/112/dbs / ' is the place where DB settings file, it could be that the location has been provided as input during the installation/configuration. Ask for your help in this on how to get rid of this problem. We don't need this to be grown in the file system. Please indicate why these files are created.

  The kind assistance in the present.

  
  

  
  Thank you, roshi

  Problems you meet again.

  Thank you

  ~ KKT ~.

• Why can't I convert my FAT32 to NTFS file system in Win XP SP3?

  I want to move to Vista and Windows 7.  When I ran the upgrade for Vista, I was told that I had to do a clean install and upgrade option has been disabled due to the FAT 32 from my hard drive file system.  I can't wipe my drive because I have a bunch of stuff and I don't have the storage means to do so.

  I followed the instructions on how to convert without data loss, but when I arrived at the command line and entered ' convert c: / fs:ntsf "I got a message that the drive had to be dismantled and that it translated when I rebooted.  So I've done that and restarted.  The blue screen came and began to convert.  Then there were a bunch of error messages regarding bad sectors or bad files and that it could not be converted.

  I then ran chkdsk and chkdsk /f.  The first chkdsk says that there are errors, but they would not fixed because I didn't run with the extension/f.  So I did this and then said that he had to do a restart.  So I restarted and the chkdsk took forever.  When I got back to my office, I ran the line convert again and now I get something along the line of FAT32 and NTFS conversion are not available.

  So in addition to abandon and wipe my drive, how can I fix my drive?  Of course, chkdsk /f has not helped and not more than chkdsk/r.  I tried the magic of partition, acronis, and anything else I can get my hands.

  What should I do now?

  Hi sweetp267,

  Try these steps and check the result.
  a. connect to the admin user account.
  b. Click Start, run, type cmd and click ok.
  (c) in the command prompt, type the following command and press ENTER: CONVERT C:/FS: NTFS /V
  d. check the difference.

  The /V will verbose mode and can give more information, if it fails. A restart will be required because the drive is currently in use by the operating system.

  See How to convert a volume to FAT32 to NTFS in Windows XP file system

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Why can't I use a virtual hard disk on a UDF file system?

  I have an external hard drive that has eSata and USB connection formatted in NTFS, where I have bootmgr and let me run windows native installers installations and windows on virtual hard drives with different software and different versions of Windows for testing purposes installed.

  I wanted to copy a VHD to another USB that is used to share files with other operating systems and is formatted with the UDF, who is reading and writing on all operating systems.

  Here it is: I can't use the VHD to a file directly from UDF system.

  I can understand that, because of the file system limits, cannot use extensible VHDs on UDF. But I opened a command line, type DISKPART, ' select vdisk file = [UDF disc]: \07-100-clean.vhd "and says it's a unsupportted action.

  Well... Make this hard drive virtual bootable since a UDF its imposible because it means modifing the bootloader, but:

  How can I reach a kick from Windows 7?

  Hello

  This is a go to TechNet and ask the same question, given that this problem is taken in charge out there and not here.

  Rob - SpiritX

• I had problems with my gc, cleaned and he is now allowed outside my control file system system, that it will take place at 68% and stops running

  I had problems with my graphics card cleaned and it works well apart from the system of checking file system on C: turns 68% and stops. If I have to cancel the computer checking seems to work ok, or is it?

  I guess that Mark_S_Sloan is talking about chkdsk /r or running a disk check with fixed error on a restart. so I would say that what I used to say the performance is chkdsk:

  The chkdsk/r can take a long time to complete depending on the size of the volume, the amount of data on the volume, the speed of the system and what chkdsk is to do.  It take about 2 hours for chkdsk/r run on one of the volumes of my1TB (I'm a right that I rarely run).

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.  Give him a chance.

  @Imran M - Microsoft technical support engineer:

  Don't you know that the performance of the auditor of the filesystem (sfc/scannow) does not provide a percentage of completion?  Have you ever used it?

  He also really tell you anything about what he did, or could have done when it is executed even if she finds something to do.

  Everything you see in the Event Viewer system log are messages like this:

  Event type: Information
  Event source: Windows File Protection
  Event category: no
  Event ID: 64016
  Analysis of file File Protection Windows has been started.

  .. few time later...

  Event type: Information
  Event source: Windows File Protection
  Event category: no
  Event ID: 64017
  Windows File Protection file analysis completed successfully.

  Even if sfc/scannow find something to do, you will know about it, because it is not connected.

  That's why use sfc/scannow still more of a waste of time.

• ASM cluster file system and df h

  Hello Oracle Community,

  I was wondering why my ASM cluster file system showing 96% (25 GB free) used, even if I moved and deleted (200 GB +) I still exports datapump see 96%.  When running the - h - max-depth = 1, it shows the correct value of 216 GB used.  But this isn't until hours later, when you run df h even once, I finally see the free space on the drive, which I was expecting.  The system is a RAC run red hat 6.5 with Oracle SE 11.2.0.4.

  [shared me@db02] $ - h - max-depth = 1
  from: cannot read directory '. / lost + found ': Permission denied
  64 k. / lost + found
  1.9 G. / datapump
  129. M / temp
  53. M / ctrlfilebkup
  214. G / dailyexport
  216G.
  [shared me@db02] $ df-h

  / dev/ASM/acfsvol-287 548 G 524 G 25 G 96% / u05/shared

  Could someone please clarify why this is happening.

  Thanks to you all!

  Found the answer:

  http://www.LinuxQuestions.org/questions/Linux-General-1/different-results-in-du-and-DF-841145/

• Rescue and Recovery backup not file system - without error message

  I use, since 1985 the first IBM, Lenovo then. I was very happy, my next Lenovo will be bought next spring.

  But I'm just very disappointed. Daily tracks of rescue and recovery on the local disk, which later are copied to a backup drive.

  The program has never shown an error on the screen and still run perfectly-, I thought!

  A few days ago, I got a Windows error for the first time. There are a lot of missing files.
  I restored the system on the R & R and reboted. But cannot start.
  With a boot disk, I booted the system and could now see that all the Windows directory was empty!

  Unfortunately, I can not in R & R files see what files and directories contain a backup? Or can you?

  Question 1:

  So I would like to know how if someone can enlighten me.

  Then I started to investigate on what had happened. In c:-Library SWSHARE I found some files that I see is connected to R & R.
  In the engine.log file, I see R & R has written a large number of error lines, of which a part is reproduced below. File dates to 2011 and there are errors all the way

  Question 2:
  Why the program not onscreen when R & R run display errors, so that the user knows there are errors?

  Now I'm sitting at the bottom with a long nose, after 2 days and nights, trying to find a solution and restored the system several times and do not know how the file system works will come back on my PC so normally again.

  Be more happy if someone can tell me how to solve this problem.

  Here is a selection of error lines:

  Thu 17 Oct 08:41:59 ENGINE 2013: failed to send an IOCTL_FFDRIVER_ENCRYPT_OFF
  Thu 17 Oct 08:43:38 engine 2013: br_funcs.exe - version is '04.17.20a.00 '.
  Thu 17 Oct 08:43:40 engine 2013: CopySAM called with pwszDestination = "C:\RRbackups\common".
  Thu Oct 17 08:43:44 engine 2013: out of CopySAM with dwRet = 0 x 00000000
  Thu 17 Oct 17:00:09 engine 2013: br_funcs.exe - version is '04.17.20a.00 '.
  Thu 17 Oct 17:00:09 engine 2013: DeleteSISAndExclude (delType 1, drive letter C, Destination 'C:\RRbackups', level 12)
  Thu Oct 17 17:01:25 engine 2013: DeleteSISAndExclude out with return code 0 x 00000000
  Thu Oct 17 17:01:59 2013 engine: br_funcs.exe - version is '04.17.20a.00 '.
  Thu Oct 17 17:01:59 2013 Verbatim: WriteDriveContents (DriveLetter ='C:', Dest = 'C:\RRbackups', level = 13, SleepCount = 0, DeviceType = 1, dwOptFlags = 0 x 00000001)
  Thu Oct 17 17:05:48 2013 Verbatim: 0x00000010883e6399 - space required before compression
  Thu Oct 17 17:05:49 2013 Verbatim: 0x00000001ef30e1bf - estimated space required after compression
  Thu Oct 17 17:05:49 2013 Verbatim: 0x0000001dae2dd000 - currently available disk space
  Thu 17 Oct 17:07:27 2013 Verbatim: can't get exclusive lock for the entire file 'C:\Documents and Settings\Bendt Skov.DK\Application Data\Mozilla\Firefox\Profiles\gbkxfkqd.default\cookies.sqlite-shm' - WinRC = 0x00000000
  Thu 17 Oct 17:07:30 2013 Verbatim: can't get exclusive lock for the entire file 'C:\Documents and Settings\Bendt Skov.DK\Application Data\Mozilla\Firefox\Profiles\gbkxfkqd.default\healthreport.sqlite-shm' - WinRC = 0x00000000
  Thu 17 Oct 17:07:31 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\Bendt Skov.DK\Application Data\Mozilla\Firefox\Profiles\gbkxfkqd.default\parent.lock" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu 17 Oct 17:07:33 2013 Verbatim: can't get exclusive lock for the entire file 'C:\Documents and Settings\Bendt Skov.DK\Application Data\Mozilla\Firefox\Profiles\gbkxfkqd.default\places.sqlite-shm' - WinRC = 0x00000000
  Thu 17 Oct 17:07:34 2013 Verbatim: can't get exclusive lock for the entire file 'C:\Documents and Settings\Bendt Skov.DK\Application Data\Mozilla\Firefox\Profiles\gbkxfkqd.default\webappsstore.sqlite-shm' - WinRC = 0x00000000
  Thu Oct 17 17:08:28 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\Bendt Skov.DK\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:08:30 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\Bendt Skov.DK\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:02 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\Bendt Skov.DK\NTUSER." DAT' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:09 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\Bendt Skov.DK\ntuser.dat.LOG" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:15 engine 2013: CreateFileW failed for the file 'C:\Documents and Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG LocalService' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:16 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\LocalService\NTUSER. DAT' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:17 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\LocalService\ntuser.dat.LOG" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:18 engine 2013: CreateFileW failed for the file 'C:\Documents and Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG Settings' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:19 engine 2013: CreateFileW failed for the file ' C:\Documents and NetworkService NTUSER. DAT' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:20 engine 2013: CreateFileW failed for the file "C:\Documents and Settings\NetworkService\ntuser.dat.LOG" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:09:25 Verbatim 2013: cannot save short name of "C:\hiberfil.sys" - WinRC = 0x00000020
  Thu Oct 17 17:09:25 engine 2013: impossible to attributes of record for the file "C:\hiberfil.sys" - WinRC = 0x00000020
  Thu Oct 17 17:09:47 2013 Verbatim: cannot save short name of "C:\pagefile.sys" - WinRC = 0x00000020
  Thu Oct 17 17:09:47 engine 2013: impossible to attributes of record for the file "C:\pagefile.sys" - WinRC = 0x00000020
  Thu Oct 17 17:11:50 engine 2013: CreateFileW failed for the file "C:\Program Files\Bitdefender\Bitdefender\onaccess.dat" and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:19:49 motor 2013: jump from the C:\Program Files\Bitdefender\Bitdefender\onaccess.dat file at the request of the user
  Thu Oct 17 17:23:10 engine 2013: CreateFileW failed for file ' C:\Program Files\Common Files\Bitdefender\Bitdefender threatens Scanner\smartdb - ntfs.db' and the reason was not a sharing violation - Windows RC = 0 x 00000020
  Thu Oct 17 17:33:13 engine 2013: jump to the folder C:\Program Files\Common Files\Bitdefender\Bitdefender threat Scanner\smartdb - ntfs.db at the request of the user
  Thu Oct 17 17:37:08 2013 engine: BackupFile failed - unable to "C:\WINDOWS" BackupRead - GetLastError() returns 0x00000020
  Thu Oct 17 17:37:08 2013 engine: unable to BackupFile directory C:\WINDOWS - dwRet = 0 x 00000516
  Thu Oct 17 17:37:09 2013 Verbatim: can't get exclusive lock for the entire file "C:\Documents and Settings\Bendt Skov.DK\Local Settings\Application Data\Microsoft\Outlook\outlook.pst" - WinRC = 0x00000000
  Thu Oct 17 17:37:13 2013 Verbatim: can't get exclusive lock for the whole of the file "C:\Documents and Settings\Bendt Skov.DK\Local Settings\Application Data\Microsoft\Outlook\Personal folders (1) .pst '-WinRC = 0 x 00000000"
  Thu Oct 17 17:37:15 2013 Verbatim: can't get exclusive lock for the entire file "C:\Privat\bendtskov-hotmail Arkiv.pst" - WinRC = 0x00000000
  Thu Oct 17 17:37:16 Verbatim 2013: can't get exclusive lock for the entire file "C:\Privat\morkebjerg-hotmail Arkiv.pst" - WinRC = 0x00000000
  Thu Oct 17 17:37:17 2013 Verbatim: WriteDriveContents exit with return code 0 x 00000000
  Thu Oct 17 17:37:25 engine 2013: br_funcs.exe - version is '04.17.20a.00 '.
  Thu Oct 17 17:37:25 engine 2013: CopySAM called with pwszDestination = "C:\RRbackups\common".
  Thu Oct 17 17:37:26 engine 2013: out of CopySAM with dwRet = 0 x 00000000
  Thu Oct 17 22:34:38 engine 2013: br_funcs.exe - version is '04.17.20a.00 '.
  Thu Oct 17 22:34:39 engine 2013: CopySAM called with pwszDestination = "C:\RRbackups\common".
  Thu Oct 17 22:34:42 engine 2013: out of CopySAM with dwRet = 0 x 00000000

  
  

• Apple and legacy applications file system?

  Hello

  I heard that Apple will release Apple (SATF) filesystem in 2017.

  I'm sorry, I have no idea what it means for my system. Will be my apps (I got a few apps too, and the apps that I don't have form the Mac App Store) continue to work?

  Thank you for your help.

  Best regards, Fabian

  The release of a new file system has nothing to do with your applications, so they will still work correctly if you start to use it (even if you need to check that your applications are supported whenever you upgrade OS X)

• Probbok 4530 s: file system on the hard drive for HP Probbok 4530 s recovery

  Hello world

  I knew that the hard disk file system must be a particular type to allow for the recovery of the HP Probook 4530 s factory. The problem is when the narrowing of my drive, I changed to NTFS and I forgot which is the file format native allowing rocovery. This is why the recovery process does not work.

  Anyone know what to do? Help, please... Thanks in advance!

  NTFS is the native file for Windows 7 system. If you have added additional partitions and/or that you converted your hard disk from basic to dynamic that would be the cause of recovery does not.

  Contact HP for recovery media.

  If you live in the United States / CA, coordinated HP here.

• Hard drive stuck in the RAW file system.

  So I had a problem with my slave drive being stuck in the RAW file system when I formatted my master drive. So I disconnected the slave drive and formatted the master once again and once all updates have been installed, I plugged the slave back in. He's still stuck in RAW format. I tried to use Norton Partition Magic, and he reads a BAD. Is it possible to change the same RAW to NTFS or FAT32 file system?

  The indication that the file system is RAW usually means that there is a corruption of the file system structures. How to go on recovery depends on the value you are asking about the data on the disk. If your budget of time or money is over and the data of low value or backed up.

  Go to start all programs accessories and click on the command line. When the window opens, type

  cmd
  CHKDSK D: /f /r Note: D: is the letter of the drive to check. Replace the appropriate letter.

  When the process is finished, type
  Output

  Go to my computer to see if it was repaired enough to at least get a list of directories.

  If no joy, go to the web site of the manufacturer of the disk. Looking for a utility to check the disk and make a low-level format ". Follow their instructions. After that, do a format to NTFS.

  If this fails, it is likely that the disc will need to be replaced.

  Remember, there are tools (the disk sector editors, etc.) that you can use to read and sometimes at least recover some data. It requires appropriate knowledge and considerable patience. Alternatively, there are services - quite expensive data recovery.

  Tom

• I ran CHKDSK, the report tells me I have problems with the file system, usn journal. ___

  I ran CHKDSK, the report tells me that I have problems with the sys file. I ran CHKDSK/F, it is said it fixed the problem but I ran CHKDSK again and it shows that the same listed the issues.

  Describe how you run chkdsk.

  That is what the report said: you have problems with the sys file?

  CHKDSK examines the disk space and use of the disk for the table of allocation of files (FAT) and NTFS file systems. CHKDSK provides information specific to each file system in a situation report. The report shows the errors found in the file system. If you run chkdsk without the /f on an active partition command line option, it can report errors because it cannot lock the drive. You should use chkdsk occasionally on each disk to check for errors.

  If you run chkdsk from a command prompt while Windows is running, it can report errors or it may not report errors - and it may report different
  Errors each time you run.  If this is the case, it could just be the way you run chkdsk.

  Here's how Microsoft explains this observation:

  "... CHKDSK may report that the disc is damaged, even when there is no
  current real corruption. This can happen if NTFS happens to modify
  areas of the disc on behalf of some programme activities that CHKDSK is
  review at the same time. To check a volume correctly, the volume
  must be in a static state, and the only way to ensure that the State is
  to lock the volume. CHKDSK only locks the volume when /F or/r (which
  involves the 'F') is specified. For example, you may need to run CHKDSK more than
  time so that it can complete all the steps in read-only mode. »

  If you run chkdsk from a command prompt, you are not the necessary static state and you can encounter errors "when no real corruption is present. This is how it works when you use this way.  Any changes made to a NTFS file system modifies the USN Journal.  If you are not in a static state, your USN change Journal probably all the time, so what you see (says something like that) can be quite normal.

  Two ways to ensure that you are in a static state is to run chkdsk from the Recovery Console or to schedule a chkdsk to run the next time that the system
  Restart by answering Yes to the question:

  Would you want to check this volume to be the next time the system restarts?

  If chkdsk reports errors when running in a static state, the errors should be investigated, resolved or explained.  This may take several
  chkdsk runs all of the issues and some problems cannot be resolved by chkdsk.

  If chkdsk runs the next time the system is restarted, the activity and the result will be displayed in the application event log.  Look in the Application log for
  Winlogon events and a source have the date and the duration nearby time chkdsk.

  It is in fact a chkdsk additional reading if you want to learn about it and it will explain everything you see and why your expectations exceed reality.

  Please vote my posts as helpful so I can get a lot of points. I'm saving for a pony!

• I had the virus 'file system' I ran most of MS who removed it... then the screen turned gray and all the icons and files have disappeared... I can't use restore even in safe mode

  I had the virus 'file system' and ran the Microsoft Essentials who kidnapped... Then the screen turned grat and all my tyop desktop icons disappeared and my files... I tried to use the restore but it wouldn't return back or in SafeMode... also, I get a notice that the Task Manager is disabled? How can I turn back?

  Hi David McGeady.

  ·         You are able to open in safe mode Task Manager?

  Follow these methods.

  Method 1: Scan the file system (CFS) auditor to repair corrupted files.

  Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)

  http://support.Microsoft.com/kb/310747

  Method 2: It seems that the virus is still there. Performs a search using the Microsoft safety scanner.

  http://www.Microsoft.com/security/scanner/en-us/default.aspx

  Note: If bad sectors are found in the hard drive, then it could try to fix this particular sector. If you have any data on that, it can get lost.

  Method 3: Create a new user account.

  How to create and configure user accounts in Windows XP

  http://support.Microsoft.com/kb/279783

  If the problem is resolved in a new user account, and then follow the article on how to fix a corrupted user account.

  How to copy data from a corrupted to a new profile in Windows XP user profile

  http://support.Microsoft.com/kb/811151

• FAT32 can convert my NTFS file system?

  my computer is in FAT32 instead of NTFS file system and it won't let me format it, what should I do?

  my computer is in FAT32 instead of NTFS file system and it won't let me format it, what should I do?

  First of all. Note that your * computer * is not FAT32, it is your hard disk which is FAT32. You may have several diosk readers and some could be some FAT32 and NTFS.

  Second, you cannot format your drive from Windows; It is like cutting the branch of a tree, on which you sit.

  Third, why do you want to get in shape? To reinstall Windows or simply to change to NTFS? If you want to reinstall Windows, boot from the Windows CD and follow the instructions for a clean install. It will begin by formatting the drive for you.

  But if you just want to change your drive to the NTFS format, use the CONVERT command. But first read http://www.aumha.org/a/ntfscvt.htm because there is an important question about the size of cluster that is not obvious.

  Note also that conversion is an important step, touching everything on your drive. When you take a big step, no matter how unlikely it is always possible that something can go wrong. For this reason, it is prudent to make sure that you have a backup of everything you can't afford to lose before you start.

• boot problems after "disk error-checking/control - automatically fix file system errors.

  I ran the two options 'check disk' after deleting some old programs and was prompted to restart. When it restarts it was all white screen, then I stop after waiting a few minutes using the power button. now it won't start at all - I have white screen and cannot even get into safe mode by pressing F8. white screen and the fan runs. I is not original boot CD, so tried a CD recovery Norton but would not start from that. I checked the monitor cables.

  It's a 2002 eveshamvale:
  Windows XP Home Edition Service Pack 3 (build 2600)
  Board: Gigabyte Technology Co., Ltd. 8ID533 1.x
  The bus clock: 100 MHz
  BIOS: Award Software International, Inc. 6.00 PG 11/11/2002

  would be grateful for any ideas.
  Thank you

  If you used the power switch, you can inadvertently damage your file system, so before wasting time to try a bunch of things, I could do this (or you may be wasting a lot of time to try things too):

  The question was preceded by a loss of power, aborted reboot or abnormal termination? (This includes the plug pulling, buttons power and removing the battery).

  These can cause corruption in the file system that must be fixed before you do anything else.

  If none of these events occurred (or even if they have not taken place), you must verify the integrity of your file system before anything else (especially "try" things).

  There is zero logic to begin to try to begin to try to modify or copy files to a hard drive that has a corrupted file system, so this must first be fixed using the XP chkdsk program and run chkdsk on your hard drives may solve your problem completely.

  Use the XP Recovery Console to check the file system on your HARD drive and fix the problems and then try to start your system - this may be all you need to do.  Or, you are welcome to just start trying things that might work.

  Boot into the Recovery Console Windows using an XP bootable installation CD.

  If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

  This is not the same as recovery disks that may have come to a store to purchase the system.

  You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

  The ISO bootable image file you need to download is called:

  xp_rec_con. ISO

  Download the ISO from here:

  http://www.mediafire.com/?ueyyzfymmig

  Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

  http://www.ImgBurn.com/

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be.

• 32 file system of Windows xp continues to go corrupt.

  My computer restarts just in itself, but when it restarts it get a message saying it cannot start because the System 32 has been corrupted.
  then he said to incert the system disk and press 'R' to repair the files. but when I do it asks what installation I want to connect to. I have no idea what it means.
  But if I try to type anything, it let me just type a letter and it must be uppercase.

  This problem continues to be that I used a Department of defence hard drive clean and reinstalled windows xp and within three days its doing this yet.
  I used the same system disk on my other computer with no problems. I took a picture of what the message on the screen in the link to photobucket

  http://i1208.Photobucket.com/albums/cc372/Q5Q/screenshots/80cc4c33.PNG

  I would like to know what can be the cause of this and how to stop it.

  Thank you

  When you see the message:

  Windows XP could not start because the following file is missing or damaged:
  \WINDOWS\SYSTEM32\CONFIG\SYSTEM

  This means that the hard disk file system is corrupted and XP cannot find the files needed to load up - he's trying to start, but it cannot find the files needed.

  What DOES mean, is that you need to implement Microsoft KB article KB307545, which is what most of the people tend to want to start when they see the problem.

  They think that's because it's the first thing coming in a Google or Bing search, but is not the problem.  If they take some time to reproduce the problem, understand it and fix a few hundred times (or more), they would never recommend this article once again (for this symptom).

  Here is a link to a thread where you can see how it is easy to solve the problem.

  In this thread, you can see where the engineer of Microsoft Support (probably limited to only understanding Bing and Microsoft KB articles) goes in the WRONG direction...

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-system/after-Windows-restart-and-then-no-configsystem/83d5c57f-9836-4f3a-bec8-04c7d81861d3

  After following my instructions, the user reports:

  now after following your recommendation to use followed by chkdsk /r recovery console command, my system started successfully at first start upward without any error... config/system registry.

  Generally, this problem comes after a power failure, power failure, pressing the power button, restart aborted, abnormal or the battery load - stop while XP is running.  None of this seems familiar?

  Third-party programs can sometimes corruption - as some earlier versions of Norton/Symantec products.  Maybe your program DOD also the origin of the problem.

  It could also be that your DOD cleaner is really delete files for some reason any or do anything else to cause the problem.  If it's true that the files are really missing after cleaning, this DOD program has a problem.

  Can you not use the program for a few days and see if your system "lasts" longer without it?  That's what I suspect.

  It seems that since your screen shot that you are about to enter the XP Recovery Console and it's where you have to fix your immediate without boot problem (a good thing).

  Here part of my itinerary and paste on what to do for your situation and how to use the XP Recovery Console to repair.  You are almost there - just need to know how to react to the Recovery Console...

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be