How to Restore Database in ACCPAC system /Pervasive SQL on corrupted Database

Find below steps for restore Database from your Backup in ACCPAC for any Database related error:

Part- 1

  1. Open PervasiveControlCenter
  2. Go to Tools
  3. Select ODBC Administrator
  4. Click System DNS
  5. Remove corrupted Database

 

Part-2

  1. Go to Pervasive Local Client
  2. Click Engine
  3. Select The Server where database added
  4. Remove corrupted Database

 

Part-3

  1. Open AccDat5.6 from Disk Drive
  2. Delete corrupted database
  3. Create New folder and rename same as corrupted database folder Name

 

Part-4

  1. Go to Sage ACCPAC Database Load
  2. Load Data in to new folder from Backup Database

 

Part-5

  1. Go to Sage ACCPAC Database Setup
  2. Click the New Created Database
  3. Click Edit
  4. Click OK

 

Then run ACCPAC without any error

UNMOUNTABLE BOOT VOLUME XP

UNMOUNTABLE BOOT VOLUME – Blue Screen Error

1.) Start your computer with the Windows CD-ROM if your computer can start from the CD-ROM drive.
2.) When the Welcome to Setup screen appears, press R to select the “Repair with Recovery Console” option.
3.) Select the Windows installation that you want to access from the Recovery Console.
4.) Type the administrator password when you are prompted to do so. NOTE: If no administrator password exists, just press ENTER.
5.) At the command prompt, on the drive where Windows is installed, type CHKDSK /P, and then press ENTER. Your hard drive is then scanned for File System errors. This process shouldn’t take more than 5 minutes.
6.) At the command prompt, type FIXMBR, and choose YES to all the scary warnings that you see regarding rebuilding the MASTER BOOT RECORD.
7.) At the command prompt, type EXIT, and then press ENTER to restart your computer.
8.) When the system reboots, choose “Go to windows”
9.) If the Windows Advanced Startup Menu appears, choose NORMAL MODE.
10.) Remove the Operating System CD.
11.) When you reach the desktop you can be assured that your issue is resolved.

*****Make Sure That your Drive Shows unallocated before you run FIXMBR******

Source: From Web

Manage Alcatel Omni PCx PABX System

How to check internal card (Analog, Digital & NDD) in System and card details?

Login in Console

Pabx> config 0

Pabx> listerm 0 1(card number)

Land Line Phone status check

Pabx> trkstat 100     (e.g Hs= Out of Order, B= Busy, F=Free)

Restart Card

Pabx> rstcpl 0 card number

Group Status

 

Pabx>manager (log in id)

Pabx>Manager> trkstat 100

If Number Busy (Hs)

>inserv n

Y enter

Manage incoming and outgoing call

 

Trunk Group|Enter 4 times|Select trunk|Consult Modify|All instance

|

Trank id 100

|

Ctrl V

|

Select Group

|

Channel Specification inonly/outonly

Change option extension status

>Termstate d extension number

Change option of outgoing call (IDD, Local, Block)

Pabx>manager>user>consult modify>Directory Number….

Ctrl V

Go Public network category

|

Change options (1=local, 2=NWD, 3= ISD)

Exchange Server 2003 Database Repair/ESEUTIL Tools

Below are the steps to repair Windows Exchange Server 2003 Database using eseutil tools. Unable to mount database or Database status showing durty shutdown

1)  First Run  eseutil/mh

D:\Program Files\Exchsrvr\bin>eseutil /mh “d:\program files\exchsrvr\mdbdata\pub
1.edb

Result:

” Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode…
         Database: d:\program files\exchsrvr\mdbdata\pub1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:05/20/2005 14:00:37 Rand:4134905 Computer:
         cbDbPage: 4096
           dbtime: 30289033 (0x1ce2c89)
            State: Dirty Shutdown – “Need To Repair”
     Log Required: 355973-355981 (0x56e85-0x56e8d)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 2823
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x55EA6,10,C2)  05/09/2009 03:04:53
      Last Attach: (0x55EA6,11,165)  05/09/2009 11:29:33
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 2
    Log Signature: Create time:05/20/2005 14:00:37 Rand:4124268 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 355274-355277 (0x56bca-0x56bcd)
           Mark: (0x56BCA,1632,1C9)
           Mark: 05/15/2009 21:00:11

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none

