search

WheezyE / Winelink

Installation scripts for running Winlink (RMS Express/Trimode & VARA) on non-Windows computers. Wine & Box86 make this project possible.
69 stars 19 forks source link

SoundModem can't find Masters Communications RA board #9

Closed mhnadler closed 2 years ago

mhnadler commented 2 years ago

Soundmodem provides PTT.DLL for RA boards like my DRA-70. When EXT selected for PTT Port, SoundModem prompts that one should check advanced settings. Opening advanced settings should normally find the C-Media device. But here it finds nothing.

Instructions are here: https://www.masterscommunications.com/products/radio-adapter/faq/ptt-soundmodem.html

Is there some workaround? Where can I look for error messages? How to debug?

WheezyE commented 2 years ago

Oh interesting! I hadn't heard of soundmodem or the DRA-70 before. I was able to start the soundmodem program in box86/wine on my Pi4 with these commands, but I don't have a DRA-70 to test trying to connect to it:

mkdir soundmodem && cd soundmodem
wget http://uz7.ho.ua/modem_beta/ptt-dll.zip
wget http://uz7.ho.ua/modem_beta/soundmodem113.zip 
7z x soundmodem113.zip
7z x ptt-dll.zip
cp *.dll ~/.wine/drive_c/windows/system32/
BOX86_NOBANNER=1 winetricks -q vb6run
wine soundmodem.exe

Screenshot_20210914-101038 Screenshot_20210914-101048 Edit: added screenshots

A good procedure for debugging with box86 is to first test your program out in wine on a regular x86 Linux computer (not a Pi4 with box86) to make sure that it's not a wine problem. If your DRA-70 device connects in "regular x86 Linux" with wine, then we know that the problem is isolated to box86 and we can ask the box86 team about it. If the DRA-70 doesn't connect in "regular x86 Linux" with wine, then we know that we should ask the wine team about it.

If you find that regular linux/wine works with your device, then the next step is to check box86 logs with BOX86_LOG=1 wine soundmodem.exe and see if anything fishy pops up. This is easier said than done and it might be best to open a ticket on the box86 github with your log file (copy-paste the terminal output into a text file) attached to your issue. The author of box86, ptitSeb ("Seb"), is amazing and might be able to figure out what's wrong and maybe push a fix for you in that case.

WheezyE commented 2 years ago

I'm going to close this ticket for now due to inactivity. Please let me know if you have any other questions/ideas/comments/concerns though and I'll re-open this thread.