We have a public beta of Wizcode ScanDisk Mobile.

Read the press release and download the beta here.

We will release a beta of another brand new product - Wizcode Defragment Mobile in the next 48 hours followed by a new beta of Wizcode Data Recovery Mobile featuring our new revolutionary Unformat module that is able to recover files from severely damaged file systems or formatted storage cards.

Tell us what you think!

Cheers,
Anton

mkss55442 - 12 February 2009 12:44 PM

Hi Anton,

I ran the new ScanDisk on my x51v/WM6.1 and here are the results:

4GB CF Card: 519 folders, 518 cross-linked chains, elapsed time <3 minutes
16GB: SD Card: 1854 folders, 1853 cross-linked chains, elapsed time >15 minutes

Then I ran WDRM’s ScanDisk and here are the results:

4GB CF Card: 519 folders, 0 cross-linked chains, 1 directory issue, elapsed time approx. 1 minute
16GB SD Card: 1854 directories, 0 cross-linked chains, 4 directory issues, elapsed time approx. 1 minute

I didn’t let the new ScanDisk fix any of the errors, but it’s hard to believe that there would be that many errors and the cards still work.

Regards,
Mark

Mark, we uploaded a new beta today (v1.0.4), please run another check using this new build. If you are still getting that many errors please contact me and I will send a debug build.

mkss55442 - 18 February 2009 06:12 AM

Hi Anton,
I think 1.0.4 is much better.

New Scandisk (automatic fix turned off):
CF card - 1 lost cluster
SD card - FAT tables mismatch, scanning stopped there because of the critical error

WDRM Scandisk (automatic fix turned off):
CF card - 1 lost chain and 1 lost cluster
FAT tables mismatch, but it said it was using the backup FAT table. After using the backup FAT table, it found 3 directory issues.

Re-ran new Scandisk (automatic fix turned off):
CF card - 1 lost cluster
SD card - FAT tables matched with 3 directory issues

It would appear that running WDRM Scandisk on the SD card fixed the FAT table mismatch, even though the automatic fix was unchecked. It also found one lost chain on the CF card that the new Scandisk didn’t.

Is it a valid comparison the run the WDRM Scandisk against the new Scandisk?

One other minor nitpick…When isntalled, WDRM created a Wizcode folder on the start menu. The new Scandisk shortcut wasn’t put in that folder.

Regards,
Mark

Nice response time Mark!

We are still about to recompile WDRM to include the new ScanDisk code, for now just assume it contains an older implementation. The latest ScanDisk (1.0.4) is what you should be using for now. We are adding the new Unformat module to WDRM which is the reason it is still being on hold. Hope to have a beta of that as well in a few days!

P.S. Check the new beta we announced:

Wizcode Defragment Mobile Beta

Regarding the Wizcode folder - we temporarily disabled that as it didn’t work well on some devices (just one to be exact).

thejbfamily - 18 February 2009 08:33 AM

Hi Anton,

I just downloaded Scandisk (running in trial mode).

My PDA is:

HP HX2795 iPAQ
624MHz CPU
CF Card:  8GB Sandisk Extreme III
SD Card:  2GB Sandisk Ultra II

Running Scandisk on my CF Card:
Took a little over 7 minutes to run
107 Lost Chains
26008 Lost Clusters

Running Scandisk on my SD Card
1 Lost Chain
77 Lost Clusters
1 Invalid Cluster

Using Norton’s Scandisk on my Windows XP machine:
CF Card:  No Errors Found
SD Card:  No Errors Found

I don’t know why there would be a difference between the Windows XP scanning and the one by your software.

Hi thejbfamily,
Are you running ScanDisk 1.0.4? If you are please email me and I will send back e debug build that will dump the lost clusters and the reason why they were declared lost.

Magellan - 19 February 2009 09:06 AM

The latest version of Scandisk fixes the issues I had with folders becoming innaccesible after fixing errors.  It now runs perfectly on my WM2003 devide!

Hey Magellan,
Glad to see you around!

Anton

thejbfamily - 18 February 2009 08:33 AM

Hi Anton,

I just downloaded Scandisk (running in trial mode).

My PDA is:

