Welcome, Guest. Please login or register.
Did you miss your activation email?
June 19, 2019, 07:08:38 PM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  unreadable data drive
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: unreadable data drive  (Read 17878 times)
bob
member

Posts: 8


« on: June 19, 2008, 04:26:49 AM »

Hi
I have a PIV computer with 2 NTFS HD. One XP OS WD 150GB Raptor and one WD 80GB data drive that I can't no longer access. Some days ago CHKDSK ran right after a boot and now I can't read neither of the two installed partitions on this HD. Now after a boot CHKDSK tells the drive need to be checked but the action is aborted before it take place and I get the following message: "Corrupt Master File Table". Here is the log file:
Code:
.../000:03/LOG> ### LOG START ###
.../000:03/LOG> DISKPATCH 3.4.100
.../000:03/LOG> (C) 2000-2008 DIY DataRecovery
.../000:03/LOG> Contact info: HTTP://www.DIYDataRecovery.nl
.../000:03/LOG> MemFree: 77Kb
.../000:03/LOG> CommandLineParms: /sup
.../000:03/LOG> LogDate: 06-18-2008
.../000:03/CFG> FilePath="1/.\DPFILES\"
.../000:03/CFG> LogFilename="DP.LOG"
.../000:03/CFG> ReadRetries="32"
.../000:03/CFG> WriteRetries="32"
.../000:03/CFG> MaxReadErrors="32"
.../000:03/CFG> MaxWriteErrors="1"
.../000:03/CFG> ReadDelay="0"
.../000:03/CFG> VfyFixedBadSect="1"
.../000:03/CFG> CleanAfterDOD="1"
.../000:03/CFG> DiskReset="1"
.../000:03/CFG> SectorSkip="1024"
.../000:03/CFG> AutoSaveState="1"
.../000:03/CFG> DumpFoundSectors="0"
.../000:03/CFG> FixFats="1"
.../000:03/CFG> MaxFatScan="51200"
.../000:03/CFG> MaxDataColEntries="256"
.../000:03/CFG> IgnoreF8FF="0"
.../000:03/CFG> DownSizeExt="1"
.../000:03/CFG> ScanSignature="55AA"
.../000:03/CFG> Rebuild="00"
.../000:03/13H> Ext13H installed test requested
.../000:03/13H> Disk found at 128
.../000:03/13H> Ext13H version: EDD-3.0
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Support: Enhanced disk drive functions
.../000:03/13H> Drive Interface Info : ATA
.../000:03/13H> Disk 128 X13H data : 16383/16/63 156301488/512
.../000:03/13H> Ext13H tested ok
.../000:03/FDL> DiskList requested
.../000:03/FDL> Disk found at 128
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB
128 | .156301488 | 255 | 63 | .74
..0 | .........0 | ..0 | .0 | ..0
..0 | .........0 | ..0 | .0 | ..0
..0 | .........0 | ..0 | .0 | ..0
.../000:03/IAS> AdmiSector found on disk 0 (128)
.../000:03/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:03/WAS> AdmiSectors in use : 0+
.../000:03/KEY> DEMO/1
.../000:03/PFC> UDMA driver not loaded
.../000:03/PFC> PQstuff signature detected on disk 0 (128)
.../000:04/PFC> Partition State backup not found on disk 0 (128)
.../000:04/PFC> No Repair date found on disk 0 (128)
.../000:14/CSD> Start CheckDisk for disk 0 (128)
.../000:14/CSD> CheckDisk complete, ReadErrors 0
.../000:14/USD> Disk 0 (128) selected
.../000:14/GSC> No geo change detected for disk 0 (128)
.../000:14/WAS> AdmiSectors in use : 0+
.../000:14/GSC> Geo for disk 0 (128) saved as 0156301488255063
128/000:14/USD> MBR for disk 0 (128)
128/000:14/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C  |  3???.|?P.P.??.|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04  |  ?..PW??.????.?.
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5  |  8n.|.u.??.???.??
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B  |  ??.It.8,t? ?.?.?
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88  |  ??<.t??..?.?.???
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B  |  N.?F.s*?F.?~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83  |  ?~..t. ?.u?F..?
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB  |  F..?V..?!.s. ?.?
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0  |  ??>?}U?t.?~..t? 
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56  |  ?.??.W???..?V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC  |  .?.?.r#??$?????
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56  |  C?????.??B??9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C  |  .w#r.9F.s.?..?.|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A  |  ?N.?V.?.sQOtN2??
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD  |  V.?.???V.`??U?A?
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6??U?u0??.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A  |  j.j..v..v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B  |  .j.?B???.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61  |  2??V.?.??a??Inva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61  |  lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E  |  ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61  |  em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00  |  ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 2C 44 63 7C 9F 00 00 00 00 80 00  |  .....,Dc|?....?.
448   01 01 07 FE FF FF C1 3E 00 00 B5 D7 70 02 00 00  |  ...?..?>..??p...
464   C1 FF 0F FE FF FF 76 16 71 02 4B CE DF 06 00 00  |  ?..?..v.q.K??...
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?
###
128/000:16/VEC> Start Verify EPBR Chain for disk 0 (128)
128/000:16/VEC> Listing current partitions on disk:
128/000:16/VEC>     NTFS (P)         Syst       16065    40949685      (20 Gb)
128/000:16/VEC>     NTFS (L)         Data    40965813   115330572      (55 Gb)
128/000:16/VEC> Extended starts at 40965750 (2550 0 1)
128/000:16/VEC> Partition Table info for sector 0 (0 0 1)
128/000:16/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 | ....1...0...1 | .1023.254..63 | .....16065 | ..40949685
..2 ...0 | ..0F | .1023...0...1 | .1023.254..63 | ..40965750 | .115330635
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
128/000:16/VEC> 55AA sig Ok
128/000:16/VEC> Partition Table info for sector 40965750 (2550 0 1)
128/000:16/LOG> PartListDump requested at 40965750 (2550 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | .1023...1...1 | .1023.254..63 | ........63 | .115330572
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
128/000:17/VEC> 55AA sig Ok
128/000:17/LOG> Boot sector dump requested at 16065 (1 0 1)
### 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): 16065
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 40949680
........MFT Location (dec): 689701
.MFT Mirror Location (dec): 1106512
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): F8005FBD005F8214
........Volume Label (txt): Syst
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:17/VEC> BS and BBS equal
128/000:17/LOG> Boot sector dump requested at 40965813 (2550 1 1)
### 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): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 115330568
........MFT Location (dec): 4
.MFT Mirror Location (dec): 524288
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 11029D9301EA3469
........Volume Label (txt): Data
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:17/VEC> BS and BBS equal
128/000:17/VEC> Verify EPBR Chain completed
128/000:18/USD> Select disk completed
128/000:20/SCN> DiskScan requested, ScanType is 3
128/000:21/SCN> from 0 (0 0 1) to 156301487 (9729 80 63), 156301488 sectors
128/000:21/SCN> Starting QuickScan (pre-vista) at 63 (0 1 1)
128/000:21/SCN> Next QuickScan location at 40965744 (2549 254 58)
128/000:22/SCN> Next QuickScan location at 156296382 (9728 254 61)
128/000:22/SCN> Next QuickScan location at 156296385 (9729 0 1)
128/000:23/SCN> Next QuickScan location at 0 (0 0 1)
128/000:23/SCN> QuickScan finished
128/000:23/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=16065, RNG=63)
128/005:48/SCN> SmartScan finished
128/005:48/SCN> DiskScan completed
128/005:48/SCN> ReadErrors for disk 0 (128): 0
128/007:32/LOG> DataCollection items found: 14 / 6
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 128 | ........63 | ...NTFS | ..BS | ........63 | ..40965681 | PRI | .
002 | 128 | ..40965749 | ...NTFS | .BBS | .....16069 | ..40949681 | PRI | .
003 | 128 | ..40965750 | ...NTFS | PTE1 | ..40965813 | .115330572 | LOG | .
004 | 128 | ..40965813 | ...NTFS | ..BS | ..40965813 | .115330569 | LOG | .
005 | 128 | .156296384 | ...NTFS | .BBS | ..40965816 | .115330569 | LOG | .
006 | 128 | .156296384 | ...NTFS | .BBS | ..40965816 | .115330569 | LOG | I
007 | 128 | .........0 | ...NTFS | PTE1 | .....16065 | ..40949685 | PRI | .
008 | 128 | .........0 | ....EXT | PTE2 | ..40965750 | .115330635 | PRI | .
009 | 128 | ........63 | ...NTFS | ..BS | ........63 | ..40965681 | PRI | I
010 | 128 | .....16065 | ...NTFS | ..BS | .....16065 | ..40949681 | PRI | .
011 | 128 | ..40965749 | ...NTFS | .BBS | .....16069 | ..40949681 | PRI | I
012 | 128 | ..40965750 | ...NTFS | PTE1 | ..40965813 | .115330572 | LOG | I
013 | 128 | ..40965813 | ...NTFS | ..BS | ..40965813 | .115330569 | LOG | I
014 | 128 | .156296384 | ...NTFS | .BBS | ..40965816 | .115330569 | LOG | I
128/007:34/LOG> DataCollection items found: 14 / 6
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 128 | ........63 | ...NTFS | ..BS | ........63 | ..40965681 | PRI
002 | 128 | ..40965749 | ...NTFS | .BBS | .....16069 | ..40949681 | PRI
003 | 128 | ..40965750 | ...NTFS | PTE1 | ..40965813 | .115330572 | LOG
004 | 128 | ..40965813 | ...NTFS | ..BS | ..40965813 | .115330569 | LOG
005 | 128 | .156296384 | ...NTFS | .BBS | ..40965816 | .115330569 | LOG
007 | 128 | .........0 | ...NTFS | PTE1 | .....16065 | ..40949685 | PRI
008 | 128 | .........0 | ....EXT | PTE2 | ..40965750 | .115330635 | PRI
010 | 128 | .....16065 | ...NTFS | ..BS | .....16065 | ..40949681 | PRI
128/007:34/LOG> PartList items created: 7
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ... | ..1 | ... | --- | ..1 | ..1 | ..1 | 1 | ..B
002 | ...NTFS | ..7 | ... | ... | --- | ..7 | ..7 | ..7 | 1 | ...
003 | ...NTFS | ... | .10 | ... | --- | .10 | .10 | .10 | 1 | ..B
004 | ...NTFS | ... | ... | ..2 | --- | ..2 | ..2 | ..2 | 1 | ..B
005 | ...NTFS | ..3 | ... | ... | --- | ..3 | ..3 | ..3 | 1 | ...
006 | ...NTFS | ... | ..4 | ... | --- | ..4 | ..4 | ..4 | 1 | ..B
007 | ...NTFS | ... | ... | ..5 | --- | ..5 | ..5 | ..5 | 1 | ..B
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R
001 | ...NTFS | ........63 | ..40965681 | ..40965743 | PRI | ..B
002 | ...NTFS | .....16065 | ..40949685 | ..40965749 | PRI | ...
003 | ...NTFS | .....16065 | ..40949681 | ..40965745 | PRI | ..B
004 | ...NTFS | .....16069 | ..40949681 | ..40965749 | PRI | ..B
005 | ...NTFS | ..40965813 | .115330572 | .156296384 | LOG | ...
006 | ...NTFS | ..40965813 | .115330569 | .156296381 | LOG | ..B
007 | ...NTFS | ..40965816 | .115330569 | .156296384 | LOG | ..B
128/007:34/SST> SaveState requested for disk 0 (128)
128/007:40/WAS> AdmiSectors in use : 0+
128/007:41/SST> SaveState completed for disk 0 (128)
128/007:41/EXE> Analysis complete
128/007:45/LOG> RunTime: 007:45
128/007:45/LOG> ### CLOSE LOG ###
Do you think I can get my data back?
Thank you for your attention
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #1 on: June 19, 2008, 09:38:58 AM »

Hello,

To first answer your most important question; can data be recovered: yes most likely. If the disk can be repaired to a state where you can access the data using DiskPatch; I very much doubt that. Although the partition table setup is a bit weird (odd starting location for your primary partition) it looks valid + boot sector looks valid + DiskPatch can locate the MFT based on boot sector values. So, that means that partition table and boot sector wise there's no damage.

Leaves the option to extract files from the damaged volume using iUndelete or iRecover. For that you'd need to connect the disk to a system that's able to boot Windows and run the file recovery software from there.

PS I assume you can access the logical drive on this disk when it's connected to a system able to boot Windows, correct?

Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #2 on: June 20, 2008, 04:16:55 AM »

Hello
Thank you for your support.
With iRecover I've recovered a folder but with a lot of garbage. I'll try to recover another ones and I'll try iUndelete if it doesn't work satisfactorily
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #3 on: June 20, 2008, 08:51:44 AM »

Hello,

If Windows still assigns drive letters to the corrupt volumes, then you can try iUndelete. If iUndelete also 'recovers' corrupt information chkdsk either made the data FUBAR, or we may need to see if iRecover / iUndelete come up with a false parameter-set, possibly confused by chkdsk 'repairs'.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #4 on: June 21, 2008, 04:29:13 AM »

Hi
I confirm: Windows still assigns drive letters to the two corrupt volumes.
As I told you yesterday I've tried today iUndelete which also recovers a lot of garbage (the processes were a lot time longer and less folders were recognized than with iRecover)
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #5 on: June 24, 2008, 09:20:06 AM »

Hello,

Well, data maybe FUBAR, or and thats a small possibilty, this can be happening: iUndelete picks a wrong parameter set. So, what you can do/try is, run iUndelete in non-autopilot mode and override the clustersize iUndelete picks. Can you tell me what clustersize it detects after you have disabled auto-pilot?
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #6 on: June 26, 2008, 08:15:16 AM »

Hi
iUndelete detected the highest ranking 8 sect/clus, followed by 16, 32, 64 and 128 sect/clus. So the clustersize should be 4 KB
Regards
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #7 on: June 26, 2008, 09:29:16 AM »

Hello,

Ok, well that's the default cluster size. So, unless you picked a different cluster size clustersize is probably detected ok.

Q: Did you, using PartitionMagic, convert partitions from logical to primary at any point?
Q: In iUndelete, what's the overall validation score?

There's a number of possibilities. I am still not convinced data is unrecoverable, but I ay be wrong:

- start for the partition (the primary one) is odd, you'd expect it to start at sector 63, it doesn't. Of course if you have been using Partition magic in the past the boot sector we see at sector 63 can a 'remnant'.

- if partitions were moved/resized with Partition Magic iRecover/iUndelet may detect older file systems remnants and use those, that can also explain massive corruption
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #8 on: June 27, 2008, 05:58:08 AM »

Hi
I was using PartitionMagic some years ago (I don't remember exactly) to set up the two volumes on this HD. That's all with PM
In Iundelete here are the results:
Total files value:41231, Percentage:100%, 85 files discarded (garbage)
Total validated:5747, Percentage: 14% of total
Validation OK: 629, Percentage: 11% of validated
Validation corrupt: 5118, Percentage: 89% of validated
Total recoverable: 4535, Percentage: 11% of total
I can read some of my 1st volume data but none of the 2nd where the data I'm looking to get back are
Regards
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #9 on: June 27, 2008, 12:28:45 PM »

Hello,

I was hoping validation would show almost 100% corruption because it would indicate iUndelete picked the wrong clustersize. We could then have improved results probably by experimenting with a different cluster size.

Was the that first or the second partition you analyzed?
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #10 on: June 28, 2008, 06:12:46 AM »

HI
It was the second partition.
LBA starts: 40965749, LBA size: 40949680, GB size: 19.53
Regards
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #11 on: June 30, 2008, 10:24:54 AM »

Hello

where did you get that start LBA from? And, how do you select the volume in iUndelete?
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #12 on: July 01, 2008, 03:48:49 AM »

Hello

I found the LBA start and size with iUndelete ( Partition Recovery Mode => Scan for lost NTFS Partitions) After the scan I've set the partition recovery mode to manually and entered the start LBA and size and got the infos I sent you
Regards
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #13 on: July 01, 2008, 08:35:23 AM »

Hello,

Since we're not dealing with lost partitions, I suggest you pick unformat mode and then simply pick that partition from the drive list and then scan it. Alternatively you can instead select the physical disk, then click next, then from the partition list select the largest partition.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
bob
member

Posts: 8


« Reply #14 on: July 06, 2008, 11:40:09 PM »

Hello
It's same in unformat mode or after selecting the larger partition.
Data of the 1st lost volume seems to be possibly recovered but nothing at all concerning the data of the 2nd one
Regards
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.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!