Elecraft

Tascam 122 and Windows 10

Classic

List

Threaded

5 messages Options

K9IR

Tascam 122 and Windows 10

I have been using a Tascam 122 MKii as an outboard sound card with my K3 for RTTY. Initially the Tascam worked fine after upgrading the shack PC to Win10. Today, however, while I can decode RTTY, I cannot send any longer. I get an eZeroDivide error message from MMTTY when WinWarbler starts.

I understand officially the Tascam drivers ended with WinXP/Vista, but I had it working in Win7. I've tried using the Compatibility feature in Programs under Control Panel to no avail; the Tascam driver software seems to load but results are the same--no TX.

I have verified VOX is engaged and the VOX gain set properly. This whole setup worked fine until today. I think there was an auto-update for Win10 that installed since the last successful operation and suspect that killed the Tascam.

Any ideas on how to jump start the Tascam into action? Or is it time to retire this piece of gear and get something else? Tnx!

73 Paula k9ir

HK3J

Re: Tascam 122 and Windows 10

Siso. Acerca de las grabadora TASCAM y operación en RTTY

El mar., 4 oct. 2016 5:39 a. m., K9IR <[hidden email]> escribió:

> I have been using a Tascam 122 MKii as an outboard sound card with my K3
> for
> RTTY. Initially the Tascam worked fine after upgrading the shack PC to
> Win10. Today, however, while I can decode RTTY, I cannot send any longer. I
> get an eZeroDivide error message from MMTTY when WinWarbler starts.
>
> I understand officially the Tascam drivers ended with WinXP/Vista, but I
> had
> it working in Win7. I've tried using the Compatibility feature in Programs
> under Control Panel to no avail; the Tascam driver software seems to load
> but results are the same--no TX.
>
> I have verified VOX is engaged and the VOX gain set properly. This whole
> setup worked fine until today. I think there was an auto-update for Win10
> that installed since the last successful operation and suspect that killed
> the Tascam.
>
> Any ideas on how to jump start the Tascam into action? Or is it time to
> retire this piece of gear and get something else? Tnx!
>
> 73 Paula k9ir
>
>
>
> --
> View this message in context:
> http://elecraft.365791.n2.nabble.com/Tascam-122-and-Windows-10-tp7623087.html
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

K9IR

Re: Tascam 122 and Windows 10

Quick update--it appears the issue may be between MMTTY and WinWarbler. In further t-shooting I was able to send from within MMTTY, so the sound card appears to be alive and well under Win10. I've emailed Dave/DXLab with my WW error log.

Sorry for the bandwidth. I'd learned about using the Tascam as a sound card on this list and thought there might be some advice for making it work under Win10 (which now appears to not be the problem).

73 Paula k9ir

Joe Subich, W4TV-4

Re: Tascam 122 and Windows 10

In reply to this post by K9IR

On 10/4/2016 6:38 AM, K9IR wrote:
> I have been using a Tascam 122 MKii as an outboard sound card with
> my K3 for RTTY. Initially the Tascam worked fine after upgrading the
> shack PC to Win10. Today, however, while I can decode RTTY, I cannot
> send any longer. I get an eZeroDivide error message from MMTTY when
> WinWarbler starts.

This is not a Tascam (sound card) issue. The solution to this ha been
posted many times on the DXLab list. It is an error in MMTTY. To fix
it ...

1) close WinWarbler
2) Using Windows Explorer navigate to the DXLabSuite\WinWarbler
directory
3) delete the file MMTTY.ini
4) restart WinWarbler
5) Select RTTY
6) Open CONFIG | RTTY and reset Mark Offset to -<PITCH> where PITCH
is your PITCH setting in AFSK A and set Optimal Offset to
[PITCH + 85]. If you are using DATA A, reset Mark Offset to <Pitch>

73,

... Joe, W4TV

On 10/4/2016 6:38 AM, K9IR wrote:

> I have been using a Tascam 122 MKii as an outboard sound card with my K3 for
> RTTY. Initially the Tascam worked fine after upgrading the shack PC to
> Win10. Today, however, while I can decode RTTY, I cannot send any longer. I
> get an eZeroDivide error message from MMTTY when WinWarbler starts.
>
> I understand officially the Tascam drivers ended with WinXP/Vista, but I had
> it working in Win7. I've tried using the Compatibility feature in Programs
> under Control Panel to no avail; the Tascam driver software seems to load
> but results are the same--no TX.
>
> I have verified VOX is engaged and the VOX gain set properly. This whole
> setup worked fine until today. I think there was an auto-update for Win10
> that installed since the last successful operation and suspect that killed
> the Tascam.
>
> Any ideas on how to jump start the Tascam into action? Or is it time to
> retire this piece of gear and get something else? Tnx!
>
> 73 Paula k9ir
>
>
>
> --
> View this message in context: http://elecraft.365791.n2.nabble.com/Tascam-122-and-Windows-10-tp7623087.html
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

K9IR

Re: Tascam 122 and Windows 10

Tnx, Joe, that did it. Sorry I didn't look far enough in the DXLab reflector posts to see this solution. When I Dave's request to send the error log for someone who posted with a similar problem, I went that route.

73 Paula k9ir