>
> I reacted to soon... my serial port is based on an 16550A.
> But i find it strange that the 16550A is mentioned in the baycom.c
> source file.
That's because this problem is known already. The question is why it does
not appear under MS-DOS. On my box, both TFPCX 2.71 and TFX 2.8 (as
TFX_UART) are running smoothly under MS-DOS 6.22. Under Linux, there are
still some problems. I have not enough knowledge to tell you why.
> I'm using a SoundBlaster AWE64 but i think this should work with any
> SoundBlaster 16+.
That's a real pity. It seeems only _real_ SoundBlasters (manufactured by
Creative Labs) work with SoundModem. So I'll have to go on and get one
from the flea market (at the moment, I can't afford such a "high end"
soundcard like the AWE ones).
I have an ESS1868 AudioDrive that all my DOS games and MOD players
recognize as "SoundBlaster 16", even without any driver loaded.
The Linux Sound driver also detects a "Sound Blaster", I can play all
sound formats without problems. But soundmodem refuses to work.
> The script i use the start the soundmodem is. But this only works (i
> think) if you compile
> the soundblaster driver as a module.
>
> #!/bin/sh
> #
> # Set Soundmodem Parameters
> #
>
> setcrystal -s 0x220 -i 5 -d 1
>
> # Select driver for interface sm0
> sethdlc -p -i sm0 mode sbc:afsk1200 io 0x220 irq 5 dma 1 serio 0x2f8
>
> # Interface sm0 up
> ifconfig sm0 up
>
> # Set call for interface sm0
> axparms -setcall sm0 PE1RXS-1
>
I can't see a line that loads the soundmodem module as well. Is there no
need for inserting such a line? Does sethdlc do the job? I have no
clue...but am going to test this. As Tom Sailer said, a 'dmesg' would show
any error messages then. I'll post them soon.
Cheers, 73
Gerd