- Downloaded
- 248.4 GB
- Uploaded
- 77 TB
- Ratio
- 317.45
- Seedbonus
- 1,090,380
- Upload Count
- 0 (0)
Member for 2 years
Great thread. Thanks to all!
i have the same issueYou must be registered for see links
Hi! Can someone create the 2 usb iso files for me?
Unfortunately, that doesn't work for me. :-(
Thanks
same issue here any bypass or an bootable iso image?i have the same issue
Absolutely True Sir. I am a Data Recovery Specialist and i encounter such cases where people do not Understand and keep inserting and removing the disks not knowing that everytime the disk spins, the heads move across the platters andt try to read the bad blocks and then a sudden stop. This process leads to head damage or complete head loss, Scratches on platters which makes the accessible data inaccessible and continuous spinning of platters and heads moving in and out increases the risk of deep scratches on platters resulting in a complete Hard Drive failure.I will just point out some facts and then everyone can believe and do whatever they like.
Software like this stopped working as intended a long time ago and here is why.
1. Under Windows and especially since Windows 7, no software is allowed to talk to any hardware directly. They have to talk to the device driver or relative APIs, so no such software can see or access the hard disks directly.
2. IDE/Sata drives (the spinners) have their own unique controller which talks to the motherboard IDE/Sata bios. Not even Windows knows what the disks are doing. Each controller is designed uniquely for each disk so no software can really know how many heads/tracks/sectors or blocks each disk has, but they rather use a translation layer that converts the physical absolute characteristic of the disk, to compatible values that bios/windows can use.
Dont take my word tho, open a power shell and type
gwmi win32_diskdrive |select DeviceID,SectorsPerTrack,Size,TotalCylinders,TotalHeads,TotalTracks,TracksPerCylinder
and you will see something like this
So either my NVMe has 128 platters and 255 heads and is 64 cm ( about 25 inches ) thick or...
3. Such software will NOT work for SSD, NVMEs, USB thumb drives, etc, yet they somehow do... SSDs and NVMes don't have sector tracks, and heads, they have cells so what is there to correct? TRIM automatically rearranges data based on free cells so there is no way for Windows and any software to know where data are physically stored on an SSD or NVMe.
I can go on but I think you get the idea by now.
So, what is actually happening? All disks have some extra space which is reserved for when errors happen. When they detect errors on a block, they try to re-read it on their own and copy whatever data they can to a block from the reserved space, mark the old block as bad, and move on.
Software such as this that "corrects" hard disks, just asks Windows to scan (read) the entire disk, from start to end, and if an error is detected from Windows it keeps sending retry commands hoping that the disk controller will start the auto repair. That is why some people say they had positive results and some don't but truth be told, those who had success, would have corrected the issue anyway, and those who failed, there is no hope other than a professional repair service.
Long story short, snake oil.
To make things worse, some problems like disk head issues, power issues, and others, because of the number of retries this kind of software sends, can make the problem MUCH worse. If the heads for example scratch the platters and the software sends like 50 retries, all you will end up with is a deeply scratched disk surface making you lose even more data instead of saving.
Only saying the above in the interest of knowledge and not to insult the uploader which I thank for sharing software with us.