public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: old artic transport, some ideas.
Date: Thu, 25 May 2017 22:16:09 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1705252212470.15475@server2.shellworld.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705222137250.2862@southernprince>

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@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>

  parent reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
   ` Linux for blind general discussion [this message]
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion
             ` Linux for blind general discussion
               ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
     ` Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.1705252212470.15475@server2.shellworld.net \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).