Re: DOS Hex2bin

From	"Kerr-Mudd,John" <notsaying@invalid.org>
Newsgroups	alt.lang.asm, alt.msdos.programmer
Subject	Re: DOS Hex2bin
Date	2019-11-20 17:12 +0000
Organization	dis
Message-ID	<XnsAB0DAF04473BFadmin127001@144.76.35.198> (permalink)
References	<XnsAB01C2CC3DFCEadmin127001@144.76.35.198> <XnsAB0D691E76D01admin127001@144.76.35.198> <XnFAB0DB3DAB6030T6A7E15I9M1B9U4S@127.0.0.1>

Cross-posted to 2 groups.

Show all headers | View raw

On Wed, 20 Nov 2019 16:40:46 GMT, NimbUs <nimbus@xxx.invalid> wrote:

> Kerr-Mudd,John wrote as news:XnsAB0D691E76D01admin127001@
> 144.76.35.198:
> 
>> The problem then is that keyboard input from int 0x16 is also 
> redirected; 
>> so it's unusable! 
> 
> Are U sure ? Console I/O "redirection" is a DOS feature - not a BIOS 
> one !
> Even if the DOS "CON" input has been redirected, it will only affect  
> the DOS int 21h readchar functions. You are still able to read the 
> keyboard using BIOS int 16h. 

I shudda tried it!! Doh!

240 byte monchrome sokoban; further testing reqd, then if there's space 
I'll display "moves taken".


> 
> My googlefu is weak; anyone here recall how to code 
>> (just the 4 csrkeys, and esc to exit) a keyin that *isn't* 
> redirected?
> 
>> Must I inf-loop around "in al,0x60"?
> 
> You would not need/want to do such a thing ordinarily, nor would you 
> need/want to hook the int 9 driver, nor int 15h/4F either. Or did I 
> misunderstand the particular situation you were facing ?
> 
No quite; I was barking up the wrong tree.


-- 
Bah, and indeed, Humbug.

Thread

DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-08 19:08 +0000
  Re: DOS Hex2bin Mike Gonta <mikegonta@gmail.com> - 2019-11-08 12:05 -0800
    Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-08 21:21 +0000
      Re: DOS Hex2bin Mike Gonta <mikegonta@gmail.com> - 2019-11-08 13:57 -0800
        Re: DOS Hex2bin Herbert Kleebauer <klee@unibwm.de> - 2019-11-09 08:11 +0100
          Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-09 09:06 +0000
  Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-20 10:19 +0000
    Re: DOS Hex2bin NimbUs <nimbus@xxx.invalid> - 2019-11-20 16:40 +0000
      Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-20 17:12 +0000
        Sokoban was Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-11-24 18:59 +0000
          Re: Sokoban was Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-03 11:37 +0000
            Re: Sokoban was Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-03 16:53 +0000
              Re: Sokoban was Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-03 20:13 +0000
                Re: Sokoban was Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-17 18:37 +0000
                Re: Sokoban was Re: DOS Hex2bin Frank Kotler <fbkotler@myfairpoint.net> - 2019-12-17 16:23 -0500
  Re: DOS Hex2bin drb@ihatespam.msu.edu (Dennis Boone) - 2019-12-17 18:07 -0600
    Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-18 09:30 +0000
      Re: DOS Hex2bin "Kerr-Mudd,John" <notsaying@invalid.org> - 2019-12-18 10:33 +0000
      Re: DOS Hex2bin drb@ihatespam.msu.edu (Dennis Boone) - 2019-12-19 20:16 -0600

csiph-web