Low-level formatting is the process of outlining the positions of the tracks and sectors on the hard disk, and writing the control structures that define where the tracks and sectors are. This is often called a "true" formatting operation, because it really creates the physical format that defines where the data is stored on the disk. The first time that a low-level format ("LLF") is performed on a hard disk, the disk's platters start out empty. That's the last time the platters will be empty for the life of the drive. If an LLF is done on a disk with data on it already, the data is permanently erased (save heroic data recovery measures which are sometimes possible)

• Supported interfaces: S-ATA (SATA), IDE (E-IDE), SCSI, SAS, USB, FIREWIRE.
• Big drives (LBA-48) are supported.
• Supported Manufacturers: Maxtor, Hitachi, Seagate, Samsung, Toshiba, Fujitsu, IBM, Quantum, Western Digital, and almost any other not listed here.
• The program also supports low-level formatting of FLASH cards (SD, MMC, MemoryStick and CompactFlash) using a card-reader. 

Download :-
 http://4eaf9d70.filesonthe.net
 http://www.mediafire.com/?mtktzzjjjz4

Kodu is a new visual programming language made specifically for creating games. It's designed to be accessible for children and enjoyable for anyone. The visual nature of the language allows for rapid design iteration using only an Xbox game controller for input (mouse/keyboard input is also supported).
"We're experimenting with new approach to making Kodu feel more responsive on lower end machines. If you've Kodu configured for Shader Model 2 and Effects turned off then this feature will be activated when your frame rate gets low. The only indication is that "frame per second" text (if turned on in configuration) will turn red. What we're doing is updating UI elements more frequently than we're updating the world. Hopefully this'll make UI feel more responsive even though the overall frame rate is still the same," revealed

SalvationDATA HD Doctor Suite a professional diagnosis and repair tool provides an integrated hardware-software solution to firmware failures. HD Doctor Suite is a Forensic data recovery tool from wrongly detected or undetected hard drives due to firmware corruption. Highlights of HD Doctor Suite: 1, Comprehensive diagnosis towards the malfunctioning hard drives to find out the best way of restoring it for further investigation; 2, Unlock password protected hard drives and access normally to evidence files; 3, Restoring malfunctioning hard drives by repairing bad sectors and corrupted firmware modules; 4, Handle different computer forensic cases in the same time, Seagate, Maxtor, Western Digital, Hitachi/IBM, Samsung, Toshiba, Fujitsu, are supported. Note: HD Doctor Suite requires the computer forensic analysts to have more experience and computer related knowledge. Application: Bad sector, Firmware / ROM Damage, NVRAM Repair/R/W, SMART Reset, Service Information Defect, Password Clear, Selfscan, Defective List Operation, Sector View, Head Depop, Motor Operation, HDD Parameter Modification, etc.

PC-3000 is specifically designed to work with failed / unrecognized hard disk drives. Because PC-3000 works through its specially created PCI card, the PC-3000 system allows the data recovery professional read and write access to an HDD's ROM and system area. (HDD's firmware is located on negative cylinders.) This means that technicians will be able to completely view and repair all of the HDD firmware modules including: Microcode Overlays, HDD Configuration Tables, Defects Tables, SMART Attributes, Security Subsystem, and Adaptive. This ability dramatically improves data recovery success rates.
Logical File recovery - has automated scripts for correcting file system structure corruptions

Raw file recovery independent of disk Operating System (sector by sector search for header files)

Ability to ignore ECC error codes and access data from "Bad Sectors" (Accomplished by working through the PC-3000 hardware.)

Sometimes you are not able to open drives on your hard disk by you double clicking on the drives icons or right click on the drive-->explore in My computer in windows xp

Normally when a virus infects a windows system which causes a drive opening problem, it automatically creates a file named autorun.inf in the root directory of each drive.
This autorun.inf file is a read only ,hidden and a system file and the folder option is also disabled by the virus. This is deliberately done by the virus in order to protect itself. autorun.inf initiates all the activities that the virus performs when you try to open any drive.

You have to just delete this file and restart your system to correct this problem.
Follow the set of commands below to show and delete the autorun.inf

1. Go to Start-->Run and type cmd and press Enter.
or
Go to Start-->All Programs-->Accessories-->command prompt.
( This will open a command prompt window. )

On the command prompt window type the following steps.
2. type cd\
3. type attrib -r -h -s autorun.inf
4. type del autorun.inf
5. now type d: and press Enter for d: drive partition. Now repeat steps 3 and 4. Similarly repeat step 5 for all your hard disk partition.

Restart your system and your trouble will be fixed.;)

When you start to shut down Windows XP, it has to quit, or “kill,” any live applications or processes that are currently running. So close all applications first. However, some applications and processes are always running in the background. You can reduce the amount of time that Windows XP waits for those applications and processes to close before Windows XP kills them. Edit three different Registry settings to change this:
1. Open the Registry Editor.
2. Navigate to HKEY_CURRENT_USER\Control Panel\Desktop. Select WaitToKillAppTimeout and set the value to 1000.
3. Select the HungAppTimeout value and set it to 1000 as well.
4. Navigate to HKEY_USERS\.DEFAULT\Control Panel\Desktop. Set the WaitToKillAppTimeout and set the value to 1000. Select the HungAppTimeout \newline value and set it to 1000 as well.
5. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l. Select the WaitToKillServiceTimeout value and set it to 1000.
6. Close the Registry Editor.