FACTORY DATA RESET IN ANDROID

Hard reset can be done in 3 ways:

1. Go to Settings –> Privacy –> Factory data reset. This method is valid for all the mobile phones. However, many users have experienced problems in resetting the phone using this method. Also, please note that this method only does a factory reset.
2. Hard reset using a hack code: *2767*3855# — Dial this code on your phone. Please note: DO NOT TRY THIS for testing purpose unless you are sure what you want to do. This code does not ask for a confirmation.
3. Factory reset using: *#*#7780#*#* — Dial this code on your phone. This will ask you for a confirmation before resetting.

It is highly recommended that you take a backup of your data if you are not sure ! You should remove the SD card before you reset your phone so that the data on the SD card is not lost !


Source : http://varunverma.org/tech/android/hard-reset-your-samsung-galaxy-5/#more-386

10 things you can do when Windows XP won't boot

• Email
• Print
• Add to Favorites
• Del.icio.us
• Digg
• Facebook
• Google Buzz

• Hacker News
• LinkedIn
• Reddit
• StumbleUpon
• Technorati
• Twitter

When your computer hardware appears to power up okay, but the Windows XP operating system won't boot properly, you have to begin a troubleshooting expedition that includes getting into the operating system, determining the problem, and then fixing it. To help you get started on this expedition, here are 10 things you can do when Windows XP won't boot.

#1: Use a Windows startup disk

One of the first things you should reach for when troubleshooting a Windows XP boot problem is a Windows startup disk. This floppy disk can come in handy if the problem is being caused when either the startup record for the active partition or the files that the operating system uses to start Windows have become corrupted.
To create a Windows startup disk, insert a floppy disk into the drive of a similarly configured, working Windows XP system, launch My Computer, right-click the floppy disk icon, and select the Format command from the context menu. When you see the Format dialog box, leave all the default settings as they are and click the Start button. Once the format operation is complete, close the Format dialog box to return to My Computer, double-click the drive C icon to access the root directory, and copy the following three files to the floppy disk:

• Boot.ini
• NTLDR
• Ntdetect.com

After you create the Windows startup disk, insert it into the floppy drive on the afflicted system and press [Ctrl][Alt][Delete] to reboot the computer. When you boot from the Windows startup disk, the computer will bypass the active partition and boot files on the hard disk and attempt to start Windows XP normally.

#2: Use Last Known Good Configuration

You can also try to boot the operating system with the Last Known Good Configuration feature. This feature will allow you to undo any changes that caused problems in the CurrentControlSet registry key, which defines hardware and driver settings. The Last Known Good Configuration feature replaces the contents of the CurrentControlSet registry key with a backup copy that was last used to successfully start up the operating system.
To use the Last Known Good Configuration feature, first restart the computer by pressing [Ctrl][Alt][Delete]. When you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options menu. Select the Last Known Good Configuration item from the menu and press [Enter].
Keep in mind that you get only one shot with the Last Known Good Configuration feature. In other words, if it fails to revive your Windows XP on the first attempt, the backup copy is also corrupt.

#3: Use System Restore

Another tool that might be helpful when Windows XP won't boot is System Restore. System Restore runs in the background as a service and continually monitors system-critical components for changes. When it detects an impending change, System Restore immediately makes backup copies, called restore points, of these critical components before the change occurs. In addition, System Restore is configured by default to create restore points every 24 hours.
To use System Restore, first restart the computer by pressing [Ctrl][Alt][Delete]. When you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options menu. Now, select the Safe Mode item from the menu and press [Enter].
Once Windows XP boots into Safe mode, click the Start button, access the All Programs | Accessories | System Tools menu, and select System Restore. Because you're running in Safe mode, the only option on the opening screen of the System Restore wizard is Restore My Computer To An Earlier Time, and it's selected by default, so just click Next. Then, follow along with the wizard to select a restore point and begin the restoration procedure.

#4: Use Recovery Console

When a Windows XP boot problem is severe, you'll need to use a more drastic approach. The Windows XP CD is bootable and will provide you with access to a tool called Recovery Console.
To boot from the Windows XP CD, insert it into the CD-ROM drive on the problem system and press [Ctrl][Alt][Delete] to reboot the computer. Once the system begins booting from the CD, simply follow the prompts that will allow the loading of the basic files needed to run Setup. When you see the Welcome To Setup screen, shown in Figure A, press R to start the Recovery Console.

Figure A

