Groups > comp.os.msdos.programmer > #3970

Re: MSDOS 3.2 COM ports

From	"R.Wieser" <address@not.available>
Newsgroups	comp.os.msdos.programmer
Subject	Re: MSDOS 3.2 COM ports
Date	2021-04-26 14:54 +0200
Organization	Aioe.org NNTP Server
Message-ID	<s66d72$10j2$1@gioia.aioe.org> (permalink)
References	(4 earlier) <80bdb037-707d-4eac-b5f6-050f3d775761n@googlegroups.com> <s639fu$ag9$1@gioia.aioe.org> <08aa84aa-2c84-4013-821c-67e04b7b4ceen@googlegroups.com> <s661tt$vvk$1@gioia.aioe.org> <d6ac0b06-f034-41fe-b9ec-c3d0fb525d10n@googlegroups.com>

Show all headers | View raw

Muta,

> Any reason why I shouldn't expect a direct response
> from the BBS running on my Windows machine?

Apart from the one you already named ? :-)

Even on your own 'puter you can do stuff that takes a while to complete. 
Just take searching for a certain file (dir filemask.ext /s/b) - or worse : 
searching for a file with certain contents (grep -idl "some text" 
filemask.ext)

> And if my BBS is in turn waiting on the news server
> on the internet, I don't see that there is much choice
> but to wait for that.

For either of the above examples I gave I can press ctrl-c to abort.    I 
can easily imagine that a BBS would accept a key stroke or command to do the 
same.    But as your client program is using blocking I/O you could be 
pressing keys all you want, but those won't be send until after you got your 
response back from the BBS ...

Granted, blocking I/O is much easier to work with.  But keep the downside of 
it in mind.

Regards,
Rudy Wieser

Thread

MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-23 16:19 -0700
  Re: MSDOS 3.2 COM ports Grant Taylor <gtaylor@tnetconsulting.net> - 2021-04-23 18:26 -0600
    Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-23 18:47 -0700
      Re: MSDOS 3.2 COM ports Grant Taylor <gtaylor@tnetconsulting.net> - 2021-04-23 20:08 -0600
        Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-23 20:40 -0700
      Re: MSDOS 3.2 COM ports Grant Taylor <gtaylor@tnetconsulting.net> - 2021-04-23 20:14 -0600
      Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-04-24 10:07 +0200
        Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-24 15:04 -0700
          Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-04-25 10:32 +0200
            Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-26 01:32 -0700
              Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-04-26 11:42 +0200
                Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-26 04:42 -0700
                Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-04-26 14:54 +0200
                Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-26 14:10 -0700
                Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-04-27 11:40 +0200
                Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-04-27 03:56 -0700
                Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-05-01 21:56 +0200
                Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-05-01 14:36 -0700
                Re: MSDOS 3.2 COM ports "R.Wieser" <address@not.available> - 2021-05-02 10:29 +0200
                Re: MSDOS 3.2 COM ports "muta...@gmail.com" <mutazilah@gmail.com> - 2021-05-02 02:14 -0700
    Re: MSDOS 3.2 COM ports Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2021-04-28 14:15 +1000

csiph-web