home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!junkyard!granz
- From: granz@junkyard.UUCP (David Granz)
- Newsgroups: comp.os.msdos.desqview
- Subject: Re: Frozen mouse in DVX when saving memory
- Message-ID: <1974@junkyard.UUCP>
- Date: 4 Jan 93 00:13:35 GMT
- References: <168CDC073.DIXONW@arizvm1.ccit.arizona.edu>
- Distribution: world,local
- Lines: 29
-
- In article <168CDC073.DIXONW@arizvm1.ccit.arizona.edu>, DIXONW@arizvm1.ccit.arizona.edu (Bill Dixon) writes:
- >
- > After following David Granz's procedure for saving mouse memory by
- > placing it in the process space of the server (see FAQ A22), my mouse
- > has a tendency to freeze up, but only under certain circumstances. It
- > seems to occur only after opening a window running WP5.1. The mouse
- > arrow still appears in the upper right corner but will not move. Within
- > WP the block mouse will move; shutting down WP has no effect on the
- > arrow mouse.
-
- The trick I suggested to save some memory by loading the mouse
- driver into the server process will only work if you never use Direct screen
- mode programs that use a mouse. As far as I can tell, as long as your program
- that wants to see a mouse is within a X window, DVX creates an appropriate
- INT33 link for that process. This is done because the X server actually owns
- the mouse, not the windowed process.
-
- Direct video processes do not get this created INT33. If you
- load a mouse driver in that Direct video process, that mouse
- driver will work OK, but it will mess up the server loaded copy.
- If you must run a mousing program direct screen... then you will have
- to load the mouse driver before you start DVX.
-
- If you load a mouse driver before you start DVX, the copy of the
- mouse driver you try to load with my trick, will simply be not loaded and the
- system should run just fine anyway.
-
- -Dave Granz
- granz@junkyard.UUCP
-