crazii wrote on 2023-04-05, 10:13:

Good News! With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug. Tested with a few gam […]
Show full quote

Good News!
With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug.
Tested with a few games all working, except that duke3d will freeze on exit, I don't think it's caused by SBEMU, probably VGA related, but I forgot to verify it without SBEMU, you guys can find it out.

SBEMU_VT8233_Fix.zip

i'm here to report back that SBEMU is now working fine on my setup with an VIA chipset.
crazii man, you doing here the lord's work. 😁

Me too, can confirm its working on VT8237R+!

Crazii, you know you are a genius and a legend alive? Great work! Thank you so much!

But there are still some glitches, duke3d is crashing some seconds after start of the game, being still in main menu. It's not related to some loading process but time related. If you skip the intro you can enter main menu otherwise it will crash in intro. And MechWarrior 2 can't find sound hardware in setup. But anyway, great work!

crazii wrote on 2023-04-05, 11:26:

When writing SBEMU, I have to search & learn documents about SB to make it work. I think Gravis would be the same, I believe the documents/programming guides can be found on the web, but I'm not ready to to that right now. Maybe later when SBEMU is more stable & compatible. It'll be good if you can help adding the GUS support 😁.

The guide should be the DOSBox source itself. You are already using it for sound blaster emulation so why not add it for GUS...

On my Audigy1 SE this only works when I enable the 'SB' command line switch in JEMMEX. What does that switch actually do, it says 'SoundBlaster driver compatibility mode' but not how it works.

Worked on my Teco TR3541 thin client with VT8233R, awesome!

crazii wrote on 2023-04-05, 10:13:

Good News! With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug. Tested with a few gam […]
Show full quote

Good News!
With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug.
Tested with a few games all working, except that duke3d will freeze on exit, I don't think it's caused by SBEMU, probably VGA related, but I forgot to verify it without SBEMU, you guys can find it out.

SBEMU_VT8233_Fix.zip

crazii wrote on 2023-04-05, 10:13:

Good News! With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug. Tested with a few gam […]
Show full quote

Good News!
With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug.
Tested with a few games all working, except that duke3d will freeze on exit, I don't think it's caused by SBEMU, probably VGA related, but I forgot to verify it without SBEMU, you guys can find it out.

SBEMU_VT8233_Fix.zip

SBEMU now works on the following laptop with this latest version.

The only issue is in Duke3D that the sound is a bit "fast", but not in other games tested so far (Doom e.g.).
Example: https://youtu.be/RrivvmKsScc

Laptop: Windows XP laptop with Intel Celeron 1.4 ghz running Windows 98SE 😀

Previous post: Re: SBEMU: Sound Blaster emulation on AC97

urbanus wrote on 2023-04-05, 20:01:

... The only issue is in Duke3D that the sound is a bit "fast", but not in other games tested so far (Doom e.g.). Example: https […]
Show full quote

...
The only issue is in Duke3D that the sound is a bit "fast", but not in other games tested so far (Doom e.g.).
Example: https://youtu.be/RrivvmKsScc
...

🤣 that accelerated Duke voice is funny

MBH wrote on 2023-04-05, 13:03:

But there are still some glitches, duke3d is crashing some seconds after start of the game, being still in main menu. It's not related to some loading process but time related. If you skip the intro you can enter main menu otherwise it will crash in intro.

I didn't got crash on the duke3d intro, during about a minute's testing in the intro. weird. But I also have glitches/speddown when loading games - that might be the IRQ sharing of USB & sound card because I'm using a USB stick to boot the thin client. The thin client has 32M Flash with WinCE installed so I didn't bother to install DOS on in.

georgel wrote on 2023-04-05, 13:18:

crazii wrote on 2023-04-05, 11:26:

When writing SBEMU, I have to search & learn documents about SB to make it work. I think Gravis would be the same, I believe the documents/programming guides can be found on the web, but I'm not ready to to that right now. Maybe later when SBEMU is more stable & compatible. It'll be good if you can help adding the GUS support 😁.

The guide should be the DOSBox source itself. You are already using it for sound blaster emulation so why not add it for GUS...

There're now two parts I directly used from DOSBox, the OPL emulation and the ADPCM decoding. I also read the SB emulation codes of DOSBox for help, but not directly use it. Either way I still need to dig a bit more to know how to use/make the GUS emulation. I'll do it when I'm ready. 😁

urbanus wrote on 2023-04-05, 20:01:

The only issue is in Duke3D that the sound is a bit "fast", but not in other games tested so far (Doom e.g.).

It might be a bug of the VT8233 driver, or a general SB emulation bug. what's the setup parameters of duke3d? bit/channel/sample rate settings? and what's the SB type you're emulating?

Hi!! ijust discover, and im starting to test in all my computers

THANKS A LOT

i have 2 question please

1- i did not succed to use with qemm, qemm load ok, but not sbemu, any triks? i found qemm much better than jemm

2- the scroll in some games is choppy, for example Pinball Fantasies, work ok witout sbemu, but as sooni activate sound blaster the scroll became bad

