Will try now with a debug build, but so far, I've got this. Thread 33 received signal SIGSEGV, Segmentation fault. [Switching to Thread 12632.0x2948] 0x005bb0ea in sb_get_buffer_emu8k () (gdb) bt #0 0x005bb0ea in sb_get_buffer_emu8k () #1 0x0057bce4 in sound_poll () #2 0x005c4ebf in timer_process ()...

These instructions are in an incorrect order: $ ./configure --enable-networking --enable-release-build $ autoreconf $ mingw32-make -j autoreconf (preferably with the -i parameter), comes before the ./configure line, as basically autoreconf will regenerate the configure script. And this is incorrect ...

it is strange, indeed, but also because it's not what happens here: config.sys: c:\sbpro\drv\ctsbpro.sys /unit=0 /blaster=a:220 i:5 d:1 c:\sbpro\drv\ctmmsys.sys autoexec.bat: (this line is supposed to restore the mixer settings previously saved with the sbpset DOS mixer application) c:\sbpro\sbpset ...

I tested with V13.1 release, and with the current development version and I get sound. I even created a new machine (and hard disk) without the drivers installed, and there, test-sbp works fine. (My previous one has another version of the soundblaster pro drivers that didn't have test-sbp, but which...

It's strange...
I have to investigate a bug where configuring some applications to use a soundblaster pro, and having a soundblaster 16 or AWE32 on the machine setup doesn't produce sound, but your case worked here on the applications that I tried.

Can you tell the names of those that fail?

I tested the patch here and worked as expected. The only downside is that it is quite slower than building with the Makefile file. The reason is because the generated Makefile continuously forks "sh" and other commands (standard behaviour), which under msys2 (Windows) is quite slow. I even...

Ok, after serveral executions, it seems that it is more a problem of incorrect initialization, and sometimes it just plays incorrectly.
There was a similar issues with Doom too, that was solved during development.

I will try to check what happens in the following days

After trying it, I believe the problem is that you run Duke Nukem from Windows. I could reproduce your bad sound running it from inside Windows. Boot up to DOS and it will work fine. The reason why this could matter is that the EMU8000 (the music chip in the AWE32) needs to be controlled directly by...

leilei wrote: ↑Sun 04 Feb, 2018 8:03 pm

Code: Select all

onesec
New CD command 12 446892401
New CD command 5A 446965045
New CD command 5A 446985185

On a side note, I don't know if you have some reference for the ATAPI commands.
I could find this wiki on internet:
https://wiki.osdev.org/ATAPI

First, as Sarah told you, ensure that you have configured Duke nukem 3D to use the AWE32, instead of the FM/OPL audio or any other setting. Then, be aware that the AWE32 emulation is not perfect. I have been improving it for the release v13 specially in regards to its envelopes and LFOs, as well as ...

@TheMechanist: try running autoreconf -i first if ./configure isn't enough

As for the OpenAL32.dll, It also performs badly here. A direct replacement is removing it and placing msys2 libopenal-1.dll in PCem's dir (not even needed to rename it).

omarsis81: I suggest you to try the openGL (either the normal, or the GL3) video modes instead of the older ones.
Then, use the scale filtering, output-stretch mode and maybe even the output scale options from the Video menu.

I don't know if it is really a bug, but in order to make it work now, you need to go to "integrated peripherals" section of the BIOS, and there, Enable "Onboard FDD controller".

I can only confirm that there seems to be some type of problem. In my case I have an original Windows NT 4 Workstation (bought in 1997 which came with Windows 95 too. I never used any of them, because they sent me an Italian version instead of Spanish). I tried installing it in PCem and works, but a...

@szadycbr : There were some changes to the floppy controller. I also experienced problems running it under a windows host.
My solution consisted in going into the guest bios , there into integrated peripherals, and there enable onboard FDD controller.

Give it a try.

Recently, PCem has an option to configure the IDE controller. It is required to be setup (currently it doesn't have a default setting) and you need to do so from the new wxwidgets interface (the older interface is going to be removed for v13). Alternatively, add this line to the config file: hdd_con...

@bighitti90 : Most probably you still have the cd Image loaded into pcem. See the menu "CD-ROM" and set it to empty. Or if you used a floppy to load the CD, then you might also need to remove the floppy. See Disk: eject Drive A

"Assert" is a coding condition that the developer explicitly sets in order to ensure that something is not going to happen, and if it happens, stop the execution. Since the intention is to correct a condition that should not have happened, what you see is the line of code where the assert ...

leilei: Seems Sarah fixed it on head (i.e. the patch has an error). I forgot to remove the right shift that was used to compensate the volume multiplication.
She also fixed a couple more bugs. I'm sorry for that.

I confirm that the weird notes at e1m2 are still there, so it seems i'll need to debug it.

This is a follow up from the previous post . Here is all that is included in the patch: - More configuration options for the soundcards ( emu address, old SBs address, configuration of mixer specific address for SB 2.0 CD). I've also made it possible to configure IRQ and DMA for SB16, although I hav...

Mmm... Yes, I think i've heard a few cases (not only in doom) of that problem, but after the chorus fix, it seemed to work well.
I will keep an eye on it to see if I get to reproduce it, since it seems a bit random.

Re: floppy.
Some revisions ago, I had to enter into the bios setup and enable the option "Onboard FDD controller" under integrated peripherals. Else, it would show a warning on boot up.
To me, the pcem-emulator repository sources are working with that option.

Another update: Running it from inside windows 98 works. And also works when running in MS-DOS mode ( F8 on boot up ). So I believe that this is more like some incompatibility coming from somewhere, or a patched game. Sorry for the noise. It might still be of help to others if they end finding that ...

Mmm.. curious...

If I use the FDOS driver, with or without the cdrcache.sys, it works.

If I load the GSCDROM with the cdrcache (either with mscdex or shsucdx) it works, but if not (either with mscdex or shsucdx) it crashes.

When loading, they say " E-IDE/ATAPI CD-ROM device driver ver 1.25" "Copyright LG Electronics Inc 1997. All rights reserved"
Filename is GSCDROM.SYS, loaded with Microsoft's MSCDEX.

I'll try now to load it with FDOS's SHSUCDX to see if it is the loader or the driver.

Just if it serves as any guideline: I have a friend that had Prince of persia on a 286 at 12MHz (12 IIRC) with a CGA display (Don't know the make/model. It was a PC integrated into a keyboard, including a 10MB HDD and a FDD ). The game was quite playable, but I don't remember much more than that. To...

Hi. While I was debugging the problem with AWE32 chorus that you reported with System Shock, I had some problems to make it run. I got a copy of the cd version from internet. Depending on the drivers that i load ( config.sys, autoexec.bat ), the emulator crashes at game startup due to a "fatal(...

Hi. I've corrected an error in the chorus engine and also forced sane max values, even though I don't know the exact reason why you needed to ensure that the value was 0 or above for System Shoch (I logged the values received and they were adequate). Didn't hear anything strange in E1M2, but the cho...