Thanks for reading and for commenting.  I must admit that Emacspeak
sounds very interesting.  But I'm still not sure whether this is just
a screen reader for Linux or whether it's an accessible shell ontop of
Linux that uses it's own commans etc.  If the latter, it might be
worth experimenting with it.  But if it's just a screen reader, then
I' need to learn a whole new set of commands and deal with the strange
quirks of Linux.  As I've said, this does not interest me, even though
it's based off of Unix, which is older than DOS itself if memory
serves..

  I really can't give an opinion on the functionality of the Microsoft
PowerShell, except to say that it's a shell and not an operating
system.  Therefor, while I would be able to do various things from the
prompt, once I opened a program, I'd still be dealing with a graphical
Windows application and usually not one designed with keyboard usage
in mind.  The same, of course, holds true in programming.  My intent
there is to write console-based tui programs and to avoid dealing with
object-oriented languages, particularly those which use graphical
symbols instead of plain English in the programming and simple y/n
prompts, hotkeys and menus in the user end.  I could be wrong, but
something tells me that Windows can't handle that.  I'm not sure if
these (or clones of them) are still being developed but are BEOS and
OS/2 accessible?  If so, what are they like i.e. cli systems or gui?
I'd also absolutely love to play with CP/M, even just once, since DOS
was based off of it.  I know it was developed for several years after
1981 and that there were screen readers made for it.  I'd like to
compare the structure of it with MS-DOS.

  At any rate, my love of DOS goes way back and I've been trying to
learn it for a very long time.  Apple IIs and Dr. Pete's Talking
Writer in elementary school  aside, I started using computers in
around 1996.  By that time, DOS was already obsolete to most people
and no one would teach me what I wanted to know.  I'd refused to learn
Windows prior to then and had started on my own little adventure using
MS-DOS 5.0, Word Perfect 5.1, DOS for Dummies tapes that I got from
the NLS, a Word Perfect tutorial from the local library and a machine
that I'd inherited from a friend of the family.  But eventually, the
computer, with a 386 cpu, crashed and I was forced to use Windows.  I
then began acquiring some DOS tech to the point that I had at least
two Echo  synths, along with an Accent SA, and two KeyNote Gold
laptops with stripped-down versions of MS-DOS 6.21 and the amazing
KeyNote Gold Voicecard synth inside.  But then, I lost the cable
needed for the synth.  I didn't know that autoexec.bat could be
skipped when booting so couldn't start the machine without having the
Voicecard connected.  By the time I went to college, the old tech was
put away.  I graduated from college four years ago and found that
crazy cable about two years ago, so now have time to get back to the
system I love.  Only now, I've outgrown the laptop and want to expand
to a newer and better computer, which is why I'm having that custom
one built.  To be honest, I'm very excited about trying this enhanced
DR-DOS and seeing all the wonderful enhancements it has when compared
with the Microsoft variety.  Ever since I began my interest in
computers, I'd heard that MS-DOS 6.22 was the last release of their
version of the os as a stand-alone product.  Even Wikipedia confirms
it.  But yesterday, I read that there really is an MS-DOS 7 and that
it was made open source?  Is that right?

  As a sidenote, I was also very much into Apple IIs during my high
school years to the point that I was able to save an IIGS from
destruction.  The high school was throwing it out but gave it to me
instead, along with the printer, extra floppy drive and software.  I
then bought  Proterm and TextTalker from APH.  This was about 2002 so
they only had three in stock).  I then put the machine away and
haven't seen it since.  While I'll never use it as my primary os, I'd
love to try it out, especially for getting on the net.  Ironically, I
have far more information from magazines online on using Apples from
the blind perspective than pcs.

Eleni

