Welcome, Guest. Please login or register.
Did you miss your activation email?
May 22, 2013, 11:42:35 AM
Home Help Search Login Register
News: When requesting a refund, do NOT post order ID in forum!

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  General Data Recovery (Moderators: Tom, Joep)
| | |-+  cant clone over bad sectors....need Help Please.
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: cant clone over bad sectors....need Help Please.  (Read 2866 times)
DukeB
member

Posts: 11


« on: March 27, 2012, 04:05:00 PM »

Have a lap top. It said it's drive was going bad, plus random BSODs. So I tried to clone it. I used a Star tech 2 bay external dock (usb 3) off of a desktop computer. Tried paragon, and acronis to clone the lap top drive to another empty laptop drive in the docking station. Both pieces of cloning software stop......and wont run any further. THey get to the part where it says having problems reading something snapshot...." and I hit ignore all, and then nothing..... I tried the disc scan an repair in windows, and tried the cloning again....but still it wouldn't do it. Is their anyway to repair the disc or somehting so I can atleast get most of it over onto a usable drive?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1146


WWW
« Reply #1 on: March 27, 2012, 04:20:05 PM »

If indeed the original drive is going bad (which is something you should verify: http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm) you can't use tools like the disk imagers that you've used so far. You'll need a cloning tool, like for instance DiskPatch. This bit will explain a bit more, in the form of a walkthrough:
http://www.diydatarecovery.nl/dp_manual/guide_clone.htm
and this bit (from the manual) explains things in more detail:
http://www.diydatarecovery.nl/dp_manual/clone.htm
Logged

DukeB
member

Posts: 11


« Reply #2 on: March 27, 2012, 05:01:59 PM »

WIn7 x64 is saying H:\SMARTCHK.EXE is not compatible and is asking if I need "a x86 (32bit) or x64 (64 bit) version of the program. Also I tried booting from the USB....but that didn't work either (boot from "usb ZIP" does nothing and rebooting from "USB fdd" brings up windows in its entirety.....on a red screen..  I formatted the usb stick in FAT not FAT32 like it said to.....it's just blinking.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1146


WWW
« Reply #3 on: March 27, 2012, 06:07:32 PM »

You installed DiskPatch and followed the included instructions (from the start menu select "create bootable USB key for DiskPatch") and it didn't work? That's very unlikely. From your description it sounds like you are doing it wrong. You need to either create a bootable USB key and start the PC from that, or create the bootable CD and start the PC from that. The manual clearly explains, in the first 3 pages, which is not that much to read through.

If you want to clone the disk you'll need to create that bootable USB key or CD to get started. You should also check to see if the target disk (in the USB enclosure) can be seen by DiskPatch; usually it's preferable to connect all disks directly, but if you have no way to do that then USB might do, if it works.
Logged

DukeB
member

Posts: 11


« Reply #4 on: March 28, 2012, 04:02:54 PM »

I tried to clone it but it freezes up. The bad disc will still boot, I found this out by accident moving back and forth from boot devices in the bios. I disabled error check (set 0 instead of 32)...and still it freezes up. I didn't start a log or anything, I wanted to clone first, and fix new disc.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1158


WWW
« Reply #5 on: March 28, 2012, 07:18:18 PM »

Quote
I disabled error check (set 0 instead of 32)...and still it freezes up.

How long did you give it to recover? Even with retries set to zero it may take a while before DiskPatch responds. DiskPatch not responding does not mean it froze: DiskPatch runs in a single task environment which means as soon as it requests a sector to be read it passes control over the PC to the system BIOS. It can only respond as soon as the BIOS released control over the system. The BIOS in turn is waiting for the disk. The disk recovering from a single error can take a while. even if DiskPatch requests one sector only, the disk may attempt to read multiple sectors and each read error will add up to recovery time. Experience learns you need to be patient, let it run. Not to hit keys all the time and assume it's hanging if it does not respond straight away or even after a minute.

Quote
I disabled error check (set 0 instead of 32)...

Try increasing skipsize as well, try 4096 for example so it gets quicker through those bad areas.
Logged

--
Kind regards,
Joep
DukeB
member

Posts: 11


« Reply #6 on: March 28, 2012, 10:21:24 PM »

increased skip to 4096.....and It's been on sector 1650688 for an hour now on first pass.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1158


WWW
« Reply #7 on: March 29, 2012, 09:19:46 AM »

Well, an hour is too long. I meant you should allow it some time and not immediately switch it off if DiskPatch doesn't respond within a few seconds. Try double skipsize or start cloning somewhere further on the disk. With disks like these you need to experiment and keep your fingers crossed. If the data is mission critical you need to consider a data recovery lab at this point.

