Reply to DMODs ask for nonexistent files - I'm confused
If you don't have an account, just leave the password field blank.
I'm a long-term Dink fan. I'm having some problems with DMODs, most of which are the fault of my own PC, because the problems are with DMODs which have worked just fine in the past. They only started when I did a total Format of C: and virgin install of W98SE.
Trouble is, some of the DMODs ask for a file MMSYSTEM296 (no extension given) - I have an MMSYSTEM.dll, but there is no file with the name MMSYSTEM296 on my entire system. So how could the DMODs have worked in the past? This is what the error log says:
Dink:Midi error: MMSYSTEM296 The file cannot be played on the specified MCI
I have tried copying MMSYSTEM.dll to another folder, renaming it for the requested file, and putting it back into the System folder. No good.
MMSYSYSTEM296 isn't the only such file that DMODs ask for. There are at least two others I know of, which are the same except the three digits are different.
How can my DMODs have worked before when these files are not, and never have been, on my system?
If my PC is giving the DMOD a problem like this:
Dink:Error reading status from midi mapper!
What should I be checking?
I have W98SE, and a piece-of-caca sound card called Sound Blaster AudioPCI128. I have not changed my hardware from the time when these DMODs worked properly, but I have tried reinstalling the card. No change, though. Updating drivers - no go. Reinstall the original Dink - no go. My sound settings are: Port 220, IRQ 7, 8 bit DMA 1, 16 bit DMA 7, MPU401Port IRQ 330, IRQ 7, AdLib port 388. I have no way to access, much less correct, problems with the "midi mapper". Device Manager says all systems are go.
Occasionally during a game, a .mid file causes a popup that tells me the sound may not play properly with my midi settings. If I click okay, it plays the file, but only till another .mid file is supposed to play - then silence. Often, after playing a file like that, the next map square I move to changes the color settings to scattered points of color and images that are almost impossible to see as such. Then I have to reboot the PC. Somehow, actually playing those files ends up screwing up the video settings. Sound effects work fine. It's just the music that won't work.
I have some troubles with DirectX (ver 9.0c), too - the diagnostic tool crashes if I tell it to test DirectShow. I can't remember ever seeing DirectShow as a feature of DirectX. It tells me there was a problem with it last time, and do I want to continue anyway? If I click yes, it freezes.
Ontrack's CrashProof utility says this:
An exception (access violation) has occurred in module at .data + 0000013C in Win32 application DXDIAG
This particular crash is not repairable, so your only choice at this point
is to terminate the application.
EAX=515F0000 CS=016F EIP=7964513C EFLGS=00210206
EBX=00409BE8 SS=0177 ESP=0056F256 EBP=0056F2AC
ECX=0000F340 DS=0177 ESI=00000001 FS=5ED7
EDX=80008158 ES=0177 EDI=00000001 GS=6086
? CS:[E]IP:
When I don't let it load the test for DirectShow, the diagnostic window opens. All tests indicate no prob, except that it suggests I update my video driver. It's rather old, and I can't upgrade it. But Dink games all played just fine with it.
Also, in STONE, the jail wall (early in the game) won't punch out. It did several days ago, and now it won't. In FIAT, nothing I do can make the pillbug larvae appear near the church, where it is supposed to. Also, once I get some scorpion tails, I can't get rid of them - I can keep getting sleep bombs, and still have the same number of scorpion tails. These didn't used to happen. I've played both DMODs to the end in the past, so I know how to do these things already. So why should they suddenly stop doing them?
Can one of you who knows how to make DMODs tell me what they think is wrong? I should be having no problems with Dink games with the equipment I've got.
Thanks,
Holly B.
Trouble is, some of the DMODs ask for a file MMSYSTEM296 (no extension given) - I have an MMSYSTEM.dll, but there is no file with the name MMSYSTEM296 on my entire system. So how could the DMODs have worked in the past? This is what the error log says:
Dink:Midi error: MMSYSTEM296 The file cannot be played on the specified MCI
I have tried copying MMSYSTEM.dll to another folder, renaming it for the requested file, and putting it back into the System folder. No good.
MMSYSYSTEM296 isn't the only such file that DMODs ask for. There are at least two others I know of, which are the same except the three digits are different.
How can my DMODs have worked before when these files are not, and never have been, on my system?
If my PC is giving the DMOD a problem like this:
Dink:Error reading status from midi mapper!
What should I be checking?
I have W98SE, and a piece-of-caca sound card called Sound Blaster AudioPCI128. I have not changed my hardware from the time when these DMODs worked properly, but I have tried reinstalling the card. No change, though. Updating drivers - no go. Reinstall the original Dink - no go. My sound settings are: Port 220, IRQ 7, 8 bit DMA 1, 16 bit DMA 7, MPU401Port IRQ 330, IRQ 7, AdLib port 388. I have no way to access, much less correct, problems with the "midi mapper". Device Manager says all systems are go.
Occasionally during a game, a .mid file causes a popup that tells me the sound may not play properly with my midi settings. If I click okay, it plays the file, but only till another .mid file is supposed to play - then silence. Often, after playing a file like that, the next map square I move to changes the color settings to scattered points of color and images that are almost impossible to see as such. Then I have to reboot the PC. Somehow, actually playing those files ends up screwing up the video settings. Sound effects work fine. It's just the music that won't work.
I have some troubles with DirectX (ver 9.0c), too - the diagnostic tool crashes if I tell it to test DirectShow. I can't remember ever seeing DirectShow as a feature of DirectX. It tells me there was a problem with it last time, and do I want to continue anyway? If I click yes, it freezes.
Ontrack's CrashProof utility says this:
An exception (access violation) has occurred in module at .data + 0000013C in Win32 application DXDIAG
This particular crash is not repairable, so your only choice at this point
is to terminate the application.
EAX=515F0000 CS=016F EIP=7964513C EFLGS=00210206
EBX=00409BE8 SS=0177 ESP=0056F256 EBP=0056F2AC
ECX=0000F340 DS=0177 ESI=00000001 FS=5ED7
EDX=80008158 ES=0177 EDI=00000001 GS=6086
? CS:[E]IP:
When I don't let it load the test for DirectShow, the diagnostic window opens. All tests indicate no prob, except that it suggests I update my video driver. It's rather old, and I can't upgrade it. But Dink games all played just fine with it.
Also, in STONE, the jail wall (early in the game) won't punch out. It did several days ago, and now it won't. In FIAT, nothing I do can make the pillbug larvae appear near the church, where it is supposed to. Also, once I get some scorpion tails, I can't get rid of them - I can keep getting sleep bombs, and still have the same number of scorpion tails. These didn't used to happen. I've played both DMODs to the end in the past, so I know how to do these things already. So why should they suddenly stop doing them?
Can one of you who knows how to make DMODs tell me what they think is wrong? I should be having no problems with Dink games with the equipment I've got.
Thanks,
Holly B.
