public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "W. Nick Dotson" <nickdotson@bellsouth.net>,
	"Speakup is a screen review system for Linux."
	<speakup@braille.uwo.ca>
Subject: Re: Re[2]: Owasys 22C Screenless Cellphone
Date: Wed, 19 Jul 2006 13:33:01 -0700	[thread overview]
Message-ID: <20060719203301.GA12400@localhost.localdomain> (raw)
In-Reply-To: <20060719151927.XYKH16552.ibm67aec.bellsouth.net@NICK3>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can you please explain what you mean when you say you're waiting for
them to call and get your card info? Do you mean that in order to get
a firmware upgrade, you need to give them info about your SIM card?
If so, then what kind of info, and why? That doesn't make sense
currently. Am I reading too much into this perhaps, and do you simply
mean credit card info? In that case, I thought that firmware upgrades
to most phones were generally free.

Greg


On Wed, Jul 19, 2006 at 10:17:33AM -0500, W. Nick Dotson wrote:
> I'll say it plainly, they'll have to pry my Owasys22C outa my cold dead fingers.  It does exactly what I want, accessories and firmware upgrade are currently 
> available, I'm waiting for them to call for my card info, and it's small, does everything I need it to with a no fuss no muss package I could just charge up turn 
> on and go with probably without ever having first read the manual, but I'm a tech support geek, and don't properly feel I own something and have the right 
> to turn it on and play with it til I've done my duty and read the manual...
> 
> Nick
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEvpb97s9z/XlyUyARAi4WAKC2MNTKyb49CWJv0GyHkXOUS3iPbACgh9/Y
ooY39BR+LdsYN4fdXU798WQ=
=ijp1
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 ace
 ` W. Nick Dotson
   ` Wil James
     ` Cheryl Homiak
       ` Lorenzo Taylor
         ` Cheryl Homiak
         ` Re[2]: " Farhan
           ` Sean McMahon
           ` Michael Whapples
             ` David Poehlman
               ` W. Nick Dotson
               ` Michael Whapples
                 ` David Poehlman
                   ` Re[4]: " Farhan
                     ` David Poehlman
                       ` Sean M McMahon
                       ` Adam Myrow
                         ` Gregory Nowak
                         ` Michael Whapples
                 ` Re[2]: " Wil James
                   ` W. Nick Dotson
                     ` Gregory Nowak [this message]
     [not found]                   ` <cone.1153334728.2370.9860.0@tux>
                     ` Michael Whapples
                   ` Re[4]: " Farhan
                     ` Sean M McMahon
                 ` Re[2]: " Janina Sajka
             ` ace
             ` Janina Sajka
         ` David Poehlman
         ` Wil James

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=20060719203301.GA12400@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=nickdotson@bellsouth.net \
    --cc=speakup@braille.uwo.ca \
    /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).