ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/11/20/15:39:26

From: timolmst AT cyberramp DOT net
Newsgroups: comp.os.msdos.djgpp
Subject: RHIDE Beta 6 : My mouse don't work right.
Date: Wed, 20 Nov 1996 13:49:53 GMT
Organization: CyberRamp.net, Dallas, TX (214) 340-2020/(817) 226-2020 for info
Lines: 25
Message-ID: <56v26a$95o@newshost.cyberramp.net>
NNTP-Posting-Host: pm2-13.cyberramp.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

HI,

1. My mouse doesn't work right with Beta 6. It did with beta 5. I am
running MSCMOUSE v6.23 for the Mouse Systems optical mouse. I know
that this a very old driver, but it has worked well with everything
else I have.

2. This is probably a gcc problem. When I make a project with RHIDE,
and say BUILD ALL, my computer would sometimes crash when gcc was
supposed to be running. It would never be on the first file compiled,
but about the third. I would see the command line message invoking the
compiler, then the machine would just go dead. At the time, I only had
578K available in the lower 640K. I now have 639K available, and don;t
see that problem anymore.

My question is this. Is there a certain monimum of memory that gcc, or
ld for that matter, need in the lower 640k? If so, it would be nice if
it would give an error message, and abort, rather than crashing the
computer.

THanks much for RHIDE. The GNU stuff is good software, but it is too
unix. I'm spoiled by the IDE in the Borland stuff. RHIDE makes the GNU
software much more comfortable for me. Great job Robert.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019