You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment AFAICT they are shown in whatever order they are placed inside a file.
But at least for the mcupdates windows ships with, there's absolutely no regularity in the position of any single "entry" across different "whole file" releases.
This makes diffing slightly more annoying than I'd like.
Now, I don't really know how much important offset ordering is (so maybe changing this could not be a good default), but I'd like to see some way to have CPUID ordering.
The text was updated successfully, but these errors were encountered:
Yes, results are shown in the order they were regex matched, meaning offset based. It is what makes sense for an extractor utility as well. This can be solved in two different ways: adding support for a parsable output (e.g. json) or comparing the extracted firmware binaries themselves. Adding json is the proper way, but it requires time, so it's not a priority for me right now. I'll add it to the "todo" list though. For now, you can compare the output folders directly.
At the moment AFAICT they are shown in whatever order they are placed inside a file.
But at least for the mcupdates windows ships with, there's absolutely no regularity in the position of any single "entry" across different "whole file" releases.
This makes diffing slightly more annoying than I'd like.
Now, I don't really know how much important offset ordering is (so maybe changing this could not be a good default), but I'd like to see some way to have CPUID ordering.
The text was updated successfully, but these errors were encountered: