Why does Wolfenstein 3D lock up with Sound Blaster 16?
Reginald Lynch P025
to play the Wolfenstein 3D game with no problems using my PC's internal
speaker. Now that I've added my sound card, Wolfenstein (v1.1) locks up
on the setup screen where it sizes your memory and detects sound card
type. Anyone else had this problem and know how to resolve it? My
computer is a 386/40 with 4M RAM. The sound card passes the TESTSB16
diagnostic and does not have problems with the other games I've tried.
--
+------------------------+----------------------------------+----------+
| Reggie Lynch | DMS-100 CC XPM Mtce Software | Opinions |
| Internet: ly...@bnr.ca | Dept 3J35, Col 3H19 BNR-RTP | exressed |
| ESN 6-294-8040 | Bell-Northern Research, Inc. | are my |
| Phone (919) 991-8040 | PO Box 13478 | own. |
| Fax (919) 991-8369 | Research Triangle Park, NC 27709 | |
+------------------------+----------------------------------+----------+
Patric Shane Linden
>Before installing my Sound Blaster 16 (i.e. 16-bit DAC), I was able
>to play the Wolfenstein 3D game with no problems using my PC's internal
>speaker. Now that I've added my sound card, Wolfenstein (v1.1) locks up
>on the setup screen where it sizes your memory and detects sound card
>type. Anyone else had this problem and know how to resolve it? My
>computer is a 386/40 with 4M RAM. The sound card passes the TESTSB16
>diagnostic and does not have problems with the other games I've tried.
>--
Mailing you direct bounced, so. . .
I'm running Wolf3d fine on a 386/33 with 4meg RAM and SB16ASP. I'd
check for a DMA or IRQ conflict. Is the SET BLASTER variable correct
for your configuration? Without more info, though, I don't know what
else to suggest. . . Good luck!
Regards,
Patric S. Linden
khe...@matt.ksu.ksu.edu
C0d3 M0n$t3r
: Before installing my Sound Blaster 16 (i.e. 16-bit DAC), I was able
: to play the Wolfenstein 3D game with no problems using my PC's internal
: speaker. Now that I've added my sound card, Wolfenstein (v1.1) locks up
: on the setup screen where it sizes your memory and detects sound card
: type. Anyone else had this problem and know how to resolve it? My
: computer is a 386/40 with 4M RAM. The sound card passes the TESTSB16
: diagnostic and does not have problems with the other games I've tried.
Wolf3D always locked up for me when I used QEMM and such...worked fine
with only himem.sys, try that...
kba...@gauss.onu.edu
David Timoney
In addition to the excellent suggestion that it could be a memory
manager, I might also suggest you check with ID or Apogee (perhaps in
the .games.arcade?). One thing I can think of is that perhaps you're
using an IRQ or DMA not supported by Wolf 3D, as the card came out well
after the software.
Dave
Rohan Talip
If you had said that it locks up after this then I would have said that
the problem was probably that you had applied the "fix" to W-3D or
obtained a "fixed" version.
If this seems familiar then send me some email and I will check out my
version of the game - I applied the fix then fixed the "fix".
Get it, got it, good!
Peter Tyers
>From: ro...@cairo.anu.edu.au (Rohan Talip)
>Subject: Re: Why does Wolfenstein 3D lock up with Sound Blaster 16?
>Date: 1 Sep 93 16:39:09 GMT
>ly...@bnr.ca (Reginald Lynch P025) writes:
>>Before installing my Sound Blaster 16 (i.e. 16-bit DAC), I was able
>>to play the Wolfenstein 3D game with no problems using my PC's internal
>>speaker. Now that I've added my sound card, Wolfenstein (v1.1) locks up
>>on the setup screen where it sizes your memory and detects sound card
>>type. Anyone else had this problem and know how to resolve it?
>>--
I realise this response sounds stupid so don't flame in advance!
In order to use Wolf3d (acquired from the net) with my SBPro2 I=10 D=1 A=220h
I found it necessary to unset the SBPRO and SOUND environment variables. I
kick Wolf3d off through a batch file of the form
set SOUND=
set SBPRO=
wolf3d
set SOUND=\SBPRO\XXXX I10 D1 A220 T4
set SBPRO=XXXXX XXXX XXX
I stress OF the FORM - I'm working from memory since the set up is on my home
machine and this is being typed at work. The critical thing is the need to
dereference the variables and reestablish them after the wolf3d session.
If I don't do this it locks at the first screen where it's sizing memory and
establishing sound card, which sounds like your problem. I believe the cause
is my using int10 rather than the default int5/7. On another machine that my
previous SBPRO card was installed (this card also required the batch file)
this batch file was not necessary with the int set to factory default.
Hope this helps.
P Tyers, Tel. +61-(0)3-2536794 JANET: p.tyers%trl....@uk.ac.ucl.cs
ACSnet: p.t...@trl.oz UUCP:{uunet,hplabs,ukc}!munnari!trl.oz.au!p.tyers
CSnet: p.t...@trl.oz.au ARPAnet: p.tyers%trl....@uunet.uu.net HAM: VK3KTS
MAIL: Telecom Research Laboratories,P.O. Box 249,Clayton,VICTORIA 3168,AUSTRALIA
Reginald Lynch P025
my Sound Blaster 16. As I now discover, many games will not work with
settings other than IRQ5 or IRQ7. But since I have a bus mouse at IRQ5
and LPT1 printer port at IRQ7 I avoided these settings. The tech at
Sierra/Dynamix advised my to set my SB16 to IRQ7 anyway and sure enough
it is working with no problem. So Wolfenstein 3D now runs fine. I can
print LPT1 and head sound sharing IRQ7 - evens Windows v3.1 works.
To change from IRQ10 to IRQ7, I left the SB16 jumpered at IRQ10 (so I
wouldn't have to pop-off the case again) and ran SBCONFIG to change
the IRQ thru software (includes update to environment variables).
My only problem now is that I still can't get sound on my Aces of the
Pacific game. Suspect I may have to change the jumper setting to IRQ7
for this to work. Will find out later when I have time ...