From: PRASADSL@iocl.co.in
To: blinux-list@redhat.com
Subject: RE: weasel Pc
Date: Sat, 16 Mar 2002 07:05:16 +0530 [thread overview]
Message-ID: <116992677F52D51194E100508B5542A5A47022@DCRBR1> (raw)
one of my friend had been using a gadget called wierdwire ..it just
automated chip having a embedded linux...which sees the bios and dictate
things ...you can manipulate it through keyboard...
but yes one draw back ..once pc boots up it is unable to dictate any nore as
it has a very low memory and the vendor said that low mem was kept to
control its price ...anyways after pc boot up u do not even need one....
the gadget is an indian make ...a local vendorer ...lemme check whether they
are still in business or not ...due to slow down many companies closed :(
sachin
and yes plz do not mind the discalimer which will be attached to this mail
..i know its frustating but still i am helpless
-----Original Message-----
From: Cheryl Homiak [mailto:chomiak@chartermi.net]
Sent: Saturday, March 16, 2002 7:03 AM
To: blinux-list@redhat.com
Subject: weasel Pc
wondered if anybody had any experience with or knowledge of this product.
Url is
www.realweasel.com/intro.html
I thought I read a while back that a blind person had put this in his
computer
and was able to use it for reading what comes up in the bios before boot
and, if
I understood correctly, he could then also make changes with sighted help.
but
I'm not sure about this. there's apparently both an ISA and a PCI version.
Not
saying I'd rush out and buy one or that i necessarily want to give up one of
my
slots to this (except temporarily when need arises), but it is frustrating
not
to be able to check bios settings without sighted help. Any input on this,
especially if anybody has had firsthand experience, would be appreciated.
TIA.
_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/blinux-list
****************************************************************************
This electronic communication and any accompanying document is being
transmitted over the Indian Oil Network and contains confidential
information that is for the exclusive use of the individual or entity to
which it is addressed and is protected against unauthorised disclosure. If
the reader of this message is not the intended receipient or the employee or
agent responsible to deliver to the intended receipient, or is not intended
to act on it, be aware that any disclosure, dissemination, distribution or
copying of this communication, or the use of its contents is prohibited and
is likely to be attended by legal consequences. If you have received this
communication in error and/or are not the intended receipient, please
immediately notify the undersigned or Indian Oil Corporation Ltd. at the
telephone or the fax number or email address given above and permanently
delete the original message from your email system. Whilst this mail has
been checked for all the known viruses, recipients should undertake their
own virus checking as Indian Oil Corporation Ltd. will not accept any
liability whatsoever
****************************************************************************
next reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
PRASADSL [this message]
-- strict thread matches above, loose matches on Subject: below --
Cheryl Homiak
` philwh
` Brent Harding
` philwh
` Katsuaki Watanabe
` Mario Lang
` Brent Harding
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=116992677F52D51194E100508B5542A5A47022@DCRBR1 \
--to=prasadsl@iocl.co.in \
--cc=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).