Last edited by ronny1982; 06-03-12 at 10:56 AM.
It's verision 1.3.6 build 2265, but like I said the newest version of sELedit wont open it, says that there is a mismatch.
Ronny, any chances for 1.3.6 -> 1.4.4 export / merge?
i don't recommend upgrading from 1.3.6 to 1.4.4 there are ton's of new fields that have to be filled with default values, and i doubt that this will not break the file
and to answer your question, i don't add a rules file for 1.3.6 -> 1.4.4 in sELedit, focus is now 1.4.4
Major Update for sELedit
- name scheme and parameters for *.cfg files and *.rules files has been changed
- element structure diff tool has been added (GUI for creating rules)
Element Structure Diff
Last edited by ronny1982; 20-08-12 at 12:43 AM.
About Configuration Files...
Since many people request configuration files, here some statements...
Some rough hints how you can basically analyze them:
*would be nice if someone could make a detailed guide with pictures
- open the latest available elements.data file in sELedit (for comparsion)
- check the version of the new elements.data file (sELedit->Tools->EL Version)
- create a copy of the latest configuration file and name it related to the new el version (i.e. PW_1.4.5_v66.cfg -> PW_1.4.5_v69.cfg)
- open the copied configuration with an text editor
- next is trial & error, we need to find out which lists have changed
- set the first number in the configuration file to maybe 10 (this will tell sELedit to only load 10 lists)
- save the configuration file, open a another instance of sELedit and load the newest elements.data file
- if everything goes well, 10 lists will be loaded, walk through each list and check if the values are ok
- check the behavior:
- if a list seems not ok, or an error occurred during loading go back to the text editor with the configuration file and reduce the number to maybe 5 and repeat until you found the list causing errors
- if list seems ok and no error occurred go back to the text editor with the configuration file and increase the number to maybe 20 and repeat the check
- when you found a list causing errors you need to check the new elements.data file in a hex editor
- take a look into sELedit with the old elements.data and go to the list causing errors in the new elements.data
- take the id (or other distinct values) of first and second item in the list and try to locate them in the hexeditor
- now compare the entrys between the hexeditor and sELedit (old elements.data)
- if you locate the new data types in the list insert them to the configuration file, increase the list number at the top of the file and reload the new elements.data in the second instance of sELedit
To encourage people making configuration files i've added an experimental feature to sELedit, which analyze a new elements.data file by using an older configuration file.
- download latest sELedit
- open sELedit->Tools->Config Editor
- in the Configuration Editor goto File->Load and open the latest configuration file
- now goto File->Scan Sequel and open the newest elements.data file
- if list 99 popup, click yes (hope pw will not change that list soon)
- if everything works, a log file will be opened, viewing info about each list
- look out for the "Changed entry size", in these lists you need to add fields (i.e. size +12 -> add 3x int32, or 3x float, or byte:12,...)
- check the end of the log file, if bytes are left, this might be an indicator for additional lists
this report shows information which will save you time and effort finding the changes, but you still need to edit the configuration file and also use a hex editor for structuring new lists...
This was moved a long time ago:
pw-tools - pwTools - Google Project Hosting
There are also several other posts pointing to this new location