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

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  Unallocated Disk Partition !
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Unallocated Disk Partition !  (Read 11863 times)
kn0ck0ut
member

Posts: 5


« on: August 17, 2014, 01:53:28 PM »

Operating system: Windows 7 (64 bit)

Hi.. My windows crashed. I tried to repair by windows cd, or by using restore point. Noone of them worked. I was thinking that, there was something wrong with the hard disk.  I decided to try my old Hiren's Boot CD which was the version 9.xx something. I saw there was a Disk Patch v.2.1.100, I heard about Disk Patch before, so I executed it.
I started to analyze and after that clicked to repair. It warned me about some points but I didnt read carefully. I thought "what can be happen at most, it will repair."
Now partitions are dissappered and harddisk seems 500 gb unallocated space. If my data's are deleted I'm dead person cause I dont have backup Cry Cry

I did analysis log operation but dont know how to reach the file since operating system does not open.
Pleaseee tell me what to do and which steps I should follow to reach my old data's.  Cry

Best Regards
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #1 on: August 17, 2014, 10:23:32 PM »

The DiskPatch version on Hiren is illegal, so no support there.

Getting to your data will probably require a purchase on your end. If you're okay with that start here (this part's free):
http://www.diydatarecovery.nl/dp_manual/guide_supportanalysis.htm

Use the latest DiskPatch version, found here:
http://www.diydatarecovery.nl/download.htm
Logged

kn0ck0ut
member

Posts: 5


« Reply #2 on: August 19, 2014, 02:04:51 PM »

First of all I'm so sorry for hiren. I didnt know that it is illegal, i just used what I had. I always respect the effort given by developers

I installed latest version of Disk Patch and created an support analysis.
Here it is.



