Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!gsbsun!valley
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Newsgroups: comp.os.msdos.apps
Subject: Re: Desqview and Ctrl/Alt/Del
Keywords: desqview ctrl/alt/del trapping programming
Message-ID: <1991Apr20.025812.6577@midway.uchicago.edu>
Date: 20 Apr 91 02:58:12 GMT
References: <1991Apr19.174531.15849@midway.uchicago.edu> <22485@yunexus.YorkU.CA>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 26

rreiner@yunexus.YorkU.CA (Richard Reiner) writes:

>valley@gsbsun.uchicago.edu (Doug Dougherty) writes:

>>I have tried every value (0-4) of the "Keyboard Conflict" variable in
>>the .DVP file, in conjunction with a "NOBOOT" TSR, but in every case, DV
>>closes the window when C/A/D is struck.

>Recent versions of DV allow additional values, not just 0-4, for the
>keyboard conflict setting.  See your DV manual for details.  Perhaps
>one of the new values does what you need.

Yes, I've since noticed that.  I wrote the orig item from work, using an
old version of DV (that only had 0-4).  At home, I run a more recent
version, that supports 0-F.  Though, I'm not sure I want to try all those
values (Who's got that kind of time??? [heh] [heh])

Incidentally, the DV manual only talks about the 0-4 set, and even that
only incompletely.  They describe 0 & 4 and then say 1, 2, & 3 are in
between, though not necessarily in a strictly linear ordering...

DesqView: Great software, tacky documentation, and piss-poor support.
(But I love it anyway...)
--

	(Another fine mess brought to you by valley@gsbsun.uchicago.edu)