I'm starting to wonder if the Super I/O expansion board could be the problem. I have one from cbmstuffBBond007 wrote:Looks like this is duplicated & corrupt (missing '[A'), delete that part - Doubt that has anything to do with the problem, but worth fixing...PiddlyD wrote: O486]
MIDI_BAUD = 38400
TCP_SOUND_CONNECT = /media/fat/SOUNDS/connect_sav.wav
I'm not sure why its not working. It almost looks like the baud rate is incorrect. What happens if you type commands such as "ATHELP" or "ATVER"?
At one point (a while ago...) the location of the MidiLink.INI changed from '/media/fat/config' to '/media/fat/linux' - are you editing the one in the 'linux' directory? If there is one in 'config' you can delete it...
I was able to connect to Afterlife BBS (afterlife.dynu.com:6400) with both of my MiSTers with the 4/25 C64 core - I have one MiSTer that is more affected by core stability issues than the other.
I get that on one of my MiSTers but not the other. If i just reload the core it seems to work the 2nd time.evdberg wrote: I noticed that the C64 core does not start when run as 1st after powering on MiSTer. Is this a known issue? After reboot it will start correctly.
You can see that he didn't follow the reference design completely. The smaller buttons don't fit the default build for a MiSTer case from Thingiverse, for example.
I'll check your advice and see. There has to be *something* wrong somewhere. It is so strange that my Minimig and AO486 are both able to connect to this BBS with no problem, it is only the C-64 core that gives me issues.