public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Maurilio Longo <maurilio.longo@libero.it>
To: Axel Holscher <Axelhols@vst.co.za>
Cc: 'Stas Sergeev' <stssppnn@yahoo.com>,
	dosemu-devel@lists.sourceforge.net, linux-msdos@vger.kernel.org
Subject: Re: [Dosemu-devel][Dosemu-bugs][DOSEMU BUG] No output received onLinux  Serial deviceswhen send ing data vai DOS COM port mapping (fwd)
Date: Thu, 13 Mar 2003 18:04:45 +0100	[thread overview]
Message-ID: <3E70BA2D.CF1B07F9@libero.it> (raw)
In-Reply-To: 69AFA5E5DDC59046A1604A8E3DFB2561085908@exchange

Alex,

even with this patch applied I can print to my serial printer with a

dir > com1:

but not from my clipper (protect mode, telepathy as comx: access library) app...

To be more precise I can print very short strings, that is

tp_open(1...)  // open com port 1
tp_send(1, "hi there")  // send string
tp_close(1)

works, but if there are more tp_send() one after the other I get no output!?!!

dosemu 1.1.1.x was working nicely

:(

regards.

Maurilio.


PS. On a side note, hogthreshold releases too much cpu when a clipper app is
running since runtime of clipper calls dos int-XX (I don't have it handy) to
retrieve time when it has nothing to do and this happens even during keyboard
input. Dosemu instead of releasing remaining of cpu slice does a sleep of a
certain amount of time, this causes sluggish keyboard input.


Axel Holscher ha scritto:

> Shot! The patch supplied fixes our COM/Serial port output problem.
>
> That's what I call swift service with as smile ;-)
>
> Many Thanks!
> Axel
>
> -----Original Message-----
> From: Stas Sergeev [mailto:stssppnn@yahoo.com]
> Sent: Thursday, March 13, 2003 2:18 PM
> To: dosemu-devel@lists.sourceforge.net
> Cc: Axel Holscher; Maurilio Longo; linux-msdos@vger.kernel.org
> Subject: Re: [Dosemu-devel][Dosemu-bugs][DOSEMU BUG] No output received
> on Linux Serial deviceswhen send ing data vai DOS COM port mapping (fwd)
>
> Hello.
>
> Bart Oldeman wrote:
> > Hmm, seems that dosemu-bugs is still used (even though it's an
> > auto-responder) so I'm forwarding any useful messages.
> Are you supposed to forward also
> the replies? :)
>
> > all aspects  except that it fails to send out data to any of the serial
> > devices via the mapped DOS COM ports.
> To get the serial back on the track
> this patch is required before anything
> else:
> http://sourceforge.net/tracker/download.php?group_id=49784&atid=457449&file_
> id=43528&aid=693722
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
 __________
|  |  | |__| md2520@mclink.it
|_|_|_|____| Team OS/2 Italia



      reply	other threads:[~2003-03-13 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 16:07 [Dosemu-devel][Dosemu-bugs][DOSEMU BUG] No output received on Linux Serial deviceswhen send ing data vai DOS COM port mapping (fwd) Axel Holscher
2003-03-13 17:04 ` Maurilio Longo [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=3E70BA2D.CF1B07F9@libero.it \
    --to=maurilio.longo@libero.it \
    --cc=Axelhols@vst.co.za \
    --cc=dosemu-devel@lists.sourceforge.net \
    --cc=linux-msdos@vger.kernel.org \
    --cc=stssppnn@yahoo.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