Operation completed successfully in 3.31 seconds.”
PUB1.STM
D:\Program Files\Exchsrvr\bin>eseutil /mh “d:\program files\exchsrvr\mdbdata\pub
1.stm

Result:

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode…
         Database: d:\program files\exchsrvr\mdbdata\pub1.stm

        File Type: Streaming File
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:05/20/2005 14:00:37 Rand:4134905 Computer:
         cbDbPage: 4096
           dbtime: 0 (0x0)
            State: Dirty Shutdown – “Need to Repair
     Log Required: 0-0 (0x0-0x0)
         Shadowed: Yes
       Last Objid: 0
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x55EA6,10,C2)  00/00/1900 00:00:00
      Last Attach: (0x55EA6,11,165)  00/00/1900 00:00:00
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 0
    Log Signature: Create time:05/20/2005 14:00:37 Rand:4124268 Computer:
       OS Version: (5.2.3790 SP 0)

Previous Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

Operation completed successfully in 3.31 seconds.”

2)  Then Run  eseutil/p

D:\Program Files\Exchsrvr\bin>eseutil /p “d:\program files\exchsrvr\mdbdata\pub1
.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode…
        Database: d:\program files\exchsrvr\mdbdata\pub1.edb
  Streaming File: d:\program files\exchsrvr\mdbdata\pub1.STM
  Temp. Database: TEMPREPAIR3544.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the ‘Recovery’ operation.
                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Scanning the database.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Repairing damaged tables.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|

Deleting unicode fixup table.
……………………………………………

Repair completed. Database corruption has been repaired!

Note:
  It is recommended that you immediately perform a full backup
  of this database. If you restore a backup made before the
  repair, the database will be rolled back to the state
  it was in at the time of that backup.

 

Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 183.31 seconds.

pub1.stm
D:\Program Files\Exchsrvr\bin>eseutil /p “d:\program files\exchsrvr\mdbdata\pub1
.stm

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode…
        Database: d:\program files\exchsrvr\mdbdata\pub1.stm
  Temp. Database: TEMPREPAIR5868.EDB

Checking database integrity.

 
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 3.141 seconds.

 
D:\Program Files\Exchsrvr\bin>eseutil /p “d:\program files\exchsrvr\mdbdata\pub1
.stm

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode…
        Database: d:\program files\exchsrvr\mdbdata\pub1.stm
  Temp. Database: TEMPREPAIR3504.EDB

Checking database integrity.

 
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 3.0 seconds.

 
D:\Program Files\Exchsrvr\bin>

2)  Then Run  eseutil/d

D:\Program Files\Exchsrvr\bin>eseutil /d “d:\program files\exchsrvr\mdbdata\pub1
.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating DEFRAGMENTATION mode…
            Database: d:\program files\exchsrvr\mdbdata\pub1.edb
      Streaming File: d:\program files\exchsrvr\mdbdata\pub1.STM
      Temp. Database: TEMPDFRG3884.EDB
Temp. Streaming File: TEMPDFRG3884.STM

                  Defragmentation Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………
Moving ‘TEMPDFRG3884.EDB’ to ‘d:\program files\exchsrvr\mdbdata\pub1.edb’… DON
E!

Moving ‘TEMPDFRG3884.STM’ to ‘d:\program files\exchsrvr\mdbdata\pub1.stm’… DON
E!

Note:
  It is recommended that you immediately perform a full backup
  of this database. If you restore a backup made before the
  defragmentation, the database will be rolled back to the state
  it was in at the time of that backup.

Operation completed successfully in 136.297 seconds.

4. And Finaly Run eseutil/mh

D:\Program Files\Exchsrvr\bin>eseutil /mh “d:\program files\exchsrvr\mdbdata\pub
1.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode…
         Database: d:\program files\exchsrvr\mdbdata\pub1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,11
     DB Signature: Create time:07/14/2009 19:09:42 Rand:79660670 Computer:
         cbDbPage: 4096
           dbtime: 1089607 (0x10a047)
            State: Clean Shutdown – ” Repaird Successfully”
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 628
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 07/14/2009 18:57:50
 Old Repair Count: 2
  Last Consistent: (0x0,0,0)  07/14/2009 19:11:54
      Last Attach: (0x0,0,0)  07/14/2009 19:09:43
      Last Detach: (0x0,0,0)  07/14/2009 19:11:54
             Dbid: 2
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none

