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.
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
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.
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
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)
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
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.