public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "John J. Boyer" <director@chpi.org>
To: "blinux-list@redhat.com" <blinux-list@redhat.com>
Cc: <dave@mielke.cc>
Subject: Re: dosemu and com port problem resolved
Date: Sat, 23 Mar 2002 19:46:31 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0203231943160.7892-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0203231032220.547-100000@maranatha.chartermi.net>

Cheryl,
Could you explain how to get dosemu started quickly with enough memory
for MegaDots and not using com1? I've downloded dosemu-1.3.1 and want to
gert to work. If you also received a personal message from me, I'm
posting this again because you may not be receiving my e-mail again or I
might not be receiving yours. My apogies to others on the list, but I
think this might be of interest to some of them also.
John
On Sat, 23 Mar 2002,
Cheryl Homiak wrote:

> I finally am able to use serial ports with dosemu; there is a bug in the stable
> version that won't allow lock files to be created without suid root. I solved
> this by obtaining and compiling the 1.1.3 version (development) from
> www.dosemu.org. For any interested debian users, I understand that the
> maintainer of the package has fixed the bug in our 1.0.2.1--whatever version and
> the upgrade will be out shortly.
> Pcisk and megadots both work with dosemu; you need to put in the number of
> kilobytes for dpmi in the dosemu.conf for megadots to work.
> The one catch turns out to be that brltty is stopped dead in its tracks, I
> assume during the initialization process when starting dosemu. This does not
> happen with speakup, however; speakup keeps
> going right to the dos prompt and beyond. It isn't probably just the piece of
> equipment being used, as I was using the same equipment for brltty and speakup.
> However, it is possible to kill brltty before entering dosemu and
> then start up a DOS speech screen reader on the same equipment. It is also
> possible simply not to include the serial port on which brltty is running in
> your dosemu.conf file. In that case, brltty keeps running happily on the dosemu
> console as well as all other consoles during the dosemu session. If one does
> accidentally leave brltty installed when starting dosemu, brltty dies but can be
> restarted again on exiting dosemu with a restart command (chord-r with
> braillelite), so apparently brltty
> isn't completely killed. In fact if you assume it was killed and type 'brltty"
> after exiting dosemu, you will probably be dealing with more than one brltty!
> At any rate, I'm happy to have access to the serial ports under dosemu now.
> thanks to all who helped.
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

-- 
Computers to Help People, Inc.
http://www.chpi.org
825 East Johnson; Madison, WI 53703





      parent reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Dave Mielke
 ` John J. Boyer [this message]

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.33.0203231943160.7892-100000@localhost.localdomain \
    --to=director@chpi.org \
    --cc=blinux-list@redhat.com \
    --cc=dave@mielke.cc \
    /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).