I tried added some debug print statements to the audlib.bas file and then rebuilding the library file with them but ended up getting "sub not defined" errors in wavetest using the new lib. (Must have broke something along the way). I might have some more time in the next few days to try getting the debug print statements to work.
Steps attempted:
- Updated audlib.bas with print statements in audPlayWav sub every few lines so hopefully when it runs, I can see which line it hung at.
- Run->Make Library. Named it AUDLIB.QLB
- Attempted to re-run wavetest.bas with: qb /run wavetest.bas /L audlib.qbl
EDIT: Got it working by dumping everything into one large bas file. haha
Here's a screenshot of a single key press and the sound working. (No lock up)
https://i.imgur.com/uevGalm.jpg
Here's a screen shot after a few plays and then hitting the spacebar quickly. It looks to lock up after sending the low byte and then attempting to send the high byte. If I force a wait during the "DMA not done, force" IF block, it keeps it from crashing but only because the sound file has time to complete before continuing.
https://i.imgur.com/GUCOhEq.jpg
I tried piping it to a text file to make it easier to view but the contents don't get saved due to the computer lock up.
Attached is the "WAVEFULL.bas" so you can see where the print lines are coming from in the audPlayWav sub.
Statistics: Posted by Erik — Tue May 12, 2020 10:38 am
]]>
Statistics: Posted by MikeHawk — Fri May 08, 2020 7:56 pm
]]>
Also just for kicks I took out all my sound configs from my autoexec.bat and config.sys and wavetest behaved the exact same way. (even played the sound still).
Yeah, that's on me: if there's no config string found, it defaults to "A220 I5 D1 H5" (base port 0x220, IRQ 5, low DMA 1, high DMA 5,) I don't know why I thought that was a good idea to be honest. It still worked because right now, the code doesn't take IRQ into account. That's why I need to write that ISR. I'm trying to figure out an organization that's not too heavy on assembly. I think I'll have to use the DMA auto-init and dump the audio data into a buffer that is fed on repeat to the SoundBlaster. The big downside is that it won't work with very early cards (pre SB 2.0)I'm 99% positive the DMA issue is on my code and has nothing to do with your hardware.
Statistics: Posted by MikeHawk — Wed May 06, 2020 4:49 pm
]]>
But at least there's sound, so it's getting somewhere... I should probably stop the DMA transfer manually, or maybe attempt auto-init DMA transfer, which would also provide sample mixing... I'm just not sure how to do it yet... I'll look into it, thanks again for your help!
You're welcome. Glad to help where I can. I found this page: http://www.oldskool.org/guides/oldonnew/sound
Which mentions the scenario I'm experiencing:
My SB Setup: https://i.imgur.com/0DnbQVv.jpgWhen one of these old games (1991 or earlier) attempts to play digitized sound on a card that isn't at the factory defaults--port 220, IRQ 7, and DMA 1--the result can range from no sound, to digitized sound that "halts" after two seconds of play, to locking up completely.
It looks like I have the default set at 220/irq 7/dma 1
I don't have anything plugged in the LPT1 port (Also on IRQ 7) so I think set up wise on my computer it should be okay.
Also just for kicks I took out all my sound configs from my autoexec.bat and config.sys and wavetest behaved the exact same way. (even played the sound still).
Also tried loading it on my IBM XT which doesn't have a sound card installed (to see if it would crash) and it returned the following at start up:
Then returned to the command prompt, so I guess that's expected.audSBInit: Failed to reset DSP
Thanks for the info, but this DMA issue is with the sound card and is running purely in DOS 5.0Check DMA on the hard drives in Device Manager. I had problems there.
PIO may be listed and unchangeable...newer stuff does not have the problem.
Statistics: Posted by Erik — Wed May 06, 2020 2:47 pm
]]>
Can click uninstall and reboot to get it reset as I recall.
http://petesqbsite.com/phpBB3/viewtopic ... pio#p22888
In the context of PC hard drives, what are PIO and DMA modes?
Statistics: Posted by burger2227 — Tue May 05, 2020 4:12 pm
]]>
]]>
Not sure if it's needed, but this is what the header section had in it:
If I play the sounds slowly and let the previous sound finish completely before hitting space bar and triggering the next sound clip to be played, it doesn't crash. I sat there for a bit slowly tapping and it worked fine. If I press space too quickly while a previous sound is playing it will usually freeze the application after the two overlapping clips finish (Requiring a soft reset with CTRL+ALT+DEL).Segment: 9C11
Length: 16103
Statistics: Posted by Erik — Mon May 04, 2020 4:09 pm
]]>
I suppose I could pull my overdrive chip out of the expansion slot and see how it runs on a 25MHz 486SX but that thing is wedged in there pretty good right now.
Thanks for the help Erik! I'm fairly certain removing the overdrive chip won't be necessary... last patch fixed a stupid mistake where I was reading a string out of bounds; I should probably focus on the sound system, mode Y and the keyboard handler. Both Cody and MSDuo have an EMS component, but since MSDuo works on your system and I didn't modify it too much in Cody, I can probably rule that out...EDIT: I think I may have a replacement for the sound code...
EDIT again: I just now realize that I'm supposed to create an ISR to acknowledge the end of DMA transfert... I guess I have to replace one of the existing interrupts according to the IRQ value provided by the BLASTER environment string? That would be interrupt 0x0A for IRQ 2, 0x0D for 5, 0x0F for 7 and 0x72 for 10 (http://www.bioscentral.com/misc/interrupts.htm). That would make sense, given that the factory default for the SoundBlaster 1.0 was IRQ 7 and it caused issues with printers (http://www.oldskool.org/guides/oldonnew/sound), since they used the same IRQ at interrupt 0x0F (http://www.ctyme.com/intr/int-0f.htm)... If I can do without, I'm probably not going to bother.
Statistics: Posted by MikeHawk — Sat May 02, 2020 9:56 am
]]>
Once I get to the first level, after McCloud is moved (either by mouse or keyboard) a bit the game freezes. I can't even soft reset the computer, it needs a full power off and power on to restart.
It's very close to being playable.
From what I can tell before it crashes, it looks to run completely fine on my 486-50Mhz 16MB of RAM. Panda now also runs completely fine on my set up (with no sound). I suppose I could pull my overdrive chip out of the expansion slot and see how it runs on a 25MHz 486SX but that thing is wedged in there pretty good right now.Statistics: Posted by Erik — Sat May 02, 2020 3:24 am
]]>
Statistics: Posted by Erik — Sat May 02, 2020 3:24 am
]]>
Statistics: Posted by MikeHawk — Fri May 01, 2020 4:47 pm
]]>
Statistics: Posted by burger2227 — Fri May 01, 2020 11:36 am
]]>
I'm also puzzled with the MSDUO/CODY issues... the one you can't run, I can, but not the other...
I really have to look into that.
EDIT: I'm a big dumb-dumb. I think I've found something... (oh boy, it's going to be a pain in the ass to fix given my setup)
I found an oddity in McCloud, fixed it, but I can't guarantee anything because that's the one I can run
(this has to be one of those rare times where I complain because something's running as intended.)Statistics: Posted by MikeHawk — Thu Apr 30, 2020 5:54 pm
]]>
Cody shouldn't try to initialize the sound card when it is first launched, so that's weird; it may try to initialize the sound card even if "sound" is set to FALSE if it thinks a sound card might be available. However, if "lodma" is set to -1 or "baseport" is set to "0xFFFFFFFF", it shouldn't... Try setting "numpages" to 0 and see if that works.
I tried again setting the pages to zero. Sound off and set the controller to "KEYBOARD" from "MOUSE" (not sure if that's right). Still didn't start unfortunately. Sound card is a Sound Blaster 16. Works on other things. Still no sound from MSDUO or PANDA though.What kind of card do you have?
The Panda patched version worked!!I attached a patch for Panda. I noticed some junk on top of the splash screen (red lines,) do you have that too?
Awesome!Yep, I do get the red lines when I start up as well. Only Panda though. I don't see them on MSDUO.
Here's what it looks like to me: https://i.imgur.com/nTJQU13.jpg
Interesting left overs I suppose in memory when I went from Doom and then loaded the game right after. You can see E1M1-ish in the background: https://i.imgur.com/QmmUjUV.jpg
Statistics: Posted by Erik — Thu Apr 30, 2020 3:37 pm
]]>
MSDUO refuses to launch.
SSSLIDE works as intended, although at a crawling pace in the menu.
I attached a patch for Panda. I noticed some junk on top of the splash screen (red lines,) do you have that too?
Statistics: Posted by MikeHawk — Thu Apr 30, 2020 9:14 am
]]>