kur4o wrote:Since we are on the variables, Can we specify a variable value.
for example we type in the item field only var1=38 32;36 32; 34 32; 34 38 and use this in the search string or take a value for a variable from the bin, example var1=@00008000:2:hex.
It will be really useful when there are some different values for table lookup.
Version 0.12.13
Added new column for variables with 2 possible format:
var1=38 32;36 32; 34 32; 34 38
var1=@00008000:7
I checked the new var search and it looks something is broken. Can`t make it to work with old and new method. With new method the program hangs in some loop.
The the new hit search count is just great. I got alot more tables and the search issues seems to be gone now.
kur4o wrote:I checked the new var search and it looks something is broken. Can`t make it to work with old and new method. With new method the program hangs in some loop.
The the new hit search count is just great. I got alot more tables and the search issues seems to be gone now.
One possible reason for loop is empty search-config line. Version 0.12.14 ignores them
Variable handling fixed.
Thanks to some nice people that provide some nice files, new enhanced features are available. You can easily find tables from any ls1 OS by using the cross reference 7603 file. It is still work in progress not optimized at all.
Some cvn reference file is provided. And enhanced pid search for ls1, diesel pcms and v6 pcms which can be exported to csv. It prints the naming and we can fill the list with some conversion factor also but again work in progress.
You need the latest xml files for everything to work. So get those first.
Any feedback and questions are highly appreciated.
It looks like you found some weird bug. I looked at the file. Couldn`t find something wrong, looked at at debug log. Again it stops for no reason at the start of segment 3. Opens good all kind of other files with that OS and anything ls1 I can throw.
That sequence should be unique to AMD compatible OS'es ...
I suspect,
AAAA skip 2 bytes 5555 skip 2 bytes 9090
would suffice ...
Using OsID 125 87 603 as an example that first sequence would start at 0x77F0C in the binary.
It's actually the code that determines if the OS is running on Intel or AMD.
Those are some of the chip setup commands to get the chip ID.
-Enjoy
Last edited by Gampy on Fri Aug 14, 2020 1:43 am, edited 1 time in total.
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
I dig out more bins that don`t open with the last version of program, but opens good with previous versions[11.xx]. I suspect something is broken on the later release.
Gampy
AA AA * * 55 55 * * 90 90
is good enough for searching at least on the bins I checked.
On the latest version there is some custom search string that is the file info tab. You can enter the string there and check on the bins you have does it get some false hits and it can be added to some of the ls1 exceptions with labal AMD supported if found and INTEL only if not found.