Any ideas?

Thanks!!!

I have a Termtek TK-3770 and I confirm that after latest VT8233 patch it works! I wasn't able to run Doom, Duke 3D (sound setup works) and History Line. I think many problems might be due to Jemmex not being compatible enough. I always had a lot of problems with it.

crazii wrote on 2023-04-06, 04:17:

urbanus wrote on 2023-04-05, 20:01:

The only issue is in Duke3D that the sound is a bit "fast", but not in other games tested so far (Doom e.g.).

It might be a bug of the VT8233 driver, or a general SB emulation bug. what's the setup parameters of duke3d? bit/channel/sample rate settings? and what's the SB type you're emulating?

The music has a normal pace, its only the sound effects that are fast. But in setup the center channel is normal, but right and left is fast.

Settings in pics, except for the one showing that I use 22khz (also tried 44khz, doesn't matter).

ill take a pic of what it dose on my laptop

crazii wrote on 2023-04-05, 10:13:

With the HP T5530, I fixed the bug for VT833 and now it's working - just overlooked a tiny bug.

I'm a bit late to to the party but I can confirm that it now works fine with the VT8237R+ in the Jetway J7F2. Thanks, amazing work!

Another positive compatibility report, it also works fine with the eBox-3350DX2 with a Vortex86DX2, which has an integrated HDA controller, detected as :

1Intel HDA: Vortex86MX (17F33010) -> Realtek (10EC0262) (max 192kHz/24bit/8ch)

urbanus wrote on 2023-04-06, 15:36:

Settings in pics, except for the one showing that I use 22khz (also tried 44khz, doesn't matter).

Looks like you configured Duke3D to use an SB16 but SBEMU to emulate an SB Pro, it needs to be T6 for SB16.

@crazii, I checked the SBEMU source and 2 /T mappings are not correct:

1//T1~T6 maps
2static const char* MAIN_SBTypeString[] =
3{
4    "0",
5    "1.0",
6    "1.5",
7    "2.0",
8    "Pro",
9    "Pro",
10    "16",
11};

T1 is SB 1.0/1.5 and T2 is SB Pro 1.0 with dual OPL2 (based on this page and this post) so this bit:

1    if(MAIN_Options[OPT_TYPE].value < 4) //SB2.0 and before

should be .value == 1 || .value == 3 (summarising).

theelf wrote on 2023-04-06, 06:12:

Hi!! ijust discover, and im starting to test in all my computers […]
Show full quote

Hi!! ijust discover, and im starting to test in all my computers

THANKS A LOT

i have 2 question please

1- i did not succed to use with qemm, qemm load ok, but not sbemu, any triks? i found qemm much better than jemm

2- the scroll in some games is choppy, for example Pinball Fantasies, work ok witout sbemu, but as sooni activate sound blaster the scroll became bad

Any ideas?

Thanks!!!

1 - there might be bugs. what's the message of the sbemu error?
2 - probably due to a poor CPU, what's the frequency of you CPU?

jtchip wrote on 2023-04-06, 23:21:

Looks like you configured Duke3D to use an SB16 but SBEMU to emulate an SB Pro, it needs to be T6 for SB16. […]
Show full quote

urbanus wrote on 2023-04-06, 15:36:

Settings in pics, except for the one showing that I use 22khz (also tried 44khz, doesn't matter).

Looks like you configured Duke3D to use an SB16 but SBEMU to emulate an SB Pro, it needs to be T6 for SB16.

@crazii, I checked the SBEMU source and 2 /T mappings are not correct:

Copy code to clipboard

1//T1~T6 maps
2static const char* MAIN_SBTypeString[] =
3{
4    "0",
5    "1.0",
6    "1.5",
7    "2.0",
8    "Pro",
9    "Pro",
10    "16",
11};

T1 is SB 1.0/1.5 and T2 is SB Pro 1.0 with dual OPL2 (based on this page and this post) so this bit:

Copy code to clipboard

1    if(MAIN_Options[OPT_TYPE].value < 4) //SB2.0 and before

should be .value == 1 || .value == 3 (summarising).

Thanks for the report and it helps. I was reading from another website and guess it was not accurate.

This software is so cool. Thanks crazii. Please let me know if there is a way to make a small financial donation.

For someone who is not that knowledgeable about DOS, I would like recommendations on what games to test. Maybe it is possible to set up a floppy with some shareware games. A methodical testing method is always good. (It's an occupational hazard.)

Baron von Riedesel wrote on 2023-04-04, 14:20:

crazii wrote on 2023-04-04, 09:24:

I merge the -x[n] code from your repo and I tested with system shock, it still exited on "not enough memory to make email cursor", weird. I then tested with Quake, the quake banner shows exact free memory according to the -x[n] option on each change of the [n] value, that means the options is working. Is there any additional modification needed?

Not with the version I tried - it's v1.6, located as a bonus on an CD inserted in a computer magazine.

I was testing with this demo version: https://archive.org/details/SSHOCK
tried with -x2 to -x5 none of them works.