Operation completed successfully in 3.32 seconds.
D:\Program Files\Exchsrvr\bin>eseutil /mh “d:\program files\exchsrvr\mdbdata\pub
1.stm

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode…
         Database: d:\program files\exchsrvr\mdbdata\pub1.stm

        File Type: Streaming File
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,11
     DB Signature: Create time:07/14/2009 19:09:42 Rand:79660670 Computer:
         cbDbPage: 4096
           dbtime: 0 (0x0)
            State: Clean Shutdown – “Repaired Successfully”
     Log Required: 0-0 (0x0-0x0)
         Shadowed: Yes
       Last Objid: 0
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  00/00/1900 00:00:00
      Last Attach: (0x0,0,0)  00/00/1900 00:00:00
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 0
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

Operation completed successfully in 3.0 seconds.

 

 
 

ACCPAC Installation Error:ACCPAC is running or in use, please exits all instances of the desktop,please stop the iconnect and process server services if they are running , please exit any application that integrate with ACCPAC

for trouble to install ACCPAC everytime its showing the error “ACCPAC is running or in use, please exits all instances of the desktop,please stop the iconnect and process server  services if they are running , please exit any application that integrate with ACCPAC” But didnt find any process running which integrate with ACCPC. Please find below solutions

1. Go to Map Drive for ACCPAC (Ex: R:\)

2. Click R:\Site