If the latter is not an option hook up the disk to a PC you can run Windows on and see if iRecover can image the disk.

It may also help if you post a disk health report http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm

EDIT: Would you be willing to try a beta where we improved cloning? If so then email us at support@diydatarecovery.nl
Logged

--
Kind regards,
Joep
DukeB
member

Posts: 11


« Reply #8 on: March 29, 2012, 02:59:37 PM »


.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 3.5.300
.../000:01/LOG> (C) 2000-2009 DIY DataRecovery
.../000:01/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 35Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 03-29-2012
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Write with verify supported
.../000:01/13H> Drive Interface Info: USB
.../000:01/13H> Disk 128 X13H data : 487/255/63 7833600/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 16383/16/63 625142448/512
.../000:01/13H> Disk found at 130
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 16383/16/63 250061423/512
.../000:01/13H> Disk found at 131
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 131 X13H data : 16383/16/63 1250263728/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
.../000:01/FDL> Disk found at 130
.../000:01/FDL> Disk found at 131
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | ...7833600 | 255 | 63 | ..3 | BIOS
129 | .625142448 | 255 | 63 | 298 | BIOS
130 | .250061423 | 255 | 63 | 119 | BIOS
131 | 1250263728 | 255 | 63 | 596 | BIOS
.../000:01/IAS> AdmiSector found on disk 0 (128)
.../000:01/IAS> AdmiSector found on disk 1 (129)
.../000:01/IAS> AdmiSector found on disk 2 (130)
.../000:01/IAS> AdmiSector found on disk 3 (131)
.../000:02/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:02/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:03/EXE> Read/Write pattern test for disk 2 (130) successful
.../000:03/EXE> Read/Write pattern test for disk 3 (131) successful
.../000:03/WAS> AdmiSectors in use : 0+ 1+ 2+ 3+
.../000:03/KEY> DEMO/1
.../000:03/PFC> PQstuff signature not detected on disk 0 (128)
.../000:03/PFC> PQstuff signature not detected on disk 1 (129)
.../000:03/PFC> PQstuff signature not detected on disk 2 (130)
.../000:03/PFC> PQstuff signature not detected on disk 3 (131)
.../000:03/PFC> UDMA driver not loaded
.../000:04/PFC> Disk health not checked
.../000:05/PFC> Partition State backup not found on disk 0 (128)
.../000:05/PFC> Partition State backup not found on disk 1 (129)
.../000:05/PFC> Partition State backup not found on disk 2 (130)
.../000:05/PFC> Partition State backup not found on disk 3 (131)
.../000:05/PFC> No Repair date found on disk 0 (128)
.../000:05/PFC> No Repair date found on disk 1 (129)
.../000:05/PFC> No Repair date found on disk 2 (130)
.../000:05/PFC> No Repair date found on disk 3 (131)
.../000:20/CSD> Start CheckDisk for disk 1 (129)
.../000:20/CSD> CheckDisk complete, ReadErrors 0
.../000:20/USD> Disk 1 (129) selected
.../000:20/GSC> No geo change detected for disk 1 (129)
.../000:20/WAS> AdmiSectors in use : 0+ 1+ 2+ 3+
129/000:20/USD> MBR for disk 1 (129)
129/000:20/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00  |  3м.|ؾ.|.
016   06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00  |  ...Ph....
032   BD BE 07 80 7E 00 00 7C 0B 0F 85 0E 01 83 C5 10  |  .~..|.....
048   E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00  |  .V.UF..F..
064   B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09  |  AU.]r.Uu.
080   F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74  |  ..t.F.f`~..t
096   26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00  |  &fh....f.v.h..h.
112   7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13  |  |h..h..BV..
128   9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00  |  .....|V.
144   8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1C FE  |  v.N.n..fas.
160   4E 11 75 0C 80 7E 00 80 0F 84 8A 00 B2 80 EB 84  |  N.u.~...
176   55 32 E4 8A 56 00 CD 13 5D EB 9E 81 3E FE 7D 55  |  U2V..]랁>}U
192   AA 75 6E FF 76 00 E8 8D 00 75 17 FA B0 D1 E6 64  |  un.v..u.d
208   E8 83 00 B0 DF E6 60 E8 7C 00 B0 FF E6 64 E8 75  |  .`|..du
224   00 FB B8 00 BB CD 1A 66 23 C0 75 3B 66 81 FB 54  |  ...f#u;fT
240   43 50 41 75 32 81 F9 02 01 72 2C 66 68 07 BB 00  |  CPAu2..r,fh..
256   00 66 68 00 02 00 00 66 68 08 00 00 00 66 53 66  |  .fh....fh....fSf
272   53 66 55 66 68 00 00 00 00 66 68 00 7C 00 00 66  |  SfUfh....fh.|..f
288   61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00 00 CD  |  ah....Z2.|..
304   18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07 32 E4  |  . .. .. .2
320   05 00 07 8B F0 AC 3C 00 74 09 BB 07 00 B4 0E CD  |  ...<.t....
336   10 EB F2 F4 EB FD 2B C9 E4 64 EB 00 24 02 E0 F8  |  .+d.$.
352   24 02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69  |  $.Invalid parti
368   74 69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72  |  tion table.Error
384   20 6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69  |   loading operati
400   6E 67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E  |  ng system.Missin
416   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
432   65 6D 00 00 00 63 7B 9A 0D AF 36 50 00 00 80 20  |  em...c{.6P..
448   21 00 07 DF 13 0C 00 08 00 00 00 20 03 00 00 DF  |  !......... ...
464   14 0C 07 FE FF FF 00 28 03 00 00 B8 3F 25 00 00  |  ......(...?%..
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
129/000:20/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:20/VEC> Listing current partitions on disk:
129/000:20/VEC>     NTFS (P)  System Rese        2048      204800       (0 Gb)
129/000:20/VEC>     NTFS (P)    (no name)      206848   624932864     (298 Gb)
129/000:20/VEC> Partition Table info for sector 0 (0 0 1)
129/000:20/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 .128 | ..07 | ....0..32..33 | ...12.223..19 | ......2048 | ....204800
..2 ...0 | ..07 | ...12.223..20 | .1023.254..63 | ....206848 | .624932864
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:20/VEC> 55AA sig Ok
129/000:20/LOG> Boot sector dump requested at 2048 (0 32 33)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 204799
........MFT Location (dec): 8533
.MFT Mirror Location (dec): 2
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 6C24F5A624F57404
........Volume Label (txt): System Rese
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:20/VEC> BS and BBS equal
129/000:20/LOG> Boot sector dump requested at 206848 (12 223 20)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 206848
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 624932863
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 2
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 1A1CF7201CF6F59B
........Volume Label (txt): (no name)
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:20/VEC> BS and BBS equal
129/000:20/VEC> Verify EPBR Chain completed
129/000:20/USD> Select disk completed
129/000:25/SCN> DiskScan requested, ScanType is 3
129/000:25/SCN> from 0 (0 0 1) to 625142447 (38913 80 63), 625142448 sectors
129/000:25/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
129/000:25/SCN> Next QuickScan location at 206848 (12 223 20)
129/000:26/SCN> Next QuickScan location at 625139712 (38913 37 37)
129/000:26/SCN> Next QuickScan location at 0 (0 0 1)
129/000:27/SCN> QuickScan finished
129/000:27/SCN> Starting SmartScan (vista) at 0 (0 0 1)
129/000:27/RDS> Read past EOD intercept for disk 129 at 4294967295 (267349 89 4)
129/000:58/RDS> ReadError for disk 129 at 15292415 (951 231 48), C:1, T:BBh
129/001:04/RDS> ReadError for disk 129 at 15292416 (951 231 49), C:2, T:BBh
129/001:04/RDS> ReadSector success (after error) at 15292416 (951 231 49), tries 1
129/001:07/RDS> ReadError for disk 129 at 15417343 (959 174 47), C:2, T:BBh
129/001:14/RDS> ReadError for disk 129 at 15417344 (959 174 48), C:3, T:BBh
129/001:21/RDS> ReadError for disk 129 at 15417350 (959 174 54), C:4, T:BBh
129/001:27/RDS> ReadError for disk 129 at 15419391 (959 207 16), C:5, T:BBh
129/001:27/RDS> ReadSector success (after error) at 15419391 (959 207 16), tries 1
129/001:44/RDS> ReadError for disk 129 at 17692671 (1101 81 4), C:5, T:BBh
129/001:50/RDS> ReadError for disk 129 at 17692672 (1101 81 5), C:6, T:BBh
129/001:50/RDS> ReadSector success (after error) at 17692672 (1101 81 5), tries 1
129/001:53/RDS> ReadError for disk 129 at 17709056 (1102 86 9), C:6, T:BBh
129/001:59/RDS> ReadError for disk 129 at 17709062 (1102 86 15), C:7, T:BBh
129/001:59/RDS> ReadSector success (after error) at 17709062 (1102 86 15), tries 1
129/002:06/RDS> ReadError for disk 129 at 18372607 (1143 163 44), C:7, T:BBh
129/002:12/RDS> ReadError for disk 129 at 18372608 (1143 163 45), C:8, T:BBh
129/002:19/RDS> ReadError for disk 129 at 18372614 (1143 163 51), C:9, T:BBh
129/002:19/RDS> ReadSector success (after error) at 18372614 (1143 163 51), tries 2
129/002:27/RDS> ReadError for disk 129 at 19152896 (1192 54 15), C:9, T:BBh
129/002:33/RDS> ReadError for disk 129 at 19152902 (1192 54 21), C:10, T:BBh
129/002:33/RDS> ReadSector success (after error) at 19152902 (1192 54 21), tries 1
129/002:45/RDS> ReadError for disk 129 at 20701183 (1288 150 14), C:10, T:BBh
129/002:52/RDS> ReadError for disk 129 at 20701184 (1288 150 15), C:11, T:BBh
129/002:52/RDS> ReadSector success (after error) at 20701184 (1288 150 15), tries 1
129/002:55/RDS> ReadError for disk 129 at 20740095 (1291 2 55), C:11, T:BBh
129/003:01/RDS> ReadError for disk 129 at 20740096 (1291 2 56), C:12, T:BBh
129/003:08/RDS> ReadError for disk 129 at 20740102 (1291 2 62), C:13, T:BBh
129/003:15/RDS> ReadError for disk 129 at 20742143 (1291 35 24), C:14, T:BBh
129/003:15/RDS> ReadSector success (after error) at 20742143 (1291 35 24), tries 1
129/003:21/SCN> DiskScan aborted at JumpSector 0 (0 0 1)
129/003:26/EXE> Analysis aborted
129/003:26/LOG> RunTime: 003:26
129/003:26/LOG> ### CLOSE LOG ###
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1146


WWW
« Reply #9 on: March 29, 2012, 03:15:18 PM »

Not sure we asked for that log, we'd like to see this one:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm

New DiskPatch build is sent. After installing that over the current DiskPatch install you'll need to build a fresh boot disk. It just occurred to me you may be using a USB bootable disk so I'll send another mail that contains just the DP.EXE file, which you'll simply need to put on the USB disk (overwriting the current DP.EXE).
Logged

DukeB
member

Posts: 11


« Reply #10 on: March 29, 2012, 03:33:12 PM »

This is all that comes up for that one.....and thank you I am using a usb stick.

Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 1002
    Device ID . . . . . . . . . . . . . . . : 4391
    Device  . . . . . . . . . . . . . . . . : ATI
    Device Location . . . . . . . . . . . . : Bus 0, Device 17, Function 0
    Device Ports  . . . . . . . . . . . . . : FF00-FF07, FE00-FE03, FD00-FD07, FC00-FC03, FB00-FB0F

  Disk Controller 2
    Device Vendor . . . . . . . . . . . . . : 197B
    Device ID . . . . . . . . . . . . . . . : 2363
    Device Location . . . . . . . . . . . . : Bus 7, Device 0, Function 1
    Device Ports  . . . . . . . . . . . . . : 8F00-8F07, 8E00-8E03, 8D00-8D07, 8C00-8C03, 8B00-8B0F
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1146


WWW
« Reply #11 on: March 29, 2012, 03:41:27 PM »

Hmm, that's not a good sign.
Logged

DukeB
member

Posts: 11


« Reply #12 on: March 29, 2012, 03:44:26 PM »

Well it does still boot......it's a mess from there....but it boots. I don't suppose that means much.
Logged
DukeB
member

Posts: 11


« Reply #13 on: March 29, 2012, 03:49:24 PM »

Here's the thing.....it's a girlfreind's daughter's laptop. She has all of her college stuff on there. I explained that this 'is not my area', but was talked into it anyway. So far I bought a new drive, acronis, parasomething....and you were my last hope. Is there any way to figgure out where the 'college stuff' would be and somehow get that into a fresh install of win7?
Logged
DukeB
member

Posts: 11


« Reply #14 on: March 29, 2012, 04:42:24 PM »

Ok running beta......skipping at 16gigs. Ran up to .9% (the farthest it has gotten yet). WHen it froze before the little light at the top right of the screen would stay green, and do nothing. THis freeze up the red light at the farthest right is on. THat's new.
Logged
Pages: [1] 2 Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!