Segment Swap utility

[kur4o]

I did a quick test. So far no bugs found. I found some improvements like the ??? marks on invalid ascii characters and that debug screen is just great. It will make debugging much easier.

I think the search for "eeprom segments" might get a little better.

A 2 more search fields for searching will cover almost any situation.

Something like this
1. search for a5a5
search from 3c
OR
2.search for a5a5
search from 4d
and so on.

I think OR arguments will be good enough.

The compare function Might get a little more flexible too.
Now it is set to compare each byte vs each byte.

If we have that case

search for FFFFFFFFFFFFFFFF
and the data at search address is 22FF3456786546ed
It will fail to identify it as a valid segment because the second byte is a match.

If it compares it as a block it will be identified correctly.

Maybe adding a check box for per block compare and per byte compare will resolve some odd situations where identifications will be compromised.


I can`t believe we missed the save issue.

[joukoy]

I did a quick test. So far no bugs found. I found some improvements like the ??? marks on invalid ascii characters and that debug screen is just great. It will make debugging much easier.

I think the search for "eeprom segments" might get a little better.

A 2 more search fields for searching will cover almost any situation.

Something like this
1. search for a5a5
search from 3c
OR
2.search for a5a5
search from 4d
and so on.

I think OR arguments will be good enough.

The compare function Might get a little more flexible too.
Now it is set to compare each byte vs each byte.

If we have that case

search for FFFFFFFFFFFFFFFF
and the data at search address is 22FF3456786546ed
It will fail to identify it as a valid segment because the second byte is a match.

If it compares it as a block it will be identified correctly.

Maybe adding a check box for per block compare and per byte compare will resolve some odd situations where identifications will be compromised.


I can`t believe we missed the save issue.

I can add more flexibility to search, need little bit planning.

But it is not comparing byte by byte.
For example if searching FFFFFFFFFFFFFF, first it divides count of F's by 2 => 8.
So, it will read 8 byte/64bit number from given address and compare it to FFFFFFFFFFFFFF.
If it read FFFFFFFFFFFFFF it is a match. Unless "Match if NOT found" is checked, then it is not match.

Searched data must be 1, 2, 4 or 8 bytes, so I can use byte, ushort, uint and uint64 datatypes, no need for exotic functions.

[joukoy]

0.8.14

Sometimes less is more.
Removed "Search from:" in segment search config.
Configure searches like this: (first match is accepted)
a5a0:3c,a5a0:4c

Tested only shortly, will fix tomorrow if I broke it.

[kur4o]

I just test it and the issue I had on some of the older version seems to be cured. Now it identifies it positively on the first try per block. It must have been some bug that you have fixed already.

I tried the CTRL+a functionality for copying all the info on the text box but it is not supported. Is it possible to output a text file with the p/n info only, [no checksums maybe just print chksum good] on all the files in a folder. It will be nice to have a print of all the files with p/n vins vs file name. Very useful for large libraries with poor file naming used.

[kur4o]

0.8.14

Sometimes less is more.
Removed "Search from:" in segment search config.
Configure searches like this: (first match is accepted)
a5a0:3c,a5a0:4c

Tested only shortly, will fix tomorrow if I broke it.

So far it works, maybe add a5a0:3c:0 , a5a0:3c:1
:0 means matched if not found,
:1 means matched if found.

I always forget to ask you about saving on exit "setup segments", If the changes are not saved before exiting maybe print a message or add save and save as button.

[In-Tech]

0.8.14

Sometimes less is more.
Removed "Search from:" in segment search config.
Configure searches like this: (first match is accepted)
a5a0:3c,a5a0:4c

Tested only shortly, will fix tomorrow if I broke it.

Hi Guys,
Sorry to interrupt. I just read the 13 pages here and then perused back. Where is the link to download the latest versions? I'm using my wifi hotspot on my phone so T-Mobile throttles me pretty hard very quickly
-Carl

p.s. Roughneck, good to see ya bud

[Gampy]

In-Tech,
The download URL is in the first post on page 1 ...

joukoy,
I finally tried this, all I can say is wow, impressive!

[edit] Binchete - The Machete for BIN's.

I do have a question, What is the button under the 'Save As' button on the form 'Modify BIN'??

FYI, the 'Original app not developed any more' message above the download link is confusing.

[In-Tech]

I clicked this on page 1 https://github.com/joukoy/PCMDuctTape and got the dreaded 404 lol, I found it, thanks.
Small feel good victory, it works in XP too yay

[kur4o]

Here are the links for the 2 apps.

https://github.com/joukoy/UniversalPatcher

https://github.com/joukoy/PCMBinBuilder

I do have a question, What is the button under the 'Save As' button on the form 'Modify BIN'??

The save as, saves the modified bin file if you apply patch or swap segment.

[Gampy]

The save as, saves the modified bin file if you apply patch or swap segment.

Umm, The Save As button is obvious ... I'm talking about the button hiding underneath the Save As button!
There are TWO button there, use the tab key you'll find it!