3. Delete Semaphor.bin file ( For deleting this file you will faied to do it if any other person connect with ACCPAC, Make sure no one is using ACCPAC during you deletion this file. Stop The database service then try. Hope it will help you to instal ACCPAC without this trouble.

stop: c0000218 {resistry file failure} the resistry can not load the hive (file)\system root\system32\config\software or its log or alternate it is corrupt, absent, or not writable

Part one

In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. When you have finished this procedure, a registry is created that you can use to start Windows XP. This registry was created and saved during the initial setup of Windows XP. Therefore any changes and settings that occurred after the Setup program was finished are lost.

To complete part one, follow these steps:

  1. Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
    Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so.
  2. When the “Welcome to Setup” screen appears, press R to start the Recovery Console.
  3. If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console.
  4. When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER.
  5. At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line:
    md tmp
    copy c:\windows\system32\config\system c:\windows\tmp\system.bak
    copy c:\windows\system32\config\software c:\windows\tmp\software.bak
    copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
    copy c:\windows\system32\config\security c:\windows\tmp\security.bak
    copy c:\windows\system32\config\default c:\windows\tmp\default.bak

    delete c:\windows\system32\config\system
    delete c:\windows\system32\config\software
    delete c:\windows\system32\config\sam
    delete c:\windows\system32\config\security
    delete c:\windows\system32\config\default

    copy c:\windows\repair\system c:\windows\system32\config\system
    copy c:\windows\repair\software c:\windows\system32\config\software
    copy c:\windows\repair\sam c:\windows\system32\config\sam
    copy c:\windows\repair\security c:\windows\system32\config\security
    copy c:\windows\repair\default c:\windows\system32\config\default

  6. Type exit to quit Recovery Console. Your computer will restart.

Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step five, and then create a text file called “Regcopy1.txt” (for example). To use this file, run the following command when you start in Recovery Console:

batch regcopy1.txt

With the batch command in Recovery Console, you can process all the commands in a text file sequentially. When you use the batch command, you do not have to manually type as many commands.

Part two

To complete the procedure described in this section, you must be logged on as an administrator, or an administrative user (a user who has an account in the Administrators group). If you are using Windows XP Home Edition, you can log on as an administrative user. If you log on as an administrator, you must first start Windows XP Home Edition in Safe mode. To start the Windows XP Home Edition computer in Safe mode, follow these steps.

Note Print these instructions before you continue. You cannot view these instructions after you restart the computer in Safe Mode. If you use the NTFS file system, also print the instructions from Knowledge Base article KB309531. Step 7 contains a reference to the article.

  1. Click Start, click Shut Down (or click Turn Off Computer), click Restart, and then click OK (or click Restart).
  2. Press the F8 key.On a computer that is configured to start to multiple operating systems, you can press F8 when you see the Startup menu.
  3. Use the arrow keys to select the appropriate Safe mode option, and then press ENTER.
  4. If you have a dual-boot or multiple-boot system, use the arrow keys to select the installation that you want to access, and then press ENTER.

In part two, you copy the registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is generally not visible during typical usage. Before you start this procedure, you must change several settings to make the folder visible:

  1. Start Windows Explorer.
  2. On the Tools menu, click Folder options.
  3. Click the View tab.
  4. Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the Hide protected operating system files (Recommended) check box.
  5. Click Yes when the dialog box that confirms that you want to display these files appears.
  6. Double-click the drive where you installed Windows XP to display a list of the folders. If is important to click the correct drive.
  7. Open the System Volume Information folder. This folder is unavailable and appears dimmed because it is set as a super-hidden folder.Note This folder contains one or more _restore {GUID} folders such as “_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}”.

    Note You may receive the following error message:

    C:\System Volume Information is not accessible. Access is denied.

    If you receive this message, see the following Microsoft Knowledge Base article to gain access to this folder and continue with the procedure:

    309531  (http://support.microsoft.com/kb/309531/ ) How to gain access to the System Volume Information folder
  8. Open a folder that was not created at the current time. You may have to click Details on the View menu to see when these folders were created. There may be one or more folders starting with “RPx under this folder. These are restore points.
  9. Open one of these folders to locate a Snapshot subfolder. The following path is an example of a folder path to the Snapshot folder:
    C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
  10. From the Snapshot folder, copy the following files to the C:\Windows\Tmp folder:
    • _REGISTRY_USER_.DEFAULT
    • _REGISTRY_MACHINE_SECURITY
    • _REGISTRY_MACHINE_SOFTWARE
    • _REGISTRY_MACHINE_SYSTEM
    • _REGISTRY_MACHINE_SAM
  11. Rename the files in the C:\Windows\Tmp folder as follows:
    • Rename _REGISTRY_USER_.DEFAULT to DEFAULT
    • Rename _REGISTRY_MACHINE_SECURITY to SECURITY
    • Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
    • Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
    • Rename _REGISTRY_MACHINE_SAM to SAM

These files are the backed up registry files from System Restore. Because you used the registry file that the Setup program created, this registry does not know that these restore points exist and are available. A new folder is created with a new GUID under System Volume Information and a restore point is created that includes a copy of the registry files that were copied during part one. Therefore, it is important not to use the most current folder, especially if the time stamp on the folder is the same as the current time.

The current system configuration is not aware of the previous restore points. You must have a previous copy of the registry from a previous restore point to make the previous restore points available again.

The registry files that were copied to the Tmp folder in the C:\Windows folder are moved to make sure that the files are available under Recovery Console. You must use these files to replace the registry files currently in the C:\Windows\System32\Config folder. By default, Recovery Console has limited folder access and cannot copy files from the System Volume folder.

Note The procedure described in this section assumes that you are running your computer with the FAT32 file system. For more information about how to access the System Volume Information Folder with the NTFS file system, click the following article number to view the article in the Microsoft Knowledge Base:

309531  (http://support.microsoft.com/kb/309531/ ) How to gain access to the System Volume Information folder

Part Three

In part three, you delete the existing registry files, and then copy the System Restore Registry files to the C:\Windows\System32\Config folder:

  1. Start Recovery Console.
  2. At the command prompt, type the following lines, pressing ENTER after you type each line:
    del c:\windows\system32\config\sam

    del c:\windows\system32\config\security

    del c:\windows\system32\config\software

    del c:\windows\system32\config\default

    del c:\windows\system32\config\system

    copy c:\windows\tmp\software c:\windows\system32\config\software

    copy c:\windows\tmp\system c:\windows\system32\config\system

    copy c:\windows\tmp\sam c:\windows\system32\config\sam

    copy c:\windows\tmp\security c:\windows\system32\config\security

    copy c:\windows\tmp\default c:\windows\system32\config\default

    Note Some of these command lines may be wrapped for readability.

  3. Type exit to quit Recovery Console. Your computer restarts.

Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step two, and then create a text file called “Regcopy2.txt” (for example). To use this file, run the following command when you start in Recovery Console:

batch regcopy2.txt

Part Four

  1. Click Start, and then click All Programs.
  2. Click Accessories, and then click System Tools.
  3. Click System Restore, and then click Restore to a previous RestorePoint

Source: Microsoft Web

XP TIPS

From below link you will find lots of XP Tips

http://www.onecomputerguy.com/windowsxp_tips.htm