Segment Swap utility

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

kur4o wrote: I noticed that theinfo from the extra info field is not loaded in the info tab.
??
Attachments
extrainfo.JPG
extrainfo.JPG (18.32 KiB) Viewed 4145 times
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

kur4o wrote: Can we add some version information for the config xml files that will be visible and editable when it is loaded. Like version 1,2,3 and so on.
Added in 0.8.17
Free text: version can be 1,2,3 or A1.B3 or Myowntestversion ... whatever, info only
kur4o
Posts: 950
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Post by kur4o »

I mean in the "File info" tab. I guess it was misspelled.
It will be cool to make more data available on the "File info" tab like some checkboxes to include 1.segment range, 2. segment size, 3. checksum 1 or 2.

I guess the cvns are more important to be included for stock files verification.


Can we improve some of the patch side. I will really like to be able to make a patch files manually, maybe some standard can be made.

Like

$5645:"5A 78 55 6B 0D FC"

And add some config lines.

First line defines the xml used, like e38.xml
second line defines OS it can be applied to, it can be multiple Oses defined with : between them


I have another idea that can be set as an exception for table extractions but the ini file maybe be more suitable there.
Like extract a table as a patch, for example high octane spark table and specify different apply address for different OS
OS1:$5678,OS2:$9876,OS3:$8907
kur4o
Posts: 950
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Post by kur4o »

Maybe we can specify different types of patches.

type 1 regular patch done from the application.
type2 manual patch
type3 table extraction.
Maybe other types can be specified later
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

Adding lot of buttons in one form is not a good idea.

How this should be divided?
- More tabs/move buttons to tabs
- Return "Main window" where is only buttons to patcher, segment config etc
- Remove buttons and add menu
- Other ideas?
kur4o
Posts: 950
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Post by kur4o »

I think, keep the design as simple as possible.

Adding some global settings for the application might do the trick for some specific pre-configurations.
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

kur4o wrote: I have another idea that can be set as an exception for table extractions but the ini file maybe be more suitable there.
Like extract a table as a patch, for example high octane spark table and specify different apply address for different OS
OS1:$5678,OS2:$9876,OS3:$8907
Segments are configurable, what segment should be used for comparing OS version?
Check all segments and check if P/N match?
Check only segment where segment name is "OS" ?
kur4o
Posts: 950
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Post by kur4o »

Check all segments and check if P/N match?
This option might cover all cases.

Some force apply can be set too,
like ALL:$5678
in case there is no need for checking p/ns on earlier pcms.

We can also specify different xmls for the same patch,
like
ls197-98.xml,p01-p59.xml,and so on.
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

0.9.0

Massive update.
Patches are now in XML-format, should be easy to edit by hand.
Attachments
Samplepatch.txt
(614 Bytes) Downloaded 162 times
User avatar
joukoy
Posts: 392
Joined: Tue Dec 17, 2019 3:27 am
cars: --
Contact:

Re: Segment Swap utility

Post by joukoy »

UniversalPatcher 0.9.1
UI fixes, resize etc.
Post Reply