Recent changes to bugs

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Filip Sikora — Wed, 01 Mar 2017 09:25:34 -0000

status: open --> closed

#2 Access Denied error when trying to write more than 3 drives at once

Filip Sikora — Wed, 01 Mar 2017 09:24:42 -0000

status: open --> closed

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Filip Sikora — Wed, 22 Feb 2017 07:31:10 -0000

You are welcome. I'm glad it worked.

As for the second post - I will look into that, but no promises, it is not that simple.

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Toma — Wed, 22 Feb 2017 01:20:58 -0000

I understand that it is hard to mess with the data inside the operating system but the minor size mismatch is a real problem. Maybe, as a workaround we ask the user to shrink one of the partitions and you could implement an option to copy only the partitioned space and the boot sector. What do you think? Is this more feasible?

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Toma — Wed, 22 Feb 2017 01:12:04 -0000

It worked! It successfully wrote to the device. At this time I cannot test booting from the CF card because I do not have access to the computer. I will try in a week. In the mean time I will try on a couple of SD cards. Thank you for the nice product!

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Filip Sikora — Tue, 21 Feb 2017 21:34:10 -0000

Ok, so first things first.
Improvement/bugfix was made on imaging side, restoring should be fine. So you need to do your image again.
The message contains size difference in appropriate units (...the extra space (64kB)...)
* What you are refering to is extremely hard to implement (at least for me), filesystems are not that simple and I don't know, if it would be even possible. Also it could lead to much more dangerous errors, loss of data, etc..

Also the message says "the extra space does appear to contain data". This is also caused by the bug that was fixed, the extra space cannot possibly contain data.

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Toma — Tue, 21 Feb 2017 20:53:50 -0000

Thank you! I tested recovery of an old archive and it did not work. See the screenshot attached. Did you make improvements on the imaging step or restoring step? It would be useful if the error message would display the size missmatch in bytes instead of GB. Also if a size missmatch is found it may be useful if the program would discard a blank sector instead of the sector(s) at the end of the archeive. I realize that this may not be easy to implement because you need to read inside the file system.

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Filip Sikora — Tue, 21 Feb 2017 20:00:57 -0000

Ok, I may have found the issue. Please try newest debug build dotNet Disk Imager 0.7.339.23 debug and let me know how it works.

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Toma — Tue, 21 Feb 2017 16:24:59 -0000

Ok. They are the same. See the pictures attached.

#3 "Target Device hasn't have enough capacity" trying to clone identical CF cards

Filip Sikora — Tue, 21 Feb 2017 08:45:16 -0000

Well don't look on the Windows device properties, AFAIK it shows only actually availible(usable) capacity excluding the file system size. Look at device info in dotNet Disk Imager, it shows total device capacity including file system etc.. and compare the two devices size there.