You'll then see a Recovery Console menu, like the one shown in Figure B. It displays the folder containing the operating system's files and prompts you to choose the operating system you want to log on to. Just press the menu number on the keyboard, and you'll be prompted to enter the Administrator's password. You'll then find yourself at the main Recovery Console prompt.

Figure B

#5: Fix a corrupt Boot.ini

As the Windows XP operating system begins to load, the Ntldr program refers to the Boot.ini file to determine where the operating system files reside and which options to enable as the operating system continues to load. So if there's a problem rooted in the Boot.ini file, it can render Windows XP incapable of booting correctly.
If you suspect that Windows XP won't boot because Boot.ini has been corrupted, you can use the special Recovery Console version of the Bootcfg tool to fix it. Of course, you must first boot the system with the Windows XP CD and access the Recovery Console as described in #4.
To use the Bootcfg tool, from the Recovery Console command prompt, type
Bootcfg /parameter
Where /parameter is one of these required parameters:

• /Add--Scans the disk for all Windows installations and allows you to add any new ones to the Boot.ini file.
• /Scan--Scans the disk for all Windows installations.
• /List--Lists each entry in the Boot.ini file.
• /Default--Sets the default operating system as the main boot entry.
• /Rebuild--Completely re-creates the Boot.ini file. The user must confirm each step.
• /Redirect--Allows the boot operation to be redirected to a specific port when using the Headless Administration feature. The Redirect parameter takes two parameters of its own, [Port Baudrate ] | [UseBiosSettings].
• /Disableredirect--Disables the redirection.

#6: Fix a corrupt partition boot sector

The partition boot sector is a small section of the hard disk partition that contains information about the operating system's file system (NTFS or FAT32), as well as a very small machine language program that is crucial in assisting the operating system as it loads.
If you suspect that Windows XP won't boot because the partition boot sector has been corrupted, you can use a special Recovery Console tool called Fixboot to fix it. Start by booting the system with the Windows XP CD and accessing the Recovery Console as described in #4.
To use the Fixboot tool, from the Recovery Console command prompt, type
Fixboot [drive]:
Where [drive] is the letter of the drive to which you want to write a new partition boot sector.

#7: Fix a corrupt master boot record

The master boot record occupies the first sector on the hard disk and is responsible for initiating the Windows boot procedure. The master boot record contains the partition table for the disk as well as a small program called the master boot code, which is responsible for locating the active, or bootable, partition, in the partition table. Once this occurs, the partition boot sector takes over and begins loading Windows. If the master boot record is corrupt, the partition boot sector can't do its job and Windows won't boot.
If you suspect Windows XP won't boot because the master boot record has been corrupted, you can use the Recovery Console tool Fixmbr to fix it. First, boot the system with the Windows XP CD and access the Recovery Console as described in #4.
To use the Fixmbr tool, from the Recovery Console command prompt, type
Fixmbr [device_name]
Where [device_name] is the device pathname of the drive to which you want to write a new master boot record. For example, the device pathname format for a standard bootable drive C configuration would look like this:
\Device\HardDisk0

#8: Disable automatic restart

When Windows XP encounters a fatal error, the default setting for handling such an error is to automatically reboot the system. If the error occurs while Windows XP is booting, the operating system will become stuck in a reboot cycle--rebooting over and over instead of starting up normally. In that case, you'll need to disable the option for automatically restarting on system failure.
When Windows XP begins to boot up and you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options Menu. Then, select the Disable The Automatic Restart On System Failure item and press [Enter]. Now, Windows XP will hang up when it encounters the error and with any luck, it will display a stop message you can use to diagnose the problem.

#9: Restore from a backup

If you can't seem to repair a Windows XP system that won't boot and you have a recent backup, you can restore the system from the backup media. The method you use to restore the system will depend on what backup utility you used, so you'll need to follow the utility's instructions on how to perform a restore operation.

#10: Perform an in-place upgrade

If you can't repair a Windows XP system that won't boot and you don't have a recent backup, you can perform an in-place upgrade. Doing so reinstalls the operating system into the same folder, just as if you were upgrading from one version of Windows to another. An in-place upgrade will usually solve most, if not all, Windows boot problems.
Performing a Windows XP in-place upgrade is pretty straightforward. To begin, insert the Windows XP CD into the drive, restart your system, and boot from the CD. Once the initial preparation is complete, you'll see the Windows XP Setup screen (shown earlier in Figure A). Press [Enter] to launch the Windows XP Setup procedure. In a moment, you'll see the License Agreement page and will need to press [F8] to acknowledge that you agree. Setup will then search the hard disk looking for a previous installation of Windows XP. When it finds the previous installation, you'll see a second Windows XP Setup screen, as shown in Figure C.

