It's on my CT2290 card. I searched topics about identifying the DSP version. It is said that there should be something like v4xx printed on the chip, but mine doesn't match the format.
if you run DIAGNOSE.EXE it will report the version , it's part of the DOS drivers
keropi wrote on 2024-02-01, 17:54:if you run DIAGNOSE.EXE it will report the version , it's part of the DOS drivers
DIAGNOSE.EXE says it's v4.13, but I'm very confused now because I have another card which is an AWE32 CT3990, which has a v4.13 DSP too. The printing on the DSP chip of this card, however, is very different from that on CT2290.
What I'm doing now is trying to trigger the hanging note bug. V4.13 DSP is known to affected by this bug. I've confirmed this bug(type 1+2) on CT3390 by running Hexen -warp 02. However, I can't trigger it successfully on CT2290, be it type 1 or type 2. If they both have the same DSP version, it shouldn't have this different result, should it?
GunKneeNeon wrote on 2024-02-01, 19:45:What I'm doing now is trying to trigger the hanging note bug. V4.13 DSP is known to affected by this bug. I've confirmed this bug(type 1+2) on CT3390 by running Hexen -warp 02. However, I can't trigger it successfully on CT2290, be it type 1 or type 2. If they both have the same DSP version, it shouldn't have this different result, should it?
According to this page on the Vogons wiki, your CT2290 card isn't affected by the Type 1 hanging note bug, due to having the CT1747 bus interface.
It only has the Type 2 hanging note bug, and the stuttering issue with high sample rates (Duke3D etc).
Joseph_Joestar wrote on 2024-02-01, 19:57:It only has the Type 2 hanging note bug, and the stuttering issue with high sample rates (Duke3D etc).
I thought I can trigger the type 2 bug by Hexen -warp 02. But it didn't, however long time it runs. So is there an guaranteed way to trigger the type 2 bug?
