From: cpt.kirk@1tree.net
To: speakup@braille.uwo.ca
Subject: Re: another newbie
Date: Sun, 2 Apr 2000 09:55:39 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10004020944120.3550-100000@rocky> (raw)
In-Reply-To: <NDBBJGODCODIKBMJDLOOAEHJCAAA.rvkassen@earthlink.net>
I remember seeing what the root password starts as, but can't help you
with that one. But I would not so much worry about destroying data. Linux
is actually less likely to let you wipe out the system or destroy data
then is Winblows. The thing is that if you spend your time in a
non-privledged account, you can't destroy any more then data local to that
account.
As for keeping Winblows, there are two things that I can think of for you
to do so. The first is OCR software (if you have it). I have not found
that in Linux yet. The other is if you have a need to use M$ Office or
similar programs for interchangability reasons. For those using X, that is
less an issue. But since your using speech, then I don't know of any
method of reading the screen inside X. (Though shell scripts can let you
use some X programs.)
As for the formatting every year, you are another victim of M$ outsourcing
program. Having been a contractor at a M$ facility I can assure you that
M$ does not endorse its support personel passing on a regular format
recomendation to its customers. The thing is that most of their support
comes from people who work with no direct M$ contact. Further, the average
tenure at said company is less then 6 months. And the first month is
spent in a class that blows over the top of 80% of the people's heads.
Such leads to people telling customer's that things such as a disk utility
(scandisk) can actually solve program errors (other then those dealing
with disk access).
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Your fly might be open (but don't check it just now).
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
Ron Kassen
` Buddy Brannan
` Ron Kassen
` Buddy Brannan
` Buddy Brannan
` cpt.kirk
` Geoff Shang
` Ron Kassen
` Geoff Shang
` Scott Howell
` 3com network driver (was another newbie) cpt.kirk
` Mike Gorse
` another newbie Christopher Moore
` Triple Talk Janina Sajka
` cpt.kirk [this message]
` another newbie William F. Acker WB2FLW +1-303-777-8123
` cpt.kirk
` Chuck Hallenbeck
` William F. Acker WB2FLW +1-303-777-8123
` Ron Kassen
` Geoff Shang
` Jacob Schmude
Another newbie Jack Daniels
` Thomas Ward
` Jack Daniels
` Janina Sajka
` Georgina
[not found] ` <Pine.LNX.4.33.0111241042310.3950-100000@toccata.grg.afb.ne t>
` Jack Daniels
` Gregory Nowak
` Jack Daniels
` Georgina
` Jack Daniels
` Thomas Ward
` Jack Daniels
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.10.10004020944120.3550-100000@rocky \
--to=cpt.kirk@1tree.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).