Figure C

This screen will prompt you to press R to repair the selected installation or to press [Esc] to install a fresh copy of Windows XP. In this case, initiating a repair operation is synonymous with performing an in-place upgrade, so you'll need to press R. When you do so, Setup will examine the disk drives in the system. It will then begin performing the in-place upgrade.
Keep in mind that after you perform an in-place upgrade or repair installation, you must reinstall all updates to Windows.

Windows Server 2003 Standard R2 Activation crack.

1. Click on Start button.
2. Click on Run.
3. Type regedit into the Run text box and press Enter.
4. Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents

5. Note: From this step onward, the cracking process must be performed as quickly as possible, as it hacks activation stuff and Windows may change back the setting if there is a delay of more than few seconds.

Locate a string value named OOBETimer.
6. Right-click on OOBETimer, and click on Modify.
7. Change the value to FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD.

Activation OOBETimer
8. Click on OK.
9. Right-click on WPAEvents and select Permissions?.
10. Click on Advanced button.
11. Uncheck the check box for Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.
12. Click on Apply.
13. When prompted, click COPY.
14. From there, highlight the SYSTEM line, and click Edit.
15. Choose the Deny option to ban all users from accessing and editing the key.
16. Click on OK.
17. Reboot the computer.

After the hack, Windows Home Server should run completely as a free copy, with users able to access Windows Update to get latest hotfixes and patches. The crack does not require BIOS mod.

To verify that the activation crack works after restarting the system, go to Start -> All Programs -> Activate Windows. The dialog should say Windows is already activated. Alternatively, go to Start -> Run and type oobe/msoobe /a.

Note: Some users reported that the method does not actually remove the activation grace period, even though it makes the system activated.

Problems Installing Windows on GPT Hard Disks

Computers with Extensible Firmware Interface (EFI) use GUID Partition Table (GPT) as the standard hard disk partitioning system. Intel proposes it as the replacement for the PC BIOS that uses Master Boot Record (MBR).In GPT partitioned disks, data that is important to platform operation is placed in partitions and not in hidden or unpartitioned sectors as done in MBR partitioned disks.
Due to this and similar other factors, you sometimes observe issues, especially while installing a Windows operating system. To solve such issues, you might need to delete all hard disk partitions and opt for suitable partitioning scheme. This deletes all data and thus to restore information, you require using your recent data backup that should be complete and valid to restore data. However, if data backup is not updated, is corrupt or absent, you can use Data Recovery applications to scan and recover your data.
As a practical instance, when you attempt to install Windows Server 2003, a x64-based Windows Server 2003 version or Windows XP, you might receive the below error message:
"Setup cannot install to the selected partition. You can only install to GPT disks on IA-64 machines and MBR disks on X-86 machines. You can only upgrade installations on GPT disks on IA-64 machines and MBR disks on X-86 machines. To go back to the previous screen press ENTER."

Cause

This error message occurs if these both conditions are true:
An operating system is already installed on hard drive or it had an operating system, which has now been removed.
Hard disk is GPT formatted
You fail to install required operating systems on GPT hard drives because of following reasons:
On GPT hard drives, you can only set up Windows Server 2003 on systems that are Itanium-based.
You can't set up Windows x64 and Windows 32-bit operating systems on GPT based hard drives.

Solution

You need to convert your GPT hard disk to a MBR drive. You can use Disk Management or Diskpart command for it, if an operating system is already installed. You can also delete all existing drive partitions while running Setup program and opting for the option to convert the partitioning scheme. In Windows Server 2003-based systems, it must have Windows Server 2003 Service Pack 1 installed. After this, you can restore lost information from backup. If backup produces errors or has not been taken, you can use Recovery applications.
Stellar Phoenix Windows Data Recovery is a complete and robust Data Recovery software. It supports FAT16, FAT32, VFAT, NTFS and NTFS5 file system based drives and volumes. It is a read-only Hard Drive Recovery application. It is compatible with Windows 7 ( currently in RC1), Vista, Server 2003, XP and 2000).

Simpson a student of Mass Communication doing research on hard drive recovery software. He is also a freelancer for image recovery software.

Article Source: http://EzineArticles.com/?expert=Simpson_Raid

How to Set a Static IP address in Ubuntu 8.10

There seems to be a known bug with the Gnome Network Manager included with the Ubuntu 8.10 release that resets any static ip address settings that are set manually when the system is rebooted reverting back to a DHCP setup. These steps will remove the Gnome Network Manager and help you manually setup the required files for your static network configuration.

