From:	Paul Brannan <brannanp AT musc DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RHIDE and WPE -- both broken
Date:	Fri, 24 Jan 1997 00:00:41 -0800
Organization:	Medical University of South Carolina
Lines:	28
Message-ID:	<32E86C29.5B31@musc.edu>
References:	<32E5B64A DOT 3CFA AT musc DOT edu> <32E5EF6D DOT 33B9 AT Mathematik DOT tu-chemnitz DOT de> <32E6FAE6 DOT 2F6F AT musc DOT edu> <32E75731 DOT 3FFF AT Mathematik DOT tu-chemnitz DOT de>
NNTP-Posting-Host:	atrium.musc.edu
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> Does this mean, that you cannot use the keyboard after ANY keypress??

Yes.  It was especially annoying because the first key I would press 
would be the enter key (to get rid of that dialog box).

> If that's true this is really new for me and I think you should post
> here you system configuration (autoexec.bat, config.sys and dejgpp.env).

Actually, I don't need to do that, because I think I found the culprit.  
I traced the problem to a program that I run, called kbxtnd.com.  The 
program is actually very useful, because it speeds up the keyboard (same 
way as doing mode con rate=30 delat=1), but most importantly because it 
extends the keyboard buffer to 255 bytes.  I find this most helpful when 
I am running a program and I don't want to have to wait on it to finish 
before I start typing the next command.

When kbxtnd extends the keyboard buffer, it basically opens up the area 
in memory located after the keyboard buffer (which I think is located at 
0:480?) for use by the keyboard buffer.  I think there might be something 
in that data area that some programs might use (some EGA parameter list 
or something).  I'm not sure what the exact cause of the problem is, but 
it has something to do with this program.

It would be nice to be able to run RHIDE after loading the keyboard 
extender, but I can certainly live without it.

Paul Brannan
brannanp AT musc DOT edu

- Raw text -