public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Jude DaShiell <jdashiel@shellworld.net>
To: blinux-list@redhat.com
Subject: Re: help please
Date: Wed, 14 Aug 2002 23:13:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.BSF.4.44.0208142302440.97435-100000@server1.shellworld.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141107560.26724-100000@TekRD.grg.afb.net>

Well, I suppose I've been working in a production environment for a bit
too long.  In that kind of environment it doesn't pay to try something and
then find out you have something on the screen three days later which
needed to be answered with yes rather than y and you didn't know that
because the documentation no longer matched the actual software output or
you hadn't been able to get into the documentation because that was on the
disk too which still isn't installed.  If someone had a project due in
part of that time, that's a great way to get unemployed real fast and for
cause at that.  Whenever I've done dos installations in my more recent
years I've tried to always have a talking installation disk and computer.
With windows 98 that didn't work.  Part of why Microsoft put windows
narrator into windows 2000 was because of the problems I had installing
win 98 at first.  After awhile I got so much practice installing win 98 I
could do it far easier.  I haven't tried installing windows 2000 with
narrator but a side benefit narrator has made possible was for nmci, our
organization hasn't yet been able to get any of the professional screen
readers through pop-in-the-box testing so the only way to have a talking
nmci computer is by using windows narrator.  I understand much of the
other section 508 hardware and software is similarly held up too.





  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Vitor Oliveira
 ` 'Georgina'
   ` Vitor Oliveira
     ` 'Georgina'
       ` Vitor Oliveira
 ` Jude DaShiell
   ` Janina Sajka
     ` Jude DaShiell [this message]
       ` Janina Sajka

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.BSF.4.44.0208142302440.97435-100000@server1.shellworld.net \
    --to=jdashiel@shellworld.net \
    --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).