SAD Version 5 (alpha)
-
- Posts: 88
- Joined: 2023 Oct 22, 22:13
- Location: New Zealand
- Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.
EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler
SAD Version 5 (alpha)
Guys,
have just released latest SAD, version 5.0.1 to github/EEC-IV-disassembler.
Have added a some new features and done a big tidy up. Most likely still some bugs, but I want you guys to play with it and give me feedback.
This version has new syntax with math calculations and multi bit fields are supported. Can also use a field more than once for printing offsets and such. (old syntax still supported, so should still work with existing command files etc.)
have just released latest SAD, version 5.0.1 to github/EEC-IV-disassembler.
Have added a some new features and done a big tidy up. Most likely still some bugs, but I want you guys to play with it and give me feedback.
This version has new syntax with math calculations and multi bit fields are supported. Can also use a field more than once for printing offsets and such. (old syntax still supported, so should still work with existing command files etc.)
-
- Posts: 242
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: SAD Version 5 (alpha)
Just a quick run with my current dir file and no cmt file gives me a bunch of errors I was not getting with the previous version. Posted up a zip with my files I am using. It is most likely me, but I figured I would report it anyways. Thank you for working in this new version.
- Attachments
-
- eqe3SADv5.zip
- (411.57 KiB) Downloaded 123 times
-
- Posts: 88
- Joined: 2023 Oct 22, 22:13
- Location: New Zealand
- Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.
EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler
Re: SAD Version 5 (alpha)
Thanks for being so quick !!
I normally blame jsa for these kind of faults so you have obviously formed a tag team !! (...joking...)
Seriously - I'll check those out against your commands file. I admit I tend to do less testing on the dirs/commands parsing as main thing for me is to try to get main binary analysis working as correctly as possible. There are still some bugs that I know of, but I decided to release it anyway, otherwise I'll be delaying it forever... looks like a 5.0.2 might be out faster than I thought....
I normally blame jsa for these kind of faults so you have obviously formed a tag team !! (...joking...)
Seriously - I'll check those out against your commands file. I admit I tend to do less testing on the dirs/commands parsing as main thing for me is to try to get main binary analysis working as correctly as possible. There are still some bugs that I know of, but I decided to release it anyway, otherwise I'll be delaying it forever... looks like a 5.0.2 might be out faster than I thought....
-
- Posts: 242
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: SAD Version 5 (alpha)
LOL. No problem at all. I just figured I would give it a shot while I was on my computer anyways. Like I said, it may just be me or something I am doing wrong. Also, forgot to mention that it doesn't seem to want to work with the drag and drop method. I had to run the exe file and type in the file name. That could also be something I am doing wrong.
Also, it does not seem to pay attention to the byte locations on the SYM commands. Does not label them correctly, also does not break them out in the lst file.
Also, it does not seem to pay attention to the byte locations on the SYM commands. Does not label them correctly, also does not break them out in the lst file.
-
- Posts: 283
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: SAD Version 5 (alpha)
LOL, always important to send the 1st report before TVRfan's screensaver has kicked in!
-
- Posts: 242
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: SAD Version 5 (alpha)
LOL. Oh man...I just noticed how quick I really was to post that. Sorry. Didn't mean to throw it at you that fast.
-
- Posts: 88
- Joined: 2023 Oct 22, 22:13
- Location: New Zealand
- Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.
EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler
Re: SAD Version 5 (alpha)
Hey, nuthin' like enthusiasm !! No worries. I'm waiting for feedback anyway....
OK - quick scan - some of those commands ARE duplicates, but some are not. Quick check is that each symbol command needs to have something different somewhere in the command, and so from what SAD came back with, couple of examples -
SYM 0007 "ATOD_TIMED_CMD" #UY
SYM 0007 "ATOD_TIMED_RESULT" #UY IS a duplicate - correct
SYM 0015 "LSO_EXP_A" :W #UY
SYM 0015 "LSI_EXP_A" #UY IS NOT a duplicate, so SAD got that wrong....a mistake with read and write somewhere to find....
so some work for me to do....................
OK - quick scan - some of those commands ARE duplicates, but some are not. Quick check is that each symbol command needs to have something different somewhere in the command, and so from what SAD came back with, couple of examples -
SYM 0007 "ATOD_TIMED_CMD" #UY
SYM 0007 "ATOD_TIMED_RESULT" #UY IS a duplicate - correct
SYM 0015 "LSO_EXP_A" :W #UY
SYM 0015 "LSI_EXP_A" #UY IS NOT a duplicate, so SAD got that wrong....a mistake with read and write somewhere to find....
so some work for me to do....................
-
- Posts: 321
- Joined: 2021 Feb 16, 15:53
- Location: Victoria, BC, Canada
- Vehicle Information: 1994 Flarside, XLT, 351w E4OD
SD48b, Quarter Horse, Burn2
Re: SAD Version 5 (alpha)
Doesn't work at all for single bank KID2 (LHBH1) for me.
A lot of the following:
A lot of the following:
Code: Select all
## word 200a 200f
## Error - PANIC - Row size is ZERO !!
## vect 2010 201f
## Error - PANIC - Row size is ZERO !!
## byte 2020 2021
## Error - PANIC - Row size is ZERO !!
## word 2022 2031
## Error - PANIC - Row size is ZERO !!
## vect 21ce 2269
## Error - PANIC - Row size is ZERO !!
## vect 22c8 22c9
## Error - PANIC - Row size is ZERO !!
## word 2350 2351
## Error - PANIC - Row size is ZERO !!
-
- Posts: 88
- Joined: 2023 Oct 22, 22:13
- Location: New Zealand
- Vehicle Information: Several Kit cars, Ford (Europe), EEC-IV, TVR Vixen, Tasmin (a.k.a Wedge),
Engine - Cologne 2.8 V6 (Europe) catch code 'AA'.
EEC_Disassembler https://github.com/tvrfan/EEC-IV-disassembler
Re: SAD Version 5 (alpha)
Thanks wwhite - is that from reusing SAD's _msg file , or from your dir ?? If I can't repro this, I may ask to you send me your dir file, if that's OK? (via PM if you prefer)
To all - I'll collect a few bugs and then fix them together.
A GENERAL QUESTION FOR ALL SAD USERS
jsa reported an error with paths - he told me he uses 'drag and drop' quite a lot on windows. I have tested 'open with' too
and it seems to fail the same way. (I would guess they do the same thing under the covers). This is where my UNIX and Linux background shows up, and I don't use these methods, so I didn't think to test them....
Do you guys use these methods or run SAD via SADwin ?? I am asking because the 'drag & drop' and 'open with' methods typically don't have extra options, (like paths) and this would mean adding a rule that my config file (sad.ini) MUST be in the same place as SAD.exe so that their paths are the same. Everything else, all the bins and listing etc could still be in separate places... I don't want to start fiddling with the Win registry and want to keep same code for windows and linux....
Any comments ?? [Thanks in advance]
To all - I'll collect a few bugs and then fix them together.
A GENERAL QUESTION FOR ALL SAD USERS
jsa reported an error with paths - he told me he uses 'drag and drop' quite a lot on windows. I have tested 'open with' too
and it seems to fail the same way. (I would guess they do the same thing under the covers). This is where my UNIX and Linux background shows up, and I don't use these methods, so I didn't think to test them....
Do you guys use these methods or run SAD via SADwin ?? I am asking because the 'drag & drop' and 'open with' methods typically don't have extra options, (like paths) and this would mean adding a rule that my config file (sad.ini) MUST be in the same place as SAD.exe so that their paths are the same. Everything else, all the bins and listing etc could still be in separate places... I don't want to start fiddling with the Win registry and want to keep same code for windows and linux....
Any comments ?? [Thanks in advance]
-
- Posts: 242
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: SAD Version 5 (alpha)
I use the drag and drop method. That is mainly because it is fast and easy and I am keeping the files I am working with in their own subdirectories anyways. That being said I am very new at this and my opinion should be the last one you consider. But, drag and drop was working really well on the old version, I was even able to run it on my computer at work from a thumb drive that I have been keeping my files on for now.Any comments ??