Also Dogs post at the beginning...
I'm not sure if you have done this yet, but is the PSU outputting correctly? Are you getting proper +5, -5, +12, -12?
Also Dogs post at the beginning...
Thanks czietz, that makes the most sense right now, the schematic I have is barely readable, not sure if there is a better copy somewhere else. I assume right now the first step is to check the YM chip for output using the keyboard to see if, 1) that is working and 2) trace from there forward to see where I am loosing the signal. If I had to guess, it's going to be further up the line as I have no sound from games or the keyboard and at some point the DMA sound should kick in, loosing both tends to indicate a circuitry area where both signals go into a device/circuit with neither coming out. I also guess that I need to make sure something in the software isn't inhibiting or turning off the sound, any suggestions on that? With the hard drive I have everything in German, which is hard to follow, and the floppy isn't working on this machine, although the floppy does works using the one in my Mega STe. Thanks!czietz wrote: 13 Dec 2020 13:10Good idea! I just did -- for TOS 3.06.exxos wrote: 13 Dec 2020 12:51 Maybe when you have time, look in TOS see if there is any mention of this switch in there ?
The DIP switch 8 does not enable/disable any hardware. It merely influences the bit for DMA sound in the _SND cookie. The logic is inverted -- as noted in Cyprians post (should have read it more carefully :( ). So, when the switch #8 is on, the bit indicating DMA sound capability in the _SND cookie is off and vice-versa.
Like I said, this does not directly influence any hardware. But software that takes into account the _SND cookie might refuse to do DMA sound when the switch is on (like in Cyprian's machine).
But let's get on-topic again. If there no sound at all (not even PSG sound, like keyclicks) in the TT there's something else amiss. @jacolover, do you have a scope? In that case for troubleshooting I suggest getting the schematic from dev-docs.org and tracing the sound from the PSG (in case of keyclicks) to the output. In that way, you should be able to see where it's faulty.
Users browsing this forum: Baidu [Spider], ClaudeBot and 7 guests