09497: at586 [msdos622]: Wolfenstein 3D 1.4g doesn't see the sb16_lle card, althought sound in at586 machine is marked as OK.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
09497	Sound	Major	Always	8 days ago	22 hours ago

Tester	VasiliyFamiliya	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Invalid report	OS	Windows (x64)
Status [?]	Closed			Driver	pc/atpci.cpp
Version	0.288	Fixed in Version		Build	x64
		Fixed in Git Commit		Github Pull Request #

Summary	09497: at586 [msdos622]: Wolfenstein 3D 1.4g doesn't see the sb16_lle card, althought sound in at586 machine is marked as OK.
Description	The only available way to play the sound is PC speaker.
Steps To Reproduce	Install and launch the game. Abscence of BGM at the titlescreen and menus, and also PC speaker beeps instead of FM-synthesized menu choice SFX are noticeable enough. Then try the sound settings menu to ensure.
Additional Information	Launch BAT content: mame at586 -pcibus:1:i82371ab:board1:fdcsmc:fdc:1 525hd -pcibus:1:i82371ab:board2:comat:serport0 wheel_mouse -isa1 clgd542x -isa2 sb16_lle -isa3 mpu401 -ram 256M -hard "My DOS.chd"
Github Commit

Flags
Regression Version
Affected Sets / Systems	at586 [msdos622]

Attached Files	Wolfenstein 3-D (USA) (v1.4).zip (1,433,610 bytes) 8 days ago Uploaded by VasiliyFamiliya

No.24466 Robbbert Moderator 8 days ago	Another case of the mysterious "My DOS.chd", which needs to be examined to make sure you've installed the sound card correctly. All sound cards need the BLASTER variable to be configured, so that games can know how to communicate with them. Early sound cards had jumpers to set the IRQ, DMA and I/O address, while later ones were configured by a utility. These later ones were examined by the DIAGNOSE utility at boot time to read off the settings and create the BLASTER variable. Have you done any of this? Doesn't seem like it. If you have, I'll need a copy of your chd before this report can be accepted.
No.24467 VasiliyFamiliya Tester 8 days ago	Archive part 1: https://www.mirari.fr/1Ur0 Part 2: https://www.mirari.fr/8emz Part 3: https://www.mirari.fr/mAR8
No.24468 Robbbert Moderator 7 days ago edited on: 7 days ago	Downloaded thanks. I've set this to acknowledged, as I ran out of time and won't be able to look further at this for a few days.
No.24472 Kale Developer 6 days ago edited on: 6 days ago	at586 uses the legacy PCI bus, and the way it works and what kind of BIOS it expects will be eventually entirely splitted in separate romsets.
No.24473 Kale Developer 6 days ago edited on: 6 days ago	To tell that is using the legacy PCI bus user side: -pcibus We also don't need this bug report, as per https://github.com/mamedev/mame/issues/391
No.24474 Robbbert Moderator 6 days ago	I'll still leave it open until I can do my testing sometime next week. Before I left I did test a number of AT-class drivers, and of those that booted and had 4M of RAM by default, Wolf3D worked on them, but I didn't add the soundcard yet. I was actually impressed as the game ran at full speed with no issues.
No.24483 Robbbert Moderator 22 hours ago	The problem was replicated on the at586. However the soundblaster works on the at486, so you should use that instead. Your command line is overly-complicated, you don't need all that stuff. The blaster variable was missing, so the game had no idea that a soundcard was installed. The Soundblaster2 card requires that the onboard jumpers be manually set, but MAME has no settings for this. DOS can't see any more than 64MB, so specifying 256M is a waste and causes a long bootup time. Wolf3d only needs 4MB. What works: Add to the autoexec.bat: SET BLASTER=A220 I7 D1 T3 The command-line to use: >mame at486 -isa2 sb16_lle -ram 4M -hard "My DOS.chd" Since Kale already said this report is a waste, and he is a dev, it is now closed.