I had a 200G SATA hard driver with Win XP pro. With 3 partitions, 13G(main
WinXP)/70G/120G.

It is below as fdisk -l in linux.
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1549 12442311 7 HPFS/NTFS
/dev/sda2 1550 24792 186699397+ f W95 Ext'd (LBA)
/dev/sda5 1550 10201 69497158+ 7 HPFS/NTFS
/dev/sda6 10202 24792 117202176 7 HPFS/NTFS

It is the only hard driver and showed "no system file" in booting.

I tried to connect it in another computer with both SATA and IDE. (with two
IDE hard drivers with dual IO Win XP+Debian Linux). I cannot boot with my
original winXP but linux. In linux, I can mount sda1 and sda6. But when I
try sda5, it is very slow and shows failure finally after about 15 minutes.

"mount -t ntfs -o umask=222 /dev/sda5 /mnt/tempdrive/

mount: wrong fs type, bad option, bad superblock on /dev/sda5,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
"

But I have some important data on this partition. Is there any chance I can
get the data out? How to do it if I can. Thanks.

Depending on what type of files you're trying to recover and what type of failure the drive has, you might be able to use foremost to get things back.

I recently used it to recover 1500 photos and another 50 or so documents from my parents failed hard disk. Pretty sure I didn't get everything, but I got much better than nothing...

Also, if you search these forums, someone wrote a pretty good howto on foremost...

Thank you very much. I have installed it. But I do not quite understand how it runs. You do not need to specify the driver to search? I did not see any help on this parameters.

How to make this input *.dd file?

Well, all I did was foremost -v -T -i /dev/hda and it recovered all the builtin filetypes. You'll probably have to do a bit more work to get *.dd files (what are these anyway?).

Here's an article that might help you figure out how to get the headers and footers to put in the /etc/foremost.conf file. And here's the man page. Basically you need to find another dd file and use head and tail to see what characters mark the file length, then put those into the config file.