old artic transport, some ideas.
Linux for blind general discussion
blinux-list at redhat.com
Fri May 26 02:16:09 UTC 2017
Hi Mark,
Santa has come early if you have an interest.
I have for you a copy of the documentation for the artic transport.
Yes there is a way to set the clock.
In any case, you may want to write me privately, but I do not know if I
put my address in here if the post will be flagged.
Let me know and we can work it out as the song goes.
Kare
On Mon, 22 May 2017, Linux for blind general discussion wrote:
> Mark Peveto here.
> Issues mostly solved. If he could tell me how to set the clock on the thing, or even if it's possible For his info, the transport modle is 611
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Mon, 22 May 2017, Linux for blind general discussion wrote:
>
>> Hi folks,
>> Realizing it may be solved by now, I did promise to ask another user.
>> His thoughts are below, if the person is still having issues let me know now
>> as he has offered to help them troubleshoot given he has used his own unit
>> with Linux for some time.
>> Karen
>>
>>
>> ---------- Forwarded message ----------
>> Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
>> Subject: Re: artic transport question?
>>
>> Ahh, yes, depending on which artic synthesizer he has, he may need to run a
>> program, or set it to synthesizer mode. If it's a spirit, nothing needs to be
>> done, it should just work. If it's a transtype, there is an option in the
>> menus to set it to speech mode, though that's the one where you can also run
>> the terminal program, and it will talk that way too, though not as readily or
>> as well as the synthewsizer mode will allow. If it's a transport, just
>> setting the linux side of things to 9600 8, n, 1 should take care of the
>> problem, as that is the default settings on the transport.
>> I think that covers all the possible options. If there are further issues,
>> feel free to pass my email address on to the individual having trouble.
>>
>>
>> Again, hope this helps.
>>
>>
>>>
>>>
>>>> If I remember correctly, (and assuming this person hasn't already solved
>>>> their issue), the keyword for the transport is txprt.
>>>> Passing that on the commandline along with the port (or it can scan for >
>>> the port automatically) should do the trick.
>>>> Hope this helps.
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
More information about the Blinux-list
mailing list