.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.300
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 62Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 08-18-2014
.../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> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../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: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 1978/16/63 1994752/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 976773168/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> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 1912/255/63 30720000/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
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ...1994752 | .16 | 63 | ...0 | BIOS | .512
129 | .976773168 | 255 | 63 | .465 | BIOS | .512
130 | ..30720000 | 255 | 63 | ..14 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/RDS> ReadError for disk 129 at 0 (0 0 1), C:1, T:20h (Controller failure)
.../000:01/RDS> ReadSector success (after error) at 0 (0 0 1), tries 1
.../000:01/IAS> AdmiSector found on disk 0 (128)
.../000:01/IAS> AdmiSector found on disk 1 (129)
.../000:01/IAS> AdmiSector init complete for disk 2 (130)
.../000:01/KEY> DEMO/1
.../000:01/PFC> PQstuff signature not detected on disk 0 (128)
.../000:01/PFC> PQstuff signature detected on disk 1 (129)
.../000:01/PFC> PQstuff signature not detected on disk 2 (130)
.../000:01/PFC> Disk health not checked
.../000:02/PFC> Partition State backup not found on disk 0 (128)
.../000:02/PFC> Partition State backup not found on disk 1 (129)
.../000:02/PFC> Partition State backup not found on disk 2 (130)
.../000:02/PFC> No Repair date found on disk 0 (128)
.../000:02/PFC> No Repair date found on disk 1 (129)
.../000:02/PFC> No Repair date found on disk 2 (130)
.../000:16/CSD> Start CheckDisk for disk 1 (129)
.../000:16/CSD> 0 (0 0 1)
.../000:16/CSD> 16064 (0 254 63)
.../000:16/CSD> 976768065 (60801 0 1)
.../000:16/CSD> 976773167 (60801 80 63)
.../000:16/CSD> CheckDisk complete, ReadErrors 0
.../000:16/USD> Disk 1 (129) selected
.../000:16/GSC> No geo change detected for disk 1 (129)
.../000:16/WAS> AdmiSectors in use : 0+ 1+ 2+
129/000:16/USD> MBR for disk 1 (129)
129/000:16/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 DC C2 E1 F6 00 00 00 20  |  em...c{...
448   21 00 07 BE 12 2C 00 08 00 00 00 F0 0A 00 00 00  |  !...,.....ğ....
464   00 00 00 00 00 00 00 00 00 00 00 00 00 00 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:16/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:16/VEC> Listing current partitions on disk:
129/000:16/VEC>     NTFS (P)  System Rese        2048      716800       (0 Gb)
129/000:16/VEC> Partition Table info for sector 0 (0 0 1)
129/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 ...0 | ..07 | ....0..32..33 | ...44.190..18 | ......2048 | ....716800
..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
129/000:16/VEC> 55AA sig Ok
129/000:16/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): 716792
........MFT Location (dec): 29866
.MFT Mirror Location (dec): 2
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 1638ED6638ED44F9
........Volume Label (txt): System Rese
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:16/VEC> BS and BBS equal
129/000:16/VEC> Verify EPBR Chain completed
129/000:17/USD> Select disk completed
129/000:19/SCN> DiskScan requested, ScanType is 3
129/000:19/SCN> from 0 (0 0 1) to 976773167 (60801 80 63), 976773168 sectors
129/000:19/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
129/000:19/SCN> Next QuickScan location at 718841 (44 190 12)
129/000:19/SCN> Next QuickScan location at 718848 (44 190 19)
129/000:20/SCN> Next QuickScan location at 274542592 (17089 123 59)
129/000:20/SCN> Next QuickScan location at 0 (0 0 1)
129/000:21/SCN> QuickScan finished
129/000:21/SCN> Starting SmartScan (vista) at 0 (0 0 1)
129/000:21/RDS> Read past EOD intercept for disk 129 at 4294967295 (267349 89 4)
129/065:59/SCN> SmartScan finished
129/065:59/SCN> DiskScan completed
129/065:59/SCN> ReadErrors for disk 1 (129): 0
129/529:29/LOG> DataCollection items found: 16 / 5
### DATACOLLECTION, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....716793 | PRI | .
002 | 129 | ....718840 | ...NTFS | .BBS | ......2048 | ....716793 | PRI | .
003 | 129 | ....718847 | ...NTFS | .BBS | ......2055 | ....716793 | LOG | .
004 | 129 | ....718847 | ...NTFS | .BBS | ......2055 | ....716793 | LOG | I
005 | 129 | ....718848 | ...NTFS | ..BS | ....718848 | .273823744 | PRI | .
006 | 129 | .274542591 | ...NTFS | .BBS | ....718848 | .273823744 | PRI | .
007 | 129 | .........0 | ...NTFS | PTE1 | ......2048 | ....716800 | PRI | .
008 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....716793 | PRI | I
009 | 129 | ....718847 | ...NTFS | .BBS | ......2055 | ....716793 | LOG | I
010 | 129 | ....718848 | ...NTFS | ..BS | ....718848 | .273823744 | PRI | I
011 | 129 | ..45027328 | ...NTFS | ..BS | ..45027328 | ......6174 | PRI | .
012 | 129 | .274542591 | ...NTFS | .BBS | ....718848 | .273823744 | PRI | I
013 | 129 | .315502591 | ...NTFS | .BBS | ....718855 | .314783737 | PRI | .
014 | 129 | .315502592 | ...NTFS | ..BS | .315502592 | .661266432 | PRI | .
015 | 129 | .976769023 | ...NTFS | .BBS | .315502592 | .661266432 | PRI | .
016 | 129 | .976773119 | ...NTFS | .BBS | ......2055 | .976771065 | LOG | .
129/529:29/LOG> DataCollection items found: 16 / 5
### DATACOLLECTION, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....716793 | PRI
002 | 129 | ....718840 | ...NTFS | .BBS | ......2048 | ....716793 | PRI
003 | 129 | ....718847 | ...NTFS | .BBS | ......2055 | ....716793 | LOG
005 | 129 | ....718848 | ...NTFS | ..BS | ....718848 | .273823744 | PRI
006 | 129 | .274542591 | ...NTFS | .BBS | ....718848 | .273823744 | PRI
007 | 129 | .........0 | ...NTFS | PTE1 | ......2048 | ....716800 | PRI
011 | 129 | ..45027328 | ...NTFS | ..BS | ..45027328 | ......6174 | PRI
013 | 129 | .315502591 | ...NTFS | .BBS | ....718855 | .314783737 | PRI
014 | 129 | .315502592 | ...NTFS | ..BS | .315502592 | .661266432 | PRI
015 | 129 | .976769023 | ...NTFS | .BBS | .315502592 | .661266432 | PRI
016 | 129 | .976773119 | ...NTFS | .BBS | ......2055 | .976771065 | LOG
129/529:29/LOG> PartList items created: 8
### PARTLIST ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ..7 | ... | ... | ..0 | ..7 | ..7 | ..7 | 1 | ...
002 | ...NTFS | ... | ..1 | ..2 | ..0 | ..1 | ..1 | ..1 | 2 | ..A
003 | ...NTFS | ... | ... | ..3 | ..0 | ..3 | ..3 | ..3 | 1 | ..B
004 | ...NTFS | ... | ... | .16 | ..0 | .16 | .16 | .16 | 1 | ..B
005 | ...NTFS | ... | ..5 | ..6 | ..0 | ..5 | ..5 | ..5 | 2 | ..A
006 | ...NTFS | ... | ... | .13 | ..0 | .13 | .13 | .13 | 1 | ..B
007 | ...NTFS | ... | .11 | ... | ..0 | .11 | .11 | .11 | 1 | ..B
008 | ...NTFS | ... | .14 | .15 | ..0 | .14 | .14 | .14 | 2 | ..A
### PARTLIST, INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ....716800 | ....718847 | PRI | ... | ..V
002 | ...NTFS | ......2048 | ....716793 | ....718840 | PRI | ..A | ..V
003 | ...NTFS | ......2055 | ....716793 | ....718847 | LOG | ..B | ..?
004 | ...NTFS | ......2055 | .976771065 | .976773119 | LOG | ..B | ..?
005 | ...NTFS | ....718848 | .273823744 | .274542591 | PRI | ..A | ..V
006 | ...NTFS | ....718855 | .314783737 | .315502591 | PRI | ..B | ..?
007 | ...NTFS | ..45027328 | ......6174 | ..45033501 | PRI | ..B | ..V
008 | ...NTFS | .315502592 | .661266432 | .976769023 | PRI | ..A | ..V
129/529:29/SST> SaveState requested for disk 1 (129)
129/529:29/WDS> WriteError for disk 130 at 34 (0 0 35), C:1, T:80h (Timeout)
129/529:29/WDS> DiskReset failed for disk 2 (130), T:80h (Timeout)
129/529:29/WDS> Maximum (1) allowed WriteErrors reached at 34 (0 0 35)
129/537:38/HWE> Abort DiskWrite after MaxWriteErrors reached at 34 (0 0 35)
129/537:38/WAS> AdmiSectors in use : 0+ 1+ 2+
129/537:39/SST> SaveState completed for disk 1 (129)
129/537:39/EXE> Analysis complete
129/537:43/LOG> RunTime: 537:43
129/537:43/LOG> ### CLOSE LOG ###

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #3 on: August 19, 2014, 02:59:59 PM »

