Good.
Tough from the data on your report it seems like no conclusion can be drawn, I mean you have two "same" files "diversely" fragmented but both into 19 segments and one is good and the other ones is not.
I can understand that when the file is overly fragmented (more than n fragments) it would have issues, but with the same number of fragments it is "queer", unless there is also a factor with the single fragment(s) being over (or below) a given size.
In your first (not working) file, you seem like having a "huge" first chunk (like half of the size) followed by 18 small chunks, maybe that is part of the issue?
BTW, with reference to the suggestion to yaya "You will need to install - then find the MyFragmentor.exe file." and for the record, the MyDefrag-v4.3.1.exe is an InnoSetup installer, contents can be extracted with Uniextract (tested):
https://www.legroom....ware/uniextract or (most probably, not tested) UniExtract2 :
https://github.com/B...tract2/releases Also InnoUnp (just tested):
http://innounp.sourceforge.net/ Run as follows:
innounp.exe -t MyDefrag-v4.3.1.exe
will list all files, since the package is for both 32 bit and 64 bit there are two files listed:
...
#2 {app}\MyFragmenter,1.exe
#4 {app}\MyFragmenter,2.exe
...
The 32 bit is the second one so:
innounp.exe -x MyDefrag-v4.3.1.exe {app}\MyFragmenter,2.exe
Output:
; Version detected: 5309 (Unicode)
#4 {app}\MyFragmenter,2.exe
Reading slice C:\dummy2\MyDefrag-v4.3.1.exe
Then you need to rename the MyFragmenter,2.exe in subfolder {app} to Myfragmenter.exe.
Wonko