Posted by StevenRoy on December 30, 2002 at 10:46:51:
In Reply to: Re: Out of memory + No sound posted by Marook on December 29, 2002 at 15:11:48:
: But now there ist a another problem. If everything is loaded and i start CCS64.EXE i get an errormsg with many machinecode commands...If i set inside the C64.CFG -> SOUNDENABLE=NO i can start it (without sound) and while its running i can turn on the sound but nothing happens...
The most likely cause of this is that your sound card is either not compatible with the "Sound Blaster" standard, or is configured in an incompatible way.
The first thing to try is to add an environment variable to your configuration. This is the "SET BLASTER" line that several programs (and I think CCS64 too) use to determine sound card settings.
Basically, you add this line to the end of your AUTOEXEC.BAT file:
SET BLASTER=A220 I5 D1 T4
The number after the "A" is the I/O address that your sound card uses. Anything other than 220 is considered "non-standard" and should probably be changed to 220. The number after the "D" is the DMA channel number. It pretty much has to be 1, and a lot of programs ignore it and just assume the card's using 1! The "T4" is simply a compatibility level indicator; very few programs actually look at that value. The "4" there just means "Sound Blaster Pro compatibility".
The number after the "I" is the most important one, because it's the IRQ number that the sound card uses, and it can be 2, 5, 7, 9, 10, or even something else (although 5 and 7 are the most common, and also the most compatible). If a program tries to use an IRQ other than what the sound card is set to, then that can cause odd problems, including what you described.
If you had Windows 95 or newer on your computer, then it could be possible to find your sound card in the Device Manager and find out what IRQ it's using. That would be the first value you would try putting after the "I".
Since you mentioned DR-DOS, I think I can assume that you'll have to rely on your memory instead (yours, not your computers), or on the auto-detect feature of some DOS games' setup programs, or on trial-and-error.
Anyway, hope this helps. Good luck.