HP HX2795 iPAQ
624MHz CPU
CF Card:  8GB Sandisk Extreme III
SD Card:  2GB Sandisk Ultra II

Running Scandisk on my CF Card:
Took a little over 7 minutes to run
107 Lost Chains
26008 Lost Clusters

Running Scandisk on my SD Card
1 Lost Chain
77 Lost Clusters
1 Invalid Cluster

Using Norton’s Scandisk on my Windows XP machine:
CF Card:  No Errors Found
SD Card:  No Errors Found

I don’t know why there would be a difference between the Windows XP scanning and the one by your software.

Jim, did you receive my email?

Best,
Anton

thejbfamily - 19 February 2009 11:45 AM

Hi Anton,

Yes I did receive it.  I installed the Debug version of Scandisk (after uninstalling the beta version), and have tried running it a couple of times now (actually on the second time now).  The first time, it ran for about 2 hours, (I went to lunch during this time).  When I got back from Lunch, my PDA was locked-up.  The Scandisk screen was up, but the bar along the bottom didn’t move, and the Animated Wait Cursor (the WM 5.0 one), wasn’t moving either.  The PDA didn’t respond to any screen taps, etc.  I ended up having to do a soft reset on it.  I need to ru nto a meeting, then I will try to run this program when I get back.  Since it appears to take a realy long time to run the debug program, I better have the device on external power when running the debug.

The debug version is slow mainly because it writes a lot to the log file. On several of our test devices debug versions produced log files larger than 15MB! Also make sure you have more free memory, close all running applications before running the debug version. If that doesn’t work I will send a new debug version that minimizes writes to the log file. Good luck!

thejbfamily - 19 February 2009 01:29 PM

Tell me about it.  The Log file that it initially wrote was around 9MB.  Running it again…  I wonder if maybe I ran out of RAM (while it was trying to write to the Log file)...I know that with the programs I have loaded, I don’t have a ton of storage memory (in the main memory).  I might have to move a bunch of these programs out of my main memory (while I am running the debug).  I will have to see if it hangs again.  If it doesn’t finish off in 1/2 an hour, I’m going to have to kill it until later tonight.  I have to go from my primary job to my second job.  When I get done there, I will start it again at home (after 8:00 PM Arizona Time).

You could run out of RAM if the log file is written to RAM. If your device has a second storage card I can configure ScanDisk to dump the log file there. Just in case you decide to stop it use the stop button instead of soft resetting the device.

thejbfamily - 03 March 2009 08:39 AM

My Trial Version is going to expire in 14 Days.  Is there any way that you can send me the Registration code?  I will wait to enter it until Scandisk Mobile expires (to make sure that it works), but it would be nice to get the registration code.

We will be generating the new batches of license keys in the next few days. Sorry this took so long.

thejbfamily - 31 March 2009 09:38 AM

thejbfamily - 16 March 2009 12:59 PM

My version of Scandisk is going to expire in 1 day.  Can I get a registration code?My Device ID is Jim Blanchard.

I can’t use this anymore.  I get the message “Evaluation period has expired.”  Can I get a Serial Number?  This is like my 3rd request…  My Device Name is Jim Blanchard.

Please send me a private message, I will send your license via PM. Thanks.

thejbfamily - 31 March 2009 11:21 AM

Hi Anton,

OK, I entered my Registration Number.  It accepted the number as a valid code, I clicked on Close, and it took me to the main screen.  When I clicked on the Scan button, it said that the evaluation period had expired, and it took me to the registration screen.  The boxes where you enter the Registration number were greyed out with *‘s in them, I clicked on close, and it took me back to the main screen.  When I clicked on the button to do the scan, it said that the evaluation period had expired, and it took me to the registration screen (again).  I clicked on Close, and I was taken to the Main Menu again.  I exited Scandisk, and then ran it again, this time it started up the scan just fine (it knows it is registered now).

What I reported above might be “normal”, but I don’t remember this occuring with the programs that I have purchased from you in the past (Virtual Explorer, Pocket Mechanic Professional , Pocket Hack Master).  Just figured I would let you know.

You are still running the beta. The issue is fixed in the official release.