On 7/25/10, Alasdair King <alasdairk...@gmail.com> wrote:
> Interesting perspective. Have you tried more modern commandline
> interfaces based on non-DOS systems?
>
> Emacspeak is an audio text-based interface to Linux:
> http://emacspeak.sourceforge.net/
>
> PowerShell is Microsoft's new commandline interface. You can access
> COM and interact with other tools through it. A quick try suggests it
> works with Narrator:
> http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx
>
> Alasdair
>
>
> On Thu, Jul 22, 2010 at 2:45 PM, Eleni Vamvakari <magkis...@gmail.com>
> wrote:
>> Hi there,
>>
>>  I wrote this in response to a personal e-mail sent to me the other
>> night and then shared it with the Blind Computer Users list but forgot
>> to send it here.  But after today's discussion, it occurred to me that
>> some of you are curious about it as well.
>>
>>  I'll add this before starting.  Apple IIs in school  aside, I
>> started using computers in around 1996.  By that time, DOS was already
>> obselete and no one would teach me what I wanted to know.  I'd refused
>> to learn Windows prior to then and had started on my own little
>> adventure using MS-DOS 5.0, Word Perfect 5.1, DOS for Dummies tapes
>> that I got from the NLS, a Word Perfect tutorial from the local
>> library and a machine that I'd inherited from a friend of the family.
>> But eventually, the computer, with a 386 cpu, crashed and I was forced
>> to use Windows.  I then began acquiring some DOS tech to the point
>> that I had synths and two KeyNote Gold laptops with stripped-down
>> versions of MS-DOS 6.21.  But then, I lost the cable needed for the
>> synth and by the time I went to college, the old tech was put away.
>> Well, I graduated from college four years ago and found that crazy
>> cable about two years ago, so now have time to get back to the system
>> I love.  Only now, I've outgrown the laptop and want to expand to a
>> newer and better computer, which is why I'm having that custom one
>> built.  Anyway, here's the essay.
>>
>>  Many people throughout my life have asked me why I love DOS so much.
>>  Not being a truly technical person, I could only give a few reasons
>> from my limited experience.  I love old tech in general, and avoid
>> touch screens on things that work perfectly fine with dials, switches
>> and real buttons.  But that's not the only reason why I love DOS. It's
>> a fast, efficient, stable, keyboard-friendly system which doesn't
>> require alot of power, hard drive space, ram, speed or money passed
>> the initial cost of a synthesizer, a screen reader if you get
>> VocalEyes (sold but no longer supported), since all others are now
>> free.  Even the machine itself is also cheap, since you don't need a
>> top of the line computer to run this os.  Of course, if you choose to
>> get scanning software and a braille embosser, that will add money to
>> the overall cost, but even those can be bought at a good price if
>> you're lucky enough to find them.  Most of the mainstream software is
>> also freeware, shareware or very cheap. The newer versions of the
>> operating system, like FreeDOS and Enhanced DR-DOS, are open source,
>> meaning that you can tweek them to meet your needs if you have the
>> technical knowhow. They're also updating the various versions to be
>> compatible with modern hardware and formats so you're not limited to
>> using only older technology.  Enhanced DR-DOS was just updated last
>> year and has it's own built-in multitasker, available since the old
>> DR-DOS days, which, if it works with a screen reader, means that
>> you're not stuck using only one program at a time.  As for me
>> personally, I like programs that use the tui (text user interface) and
>> the command line or that have nice hotkeys and/or menus built in and
>> that don't have tons of graphics, most of which are unnecessary or
>> which complicate things without reason.
>>
>>  For the longest time, that was as far as I could go with my answer.
>> But after 14 years, I've found the page that explains more than I ever
>> could about why DOS is still a viable option today and why it
>> shouldn't be tossed aside.  At the below link, you'll find 37
>> fallacies about DOS and why they're all wrong.  Some are common
>> misconceptions and some even surprised me.  It's a bit long but
>> definitely worth reading, especially if you know alot about operating
>> systems and/or are looking for an alternative one that will keep you
>> on budget and won't give you a headache.
>>
>> http://www.chebucto.ns.ca/~ak621/DOS/DOS-Fal.html
>>
>>  Many have said that software and resources are no longer available
>> for DOS.  If they mean ones for adaptive technology, then sadly,
>> they're right.  But there's alot out there for the mainstream.
>>
>> http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php
>>
>> and
>>
>> http://www.chebucto.ns.ca/~ak621/DOS/DOS-Head.html
>>
>> (especially the second one) are both gold minds of material and have
>> just about everything you could ever want, from links to other
>> websites, including ones with different varieties of DOS, to programs,
>> to tutorials and books on using the os, various programs and even
>> programming itself, to tips and even a little humour.  The only things
>> they doen't have, as I've said, are reviews and tips on using software
>> from the blind point of view and information on finding and using
>> adaptive technology.
>>
>>  I hope this explains my point of view a bit more clearly and that
>> some people here will be able to help me.  I'd really like to get my
>> system up and running.
>>
>> Talk soon,
>> Eleni
>>
>> For answers to frequently asked questions about this list visit:
>> http://www.jaws-users.com/help/
>>
>
>
>
> --
> Alasdair King
>
> For answers to frequently asked questions about this list visit:
> http://www.jaws-users.com/help/
>

For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/

Reply via email to