SAD Version 5 (alpha)

All hardware related, disassembly / programming and code discussions belong here.
wwhite
Posts: 317
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)

Unread post by wwhite »

tvrfan wrote: 2023 Dec 18, 19:37 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)
That is from SAD Version 5.0.1 Alpha (17 Dec 2023) from command line.

If I do not include the .dir nothing is output in .msg file.

I'll attempt to debug myself for a bit.
BOOSTEDEVERYTHING
Posts: 234
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)

Unread post by BOOSTEDEVERYTHING »

I do not get anything in the msg file when not using a dir file either. Forgot to mention that.
tvrfan
Posts: 86
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)

Unread post by tvrfan »

Guys,
just released 5.0.2 which has fixes for problems reported so far.

Drag and drop now works as far as I can tell. Tested in virtual machine (Windows XP) on my Linux PC. It was caused by SAD not handling the file paths correctly ('cos I didn't even think of drag and drop, being a UNIX dinosaur. V4 worked more by good luck than design)
Sometimes SAD crashed as bin file was not found due to messed up file paths.

Several errors were incorrectly reported in _msg file. Fixed & tidied those up.
I added a new check. SAD wasn't checking for too many/too few data items ... which leads me to ...

BOOSTED - some of your lines in the eqe3.dir as posted ARE duplicates, but many of the reported ones were SAD bug. The duplicate generated with SYM .... [W] [Bx] should have returned "too many data items" because a symbol only ever has zero or one set of 'extra definitions' The format should be [W Bx] in a single set of brackets. SAD also mishandled even the correct format if the W appears before the B, causing more confusion. Fixed that.

On to next set of (my) mistakes !
tvrfan
Posts: 86
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)

Unread post by tvrfan »

--- Oops forgot to update version number and left in some debug stuff. Fixed. If you got it between this and last post, just download again ---
wwhite
Posts: 317
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)

Unread post by wwhite »

tvrfan wrote: 2023 Dec 21, 19:34 Guys,
just released 5.0.2 which has fixes for problems reported so far.
Now I get a bunch of this:

Code: Select all

## byte 	75f0 75f0
   ## Error - Commands Overlap

## word    7d36 7d37
   ## Error - Commands Overlap

## word    7d38 7d39
   ## Error - Commands Overlap

## timer   a841 a843 [ UW N]
   ## Error - Invalid Command at 'timer ' 
## timer   a844 a846 [ UW N]
   ## Error - Invalid Command at 'timer ' 
## timer   a847 a849 [ UW N]
The program does not complete, msg file is truncated, last line:

Code: Select all

## byte    c222 c222
   ## Error - Comman
Drag and drop works on Windows11
BOOSTEDEVERYTHING
Posts: 234
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)

Unread post by BOOSTEDEVERYTHING »

I get a dbg file and nothing in the lst or msg files. I downloaded the exe today 12/22 at 1:11 pm my time which is eastern standard time usa
jsa
Posts: 272
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)

Unread post by jsa »

I've reported a number of branch instruction logic issues.
tvrfan
Posts: 86
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)

Unread post by tvrfan »

Yep got that from jsa. Thanks.

a list of issues to fix, and appears I released a DEBUG version, which creates a (large) '<name>_dbg.txt' file. You can delete this safely. It doesn't change listing or message files.

(Damn...I thought v5 was doing well, but several things screwed up that I didn't see)

Ok - fixes coming soon....
BOOSTEDEVERYTHING
Posts: 234
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)

Unread post by BOOSTEDEVERYTHING »

I got the dbg file but nothing in the lst or msg files at all. It creates the files but they are blank.
tvrfan
Posts: 86
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)

Unread post by tvrfan »

If you get blank files, SAD may have crashed 'silently'.
This may sound nuts, but I have noticed over a long time that Windows occasionally doesn't pick up a crash with file related errors.
(in the same category as 'file not found' or "illegal write to file" types). So your program just 'disappears'.
Windows always seems to catch memory violations though (like an illegal pointer to nowhere) and pops up a crash window.
OR it still could be a bug somewhere in SAD which just terminates when it should not.
Post Reply