Questions about new Graph capability in DTC
Posted: Tue Apr 24, 2018 1:14 pm
Thanks for the new release 2.72 of DTC.
I am particularly interested by the new graph capability. I have read carefully the documentation and I would appreciate if you could clarify some points.
First I do not understand the meaning of “Heat map” graph. I have looked for definition at a dictionary (http://www.wordreference.com/enfr/heat%20map) and I can see a lot of “heat something” (e.g. heat engine, heat cramp, heat lamp, …) but no heat map. I suspect that you have called the flux reversal scattered chart like this to indicate how “hot” are the transition?
Now about the graph content I first an easy question: in the scattered chart the flux dots are mostly in blue but some are in red (and may be some other color?), what is the meaning of the colors?
About the “consistency bars”: You indicate that “Each horizontal bar” represents one revolution. I only see one big green bar so I suspect that this is because there are 5 horizontal bars that are merged together without separation? So if inside this big bar I see some red dots or lines their locations are based on inconsistencies for horizontal position and revolutions for vertical position.
You indicate that some copy protections like weakbits and Non flux area produces inconsistent data but I believe this is not the case for NFA. About the weakbits if they are obtained by partially unformatted areas we get indeed inconsistent data and they are clearly indicated in red in your graph. But for what you call programmed/predictable weakbits (Dungeon Master) there is no indication of inconsistency. I first thought that you had programmed a special detection for DM but to better understand I did a test on “DrT protected diskette” (described in detail in my protection document page 57) that use a totally different scheme of sliding predictable weakbits (you only get pseudo randomly $00 or $01 bytes) and here again you do not detect any inconsistency. Therefore, I would be interested to know what kind of analysis you are performing to detect inconsistencies, I suspect that you use some sort of correlation analysis?
On page 28 the d) paragraph is hard to understand but I think I got it. However, the black line drawn on the graph is a bit mysterious. I guess you want to indicate that if “YOU” can trace an uninterrupted line in the consistency graph you have some chance to read correctly, but if this line is interrupted by a complete vertical line you are out of chance.
Also not related I have a question about image type. When and why you use 0a type versus 0 type?
What is the difference in the output is you use “–fstreamfile –i0 –i4” and “–fstreamfile –i0a –i4”?
What is the difference in the output is you use “–fstreamfile –i0” and “–fstreamfile –i0a”?
Aufit graph
I am particularly interested by the new graph capability. I have read carefully the documentation and I would appreciate if you could clarify some points.
First I do not understand the meaning of “Heat map” graph. I have looked for definition at a dictionary (http://www.wordreference.com/enfr/heat%20map) and I can see a lot of “heat something” (e.g. heat engine, heat cramp, heat lamp, …) but no heat map. I suspect that you have called the flux reversal scattered chart like this to indicate how “hot” are the transition?
Now about the graph content I first an easy question: in the scattered chart the flux dots are mostly in blue but some are in red (and may be some other color?), what is the meaning of the colors?
About the “consistency bars”: You indicate that “Each horizontal bar” represents one revolution. I only see one big green bar so I suspect that this is because there are 5 horizontal bars that are merged together without separation? So if inside this big bar I see some red dots or lines their locations are based on inconsistencies for horizontal position and revolutions for vertical position.
You indicate that some copy protections like weakbits and Non flux area produces inconsistent data but I believe this is not the case for NFA. About the weakbits if they are obtained by partially unformatted areas we get indeed inconsistent data and they are clearly indicated in red in your graph. But for what you call programmed/predictable weakbits (Dungeon Master) there is no indication of inconsistency. I first thought that you had programmed a special detection for DM but to better understand I did a test on “DrT protected diskette” (described in detail in my protection document page 57) that use a totally different scheme of sliding predictable weakbits (you only get pseudo randomly $00 or $01 bytes) and here again you do not detect any inconsistency. Therefore, I would be interested to know what kind of analysis you are performing to detect inconsistencies, I suspect that you use some sort of correlation analysis?
On page 28 the d) paragraph is hard to understand but I think I got it. However, the black line drawn on the graph is a bit mysterious. I guess you want to indicate that if “YOU” can trace an uninterrupted line in the consistency graph you have some chance to read correctly, but if this line is interrupted by a complete vertical line you are out of chance.
Also not related I have a question about image type. When and why you use 0a type versus 0 type?
What is the difference in the output is you use “–fstreamfile –i0 –i4” and “–fstreamfile –i0a –i4”?
What is the difference in the output is you use “–fstreamfile –i0” and “–fstreamfile –i0a”?
Aufit graph