Solution 1

Step 1 – Remove the Gnome Network Manager: You need to complete this step first because if left installed this application will overwrite any changes you make to your configuration when the system is rebooted. This is apparently where the bug is located.
To remove the Gnome Network Manager issue the following command in the terminal:

sudo update-rc.d -f NetworkManager remove

This will disable and remove the Gnome Network Manager application. Now you will have to edit your configuration manually.

Restart your System

Step 2 – Manual configuration of your network interface: In this step you will manually configure your network interface by editing the following two files using your preferred text editor(nano gedit vi). For the purpose of this example I am using the nano editor.

Step 2.1 – Manually configure your network interface file: You can edit the appropriate file by entering the following command into the terminal:

sudo nano /etc/network/interfaces

Once your prefered editor opens the file you want to enter the following information (changing your addresses where necessary):

auto lo eth0
iface lo inet loopback
iface eth0 inet static
address xxx.xxx.xxx.xxx(enter your ip here)
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx(enter gateway ip here)

Be sure to save your changes.

Step 2.2 – Manually configure your dns configuration file: You can edit the appropriate file by entering the following command into the terminal:

sudo nano /etc/resolv.conf

Once your preferred editor opens the file you want to enter the following information (changing your addresses where necessary):

# Generated by NetworkManager
nameserver xxx.xxx.xxx.xxx(enter your dns server ip)
nameserver xxx.xxx.xxx.xxx(enter your alt dns server ip)

Be sure to save your changes.

Step 2.3 – Manually restart your network interface with the new settings: Enter the following command in the terminal:

sudo /etc/init.d/networking restart

This should return a result that looks like the following:

*Reconfiguring network interfaces… [OK]

At this point in your terminal you should be able to run the ifconfig command and the results should reflect your new settings. If the addressing is correct you should have full network access, even after a system restart.

Haven’t tried reinstalling the Network Manger after doing these steps to see if it still works.

Solution 2

Install Wicd if you need both wired and wireless connection

Solution 3

Also, it is said that adding a new config in networkmanager (instead of editing the system default ‘Auto eth0′ stuff) and assign the right MAC address (and the static ip) will fix it, every thing’s fine even after reboot, and you can still use that gnome-networkmanager.

Check this simple guide

Credit Goes here

Uninstalling Windows Movie Maker in Windows XP

Although Microsoft doesn't allow you to uninstall Windows Movie Maker officially, there is a workaround which will let you remove Windows Movie Maker and all of its associated files. Want to free up some space by deleting an application that you might never use? Then check out this article!

Windows Movie Maker

If you've never edited your own movies, or if you have a better-equipped video editor, you might want to get rid of Windows Movie Maker. Sadly, with Microsoft's System-File-Protection mechanism, you cannot simply delete the relevant files from the Program Files folder. Windows will restore the files within a few minutes and Windows Movie Maker will keep working. If you are really stubborn about removing Windows Movie Maker from Windows XP

, there is a workaround which will allow you to delete all the concerned files and free-up some space which would otherwise be taken up by Windows Movie Maker.

Uninstallation

Removing Windows Movie Maker requires a workaround since Windows considers it an essential part of Windows. Here is the procedure to delete Windows Movie Maker completely from Windows.

Restart Windows XP in Safe Mode. To do this, start tapping on the F8 key as soon as your computer boots, before the Windows XP loading screen. In the menu that is then shown, select Safe Mode.
Once Safe Mode starts, Click on Start Menu, then go to Run and type "cmd". This will open up a command prompt where you will be entering a few commands:

Type these commands one-by-one and you will completely remove Windows Movie Maker.

• del "c:\system32\dllcache\*wmm*.dll"
• del "c:\system32\dllcache\moviemk.exe"
• del "c:\Program Files\Movie Maker\*.*"
• rmdir /s "c:\Program Files\Movie Maker"

Make sure to include the double quotes around the path of the files, and replace c: with whichever drive Windows is installed on. Once done, just restart your computer. You should have successfully removed Windows Movie Maker from your Windows installation.

Final Words

Removing Windows Movie Maker, while possible, can be dangerous if you do not take care while typing the above commands and delete anything important by mistake. Remember that the system32 directory contains the core of Windows system files and any important files being deleted will cause big problems. If in doubt, make sure to backup everything before you start with this procedure.

Read more: http://www.brighthub.com/computing/windows-platform/articles/45977.aspx#ixzz0tYv3BRQv

RPM COMMAND

RPM command usage