From:	pwalker AT zetnet DOT co DOT uk (Paul Walker)
Newsgroups:	comp.os.msdos.djgpp
Subject:	RHIDE keyboard problem
Date:	Fri, 17 Apr 1998 19:56:43 GMT
Lines:	28
Message-ID:	<3537b2d8.8731628@news.zetnet.co.uk>
NNTP-Posting-Host:	man-091.dialup.zetnet.co.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi,

Does anyone know about / know how to solve a serious problem I have
with RHIDE?

Symptoms: doesn't accept keyboard input at all after initial "enter"
to clear brag-screen in DOS box under Win95 (4.00.95a); accepts some
keypresses under pure dos (6.20), but then goes .. very strange. :/ 

Not entirely helpful, I know, but I've not seen anything like what
happens - windows pop up and are dismissed straight away again, so
quickly I can only just see them.

CTRL-Break works once, but doesn't seem to work again. Can still use
the mouse, at least under Win95 - haven't tried again under DOS! :)

Latest versions of both RHIDE and DJGPP (fetched from ftp.demon.co.uk
- link from zippicked on delorie.com).

Thanks,


Paul
--
---- MicroSoft Windows - when do you want to crash today? ----
             FidoNet: 2:440/60.11     2:442/103.13
      -->      http://www.trak-one.co.uk/foti       <--

 I recommend using PMODE - it is faster still.  You
can then disable the CTRL-C behavior using libc calls.

If ring-0 access is all that is needed, you can use the create descriptor
functions to provide ring 0 call gates or interrupts, lock your memory, etc
to provide your own protected mode "kernel" functions with the standard
CWSDPMI.

cwsdpr0 was never planned to be a general purpose replacement for cwsdpmi.
It was written for id Software to allow using the pentium profiling 
instructions during development.  If anyone finds it useful for more than
that, great - but it's really not something I want to support.

- Raw text -