There are some read errors, so there may be something wrong with a disk, more disks, or a controller.
Please run this as well:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm

Now, the list of all volumes that DiskPatch finds on the disk is this:

SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ....716800 | ....718847 | PRI | ... | ..V
002 | ...NTFS | ......2048 | ....716793 | ....718840 | PRI | ..A | ..V
003 | ...NTFS | ......2055 | ....716793 | ....718847 | LOG | ..B | ..?
004 | ...NTFS | ......2055 | .976771065 | .976773119 | LOG | ..B | ..?
005 | ...NTFS | ....718848 | .273823744 | .274542591 | PRI | ..A | ..V
006 | ...NTFS | ....718855 | .314783737 | .315502591 | PRI | ..B | ..?
007 | ...NTFS | ..45027328 | ......6174 | ..45033501 | PRI | ..B | ..V
008 | ...NTFS | .315502592 | .661266432 | .976769023 | PRI | ..A | ..V


The most likely candidates are 5, 6 and 8. Obviously 5 and 6 can't co-exist so it's up to you to decide which one is the most likely candidate. Actual sizes are:
volume 5 - 130 Gb
volume 6 - 150 Gb
volume 8 - 315 Gb
I'd say it's 6 and 8 because they "connect" perfectly (though 6 has some weird attributes, but try. if it's not 6 then try 5).

Questions:
- When you ran the recovery CD (Windows recovery, correct?) did you actually repair a volume?
- Was this done before you ran DiskPatch 2 and "fixed" the disk?
- Was at any time a volume changed (made bigger or smaller) by using a 3rd party volume tool?

From what I see here a repair should be possible. You select the volumes I indicated and see how that works out. A walkthrough of the procedure can be found here (it is an example, things will be different at your end):
http://www.diydatarecovery.nl/dp_manual/guide_ptrepair.htm
Logged

kn0ck0ut
member

Posts: 5


« Reply #4 on: August 19, 2014, 05:10:10 PM »

Here is the report:

Detected Controllers

Disk Controller 1
Device Vendor . . . . . . . . . . . . . : 8086
Device ID . . . . . . . . . . . . . . . : 1C03
Device  . . . . . . . . . . . . . . . . : Intel
Device Location . . . . . . . . . . . . : Bus 0, Device 31, Function 2
Device Ports  . . . . . . . . . . . . . : E070-E077, E060-E063, E050-E057, E040-E043, E020-E03F

Questions:
- When you ran the recovery CD (Windows recovery, correct?) did you actually repair a volume?
- Was this done before you ran DiskPatch 2 and "fixed" the disk?
- Was at any time a volume changed (made bigger or smaller) by using a 3rd party volume tool?

Answers
  • It was before trying DiskPatch 2.
    Maybe while I was formatting laptop 5-6 ago, I did it. Apart from that, I did not extend it or make it shorter.

So now we are sure that my data's are still there and the repair operation does not give any harm. am I  right?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #5 on: August 19, 2014, 09:30:34 PM »

Quote
So now we are sure that my data's are still there and the repair operation does not give any harm. am I  right?
No. The health report is incomplete (unless you made a mistake in copying the report), so something is very wrong. Without the report it is impossible to say what that is but the fact that the report is this short is bad.

We are not sure that your data is there. We have an idea of where the volumes are and we can probably fix the volume table. This says nothing about what is IN the volumes, especially as you've been doing things like a repair.

As far as harm goes... Things are not good now so it can only get better. We will know how "harmful" it was when you've finished.

The first thing you should do is find out which part of the PC (the hardware) is causing problems. The fact that your Windows crashed also points in the direction of faulty hardware. We've tried the health check and that didn't work so it's up to you now to figure that out.

DiskPatch doesn't show many read errors so you could simply go ahead as-is, but if I were you I'd first try to figure out what is wrong on a hardware level.
Logged

kn0ck0ut
member

Posts: 5


« Reply #6 on: August 21, 2014, 09:41:51 AM »

Just wanted to inform you, I did repair operation and after assigning partition attributes, I reached the partitions by virtual xp .  By the way the true candidates were 5 and 8, because 6 was not working. After reaching the data's I took the backup and wipe the disk by Disk Patch. I think it will be beneficial for the disk. Thanks a lot for the help.
Do suggest any maintenance operation after wipe ?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #7 on: August 21, 2014, 11:14:50 AM »

Quote
First of all I'm so sorry for hiren. I didnt know that it is illegal, i just used what I had. I always respect the effort given by developers
It seems you used the illegal version of DiskPatch to do the repairs so I'm not really inclined to help you any further.
Logged

kn0ck0ut
member

Posts: 5


« Reply #8 on: August 21, 2014, 02:17:55 PM »

I used latest version of it as you said. But as you wish. I dont need your help.

By the way you could just say "It seems unallocated partition because disk patch sets all of the partitions deactivate ".
But instead of saying that you just said "you need to purchase" bla bla bla.

This is a TRAP. Unwillingly I used free and old version of your program and encounter with some difficulties because of your program again. After that you are saying that you need to purchase to solve the problem that your program caused. At the end of the day you are expecting honesty which you do not have.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #9 on: August 21, 2014, 03:18:54 PM »

No, no trap. You messed it up by using DiskPatch incorrectly (and illegally), that's not on us.
Quote
By the way you could just say "It seems unallocated partition because disk patch sets all of the partitions deactivate ".
But instead of saying that you just said "you need to purchase" bla bla bla.
Also incorrect. There were no volumes in the table, except for a recovery volume. So nothing was inactive, it wasn't there. My purchase remark meant that, given the Hiren stuff, I expected you to buy a license IF we could help you. Turned out we could, and we did.
And for the record, yes, you could have used the illegal version 2 to repair the volumes. The manual states that nothing is set active, for safety reasons. You did not read the manual, or the walkthroughs, otherwise you would have known this.

I checked sales records to see if you bought a license and didn't see the sale. That led me to the conclusion that you used the illegal version.
If I jumped to the wrong conclusion then please accept my apologies.

At the end of the day we helped you fix a problem that was created by you, by using one of our (illegally obtained) products incorrectly. I do not fear for my honesty.
Logged

Pages: [1] 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!