MGP Posted January 17, 2014 Author Report Posted January 17, 2014 Hi MGP, Please download the new file and try again, the file wiselog.txt will be saved in C: drive THX. WiseCare365.zip wiselog.txt
wisecleaner_admin Posted January 18, 2014 Report Posted January 18, 2014 Hi MGP, Please try this file again, if ti cannot get your disk info, it will create a log file in C:\wiselog.txt THX. WiseCare365.zip
wisecleaner_admin Posted January 19, 2014 Report Posted January 19, 2014 Hi MGP, Try this new file, and send the log file to me. Thank you! WiseCare365.zip
wisecleaner_admin Posted January 20, 2014 Report Posted January 20, 2014 Hi MGP, Please try this new file. whatever it can find your disk, send me a screenshot, defragment screenshot. like this: WiseCare365.zip
MGP Posted January 20, 2014 Author Report Posted January 20, 2014 Screenshot 1 - Defrag analysis Screenshot 2 - Wisecare365 crashes when I click on DiskEraser
wisecleaner_admin Posted January 21, 2014 Report Posted January 21, 2014 Hi MGP, Please try this new file. Thank you. WiseCare365.zip
MGP Posted January 21, 2014 Author Report Posted January 21, 2014 Looks like a success. DiskEraser recognized the drive. And when I clicked "Clean", it started the Erasure process. I didn't have it clean the whole drive, since the only recoverable files were actually clusters that Ccleaner had already cleaned and renamed with files names of zzzzzz, etc. That and the estimated time of over 5 hours, I figured as long as it recognized the drive and started the process was enough to prove a successful run. So, what was the ultimate fix that finally got it to work?
wisecleaner_admin Posted January 24, 2014 Report Posted January 24, 2014 Hi MGP, Sorry for delay. Thank you for your help to fix this problem. The reason is, the MBR (Master Boot Record) of your disk is not 512 byte.
MGP Posted January 27, 2014 Author Report Posted January 27, 2014 Hi MGP, Sorry for delay. Thank you for your help to fix this problem. The reason is, the MBR (Master Boot Record) of your disk is not 512 byte. I'm guessing that's due to the fact that, according to what I've read, (from Wikipedia) "The organization of the partition table in the MBR limits the maximum addressable storage space of a disk to 2TB", and my disk is 3TB. According to what I've read, my disk should utilize GPT, but I'm not sure it is. Anyway, I'll leave it at that. Glad I could help you figure out why Wisecare365 wasn't able to read the disk. Thanks again for a great product. UCanFixIt 1
UCanFixIt Posted January 27, 2014 Report Posted January 27, 2014 According to what I've read, my disk should utilize GPT, but I'm not sure it is. Your disk is not GPT (according to the diskpart view I asked you to provide earlier). In addition, the GPT requirement only applies to boot drives. So, the only logical conclusion is/was that Wise Care 365 could not address anything above 2TBs (as you stated) because they were hard-wired to the old standard addressing format. You did them a great service by hanging in there and helping them correct their addressing issue.
wisecleaner_admin Posted January 29, 2014 Report Posted January 29, 2014 Thank you MGP, you help us to improve Wise Care 365. Thank you UcanFixIt, too.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now