February 18th 2009 - Wizcode LLC annoucned the public beta of Wizcode Defragment Mobile, storage card and RAM defragmenter and optimizer for Windows Mobile.

Wizcode Defragment Mobile can defragment files and folders on the storage card of your Windows Mobile device and optimize folder performance by re-sorting the directory entries of each folder. You will notice dramatically increased perfomance especially in applications that list a large number of files like file explorers, image viewers etc. Zero fragmentation is also essential for any data recovery procedures you may attempt

The new Defragment Mobile is based on previously announced Evolution framework and the Wizcode FATFS library.

Below is the summary of features in the current version:

  * Check fragmentation - will report the summary file and folder fragmentation and will optionally report directory entry sorting issues.

  * Defragment - eleminates file and folder fragmentation, improves overall storage card performance.

  * Sort directory entries - by keeping the folder contents sorted there can be a significant gain in performance/start up of many applications that sort file lists internally.

  * Defragment service - automatically defragment storage cards when the device is rebooted.

  * Exclusive card access - storage cards are now locked when being defragmented which virtually removes the possibility of a conflict with another application trying to access the storage card meanwhile.

  * RAM optimization - heap defragmentation and optimization will also reclaim unused RAM from running applications.

  * Error checking - volumes will be checked for errors before defragmentation (can be turned off although not recommended)

The public beta of Wizcode Defragment Mobile can be downloaded here:

  * Windows Mobile 2003 device .CAB file

  * Windows Mobile 5 devices .CAB file

  * Windows Mobile 6 devices .CAB file

New version (v1.0.1) uploaded today. Changes include:

- Fixed reverse ScanDisk logic
- Improved folder sorting speed
- Improved user abort responsiveness

The beta can be downloaded from our servers (download links above).

mkss55442 - 19 February 2009 06:02 AM

Hi Anton,
You’re too fast for me! I was going to report a couple of issues but I’ll wait to see if 1.0.1 solves them
Mark

Mark, go ahead and report any issues you have found!

mkss55442 - 19 February 2009 05:55 PM

Hi Anton,

Running Check Card
4GB CF card: 4.8% fragmented, 38% folders with unsorted directory entries
16GB SD card: 0.58% fragmented, 48 folders with unsorted directory entries

Running Defragment Card on the SD card hangs on an empty folder, requiring a soft reset. I didn’t try defraging the CF card.

Interesting that the Card Check Report shows (among other things) a defragmentation time of 49710 days for both cards.

As a comparison, I ran the Defrag module in Pockect Mechanic.
CF card: 0.03% fragmented
SD card: 0.58% fragmented

Running Defragment RAM reclaims 0 bytes reclaimed. I don’t have anything to compare it to so I don’t know if that’s “normal”.

Rgards,
Mark

Hi Mark,
Fixed the 49710 days of defragmentation time It is normal for the reclaimed RAM to vary. That depends on the heap fragmentation and could be 0 to several megabytes. If you defragment the heap and reclaim some RAM it is normal to not reclaim anything a short time after that since the heap hadn’t had the chance to fragment yet.

Regarding the lock up - are you sure it’s a lock up and not something that is just slow? Can you send me an email and I will respond a debug build to verify where exactly the issue is?

Thanks,
Anton