Creator wrote:
xehqter wrote:
1.6 is buggy as hell.. it crashes constantly, 1.6.1 is a lot more stable. When/if they crack SanDisk Crypto I'll give them a pat on the back otherwise I'm not impressed. PC3K flash is only good for 10% of my cases, granted it is nice when it works
I wish all I got were USBest or SM32x those are easy.
Auto Detect works well on "known" controller/size combo's, otherwise its useless, it mangles the image beyond recognition or does nothing.
I couldn't imagine, how do you solve only 10% of cases? I suppose that you're didn't read the manual. In the PC3k flash there are universal algorithms which are very good. Much better than in another tools. As I can see you're newbie and you use only "Recovery via controller mode". You should just run autoanalysis and it will solve much more your cases.
Read more about "how to use new version" there:
http://www.pc-3000flash.com/eng/ver161.090302.phpROFLMAO, I haven't been called newbie much less been told to RTFM in so long. Thanks for the complement...
Yes, 10%, granted I haven't had enough time to give 1.6.1 a good tryout. I got 1.6 on the 2nd which was so buggy I stopped using it, and 1.6.1 on Monday.
Problem #1. No SANDISK SUPPORT!!! SanDisk are the most popular drive I have coming in..
Problem #2. No Support for Flash Drives with non-standard pages sizes (only 528 or 2112 are supported)
Problem #3. Tech-support, the lack of trained techs.
Problem #4. Auto Mix detection results vary greatly, sometimes their spot on, other times its way out there. I've had drives with no mix that get flagged as having a mix, other times its a simple block split that the Auto-Mix detection ends up splitting the image many different ways producing a completely mangled result. Whenever I get an unpopular controller guaranteed auto-mix detection will mess it up in some way.. yes, I can solve the mix manually w/ PC3K however SoftCenters Mix Editor is far superior. Understandable as PC3K's product is geared towards automated recovery.
Problem #5. Documentation or the lack or it
Problem #6. The assemblers are myopic, they tend to work only cases that PC3K flash has seen, not real world. For example I had a controller using Transcend_F0 , the translation table for Bank 0 was lost in an erase cycle.. all 0xFFFF, PC3K flash gave up. SoftCenter used the block numbers in the SA for bank 0 and the translation table for Bank 1.
I could go on all day..
In the last 5 months PC3K has made fantastic progress. Back when PC3K started doing hard drives, they only supported a few. Now they support many. Its the same with flash drives. I'm not saying its a bad product, just that RIGHT NOW, it doesn't support a lot of flash drives. Unlike hard drives, there are many companies manufacturing controllers, this makes it tough.. PC3K is to ridged in design, to be a complete solution it needs more flexibility. They will always be playing catchup to the market.
In the long run, time is money. When PC3K perfects its translators, assemblers, and mix detection it will save me time. Until that happens I'll be using other solutions which make the process of solving the mix & assembling the image easier. Even if I have to write them myself. Right now I'm using both products, when auto-detection fails I head to SoftCenter.