VOGONS


The Soundblaster DSP project

Topic actions

Reply 540 of 1109, by mattw

User metadata
Rank Oldbie
Rank
Oldbie
Maelgrum wrote on 2023-10-04, 13:06:

Logs are dumped on each line
Scanning process not stops on first found

log attached from that version - attached - all failed. currently testing Starge5, will report back soon...

Reply 541 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member

One more time please !
I feel we are very very close ...

Reply 542 of 1109, by Gmlb256

User metadata
Rank l33t
Rank
l33t
Maelgrum wrote on 2023-10-04, 13:17:

And stage 5, with another search.
This log and previous log (one post up) i hope gives exact address location.

Stage 5 log, same results as with Stage 4. Now testing the recent versions of both.

VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce2 GTS 32 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS

Reply 543 of 1109, by mattw

User metadata
Rank Oldbie
Rank
Oldbie
Gmlb256 wrote on 2023-10-04, 13:33:

Stage 5 log, same results as with Stage 4. Now testing the recent versions of both.

same here, but attaching it anyway... OK, going to run "sbcrack_st5.zip " and "sbcrack_st4.zip"...

Reply 544 of 1109, by Gmlb256

User metadata
Rank l33t
Rank
l33t
Maelgrum wrote on 2023-10-04, 13:28:

One more time please !
I feel we are very very close ...

New logs, no success from both.

VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce2 GTS 32 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS

Reply 545 of 1109, by mattw

User metadata
Rank Oldbie
Rank
Oldbie

I guess good news from my side: "sbcrack_st5.zip" - gives several passes - the log as usual - attached. P.S. "sbcrack_st4.zip" - are all "failed" for me.

[EDIT] but we have maybe now too many "passes", I counted 37:

$ cat LOG.TXT | grep pass | wc -l
37

Reply 546 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member
Gmlb256 wrote on 2023-10-04, 13:53:
Maelgrum wrote on 2023-10-04, 13:28:

One more time please !
I feel we are very very close ...

New logs, no success from both.

On stage 4 - It must see old matches - 0x1183, 0x116c
Looks like it in invalid internal state.
Will previous version give positive match - 0x1183, as it was ?

Reply 547 of 1109, by mattw

User metadata
Rank Oldbie
Rank
Oldbie
Maelgrum wrote on 2023-10-04, 14:10:

Will previous version give positive match - 0x1183, as it was ?

0x1183 is failed for me with ST4 version.

Reply 549 of 1109, by georgel

User metadata
Rank Member
Rank
Member

Why not try address search on 4.13 and see if sbcrack finds correct addresses that you already know?

Reply 550 of 1109, by mattw

User metadata
Rank Oldbie
Rank
Oldbie
Maelgrum wrote on 2023-10-04, 14:14:

May be power off/on needed ?

always, do that.

georgel wrote on 2023-10-04, 14:15:

Why not try address search on 4.13 and see if sbcrack finds correct addresses that you already know?

I was doing to suggest the same, i.e. test if "E3-search-algo" works with V4.13, because V4.13 we know what it is supposed to return.

Last edited by mattw on 2023-10-04, 14:17. Edited 1 time in total.

Reply 551 of 1109, by Gmlb256

User metadata
Rank l33t
Rank
l33t

I will try again to see if there is any difference with the recent versions.

Last edited by Gmlb256 on 2023-10-04, 14:41. Edited 2 times in total.

VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce2 GTS 32 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS

Reply 552 of 1109, by S95Sedan

User metadata
Rank Member
Rank
Member
georgel wrote on 2023-10-04, 14:15:

Why not try address search on 4.13 and see if sbcrack finds correct addresses that you already know?

If needed i can put in a 4.13 one so you dont have to keep switching stuff around.
Just need to know which version (stage) to use for probing.

Reply 553 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member

Ok, we can try to make it with 4.13. Its reasonable suggestion. But tomorrow ))

Reply 554 of 1109, by georgel

User metadata
Rank Member
Rank
Member

What do you assume SP to be at MIDI byte write routine in 4.16?

Reply 556 of 1109, by S95Sedan

User metadata
Rank Member
Rank
Member
mattw wrote on 2023-10-04, 14:29:
yep, lets rest and think about it for awhile. BTW, about 1183 - I mentioned here that it stopped giving "passed" result: […]
Show full quote
Maelgrum wrote on 2023-10-04, 14:21:

But tomorrow ))

yep, lets rest and think about it for awhile. BTW, about 1183 - I mentioned here that it stopped giving "passed" result:

Re: The Soundblaster DSP project

but the 1st version still gives "passed" for me on 1183.

Best would be to go by stage i recon, using 4.13 as 'known result' and put 4.16 next to it.
The offset should be known (as that was the first test i believe?) and based on the known code decompile for 4.13 you can approximate in which section of the code you are. (assuming it didnt change drastically)
(Hopefully that makes sense)

Last edited by S95Sedan on 2023-10-04, 14:39. Edited 1 time in total.

Reply 557 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member
georgel wrote on 2023-10-04, 14:29:

What do you assume SP to be at MIDI byte write routine in 4.16?

0xC0 at command loop
0xC2 at entering midi loop
0xC4 in midi byte write routine

Reply 558 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member

Thanks to all this massive testing !

Reply 559 of 1109, by Maelgrum

User metadata
Rank Member
Rank
Member
mattw wrote on 2023-10-04, 14:29:
yep, lets rest and think about it for awhile. BTW, about 1183 - I mentioned here that it stopped giving "passed" result: […]
Show full quote
Maelgrum wrote on 2023-10-04, 14:21:

But tomorrow ))

yep, lets rest and think about it for awhile. BTW, about 1183 - I mentioned here that it stopped giving "passed" result:

Re: The Soundblaster DSP project

but the 1st version still gives "passed" for me on 1183.

Thats strange, what last version gives nonsense, but old gives something more sane. Will look into this.