Double cursor in CLIPW [Was: No more XP lag with Tamedos]

[Michael Norman michael.norman@xxxxxxxx]

The details of my machine, setup (XyDos in an XP/SP2 DosBox) and
STARTUP.INT are below. In a nutshell, XY runs well in all respects save
one, a small anomaly.
PROBLEM: When I run CLIPW I get a double cursor. The second cursor appears
at the point where I invoke the CLIPW routine. If I paste the contents of
the of the clipboard, the second cursor then jumps to that point. The
second cursor then stays on screen, in that position, no matter what file I
open. In other words, the second cursor persists throughout the editing
session, here or there, depending on where I clip and paste. The size of
second cursor depends on the setting in TITLE
BAR==>PROPERTIES==>OPTIONS==>CURSOR SIZE. My normal XY cursor is set to a
non-blinking gray block; the second cursor always blinks. The normal XY
cursor also retains its shape and stays non-blinking.
TESTS: 1) In XY. I tested STARTUP.INT first (again, see below, please)
commenting out one line at a time, though clearly it made no sense to
disable the U2 lines or SETTINGS.DFL. So to test SETTINGS.DFL, I
commented-out each DF and MD setting, one setting at a time, quitting
XyWrite after each (to get rid of the second cursor), then restarting the
program and invoking CLIP. SAVESESS made this tolerable. (Another way to do
this, at Patricia's suggestion, is to use FileCompare and a virgin
SETTINGS.DFL. Or you can change only the files specs on the virgin SETTINGS
file and load that in place of your regular settings.dfl and see the
effect.) I also disabled the printer file by commenting out the printer
lines in SETTINGS.DFL; after that I looked hard at the .REG file, though I
could have missed something there. Finally I studied my .KBD file but could
not find a setting there that would cause a screen anomaly, at least in my
limited understanding of those issues. (Results of this testing are below).
2) In XP. I also tested, one at a time, all the settings in all the tabs of
EDITOR.EXE's shortcut and the tabs of the Properties dialog that drops
down from the title bar in the DosBox. Next I tested all the settings in
the KEYBOARD and MOUSE sections of the Control Panel. I also checked to
make sure, again, all my drivers were current, checked the ATI WEB site to
see if the anomaly was reported there or at the ThinkPad Forum. Finally I
disabled my antivirus program and turned off a screen utility that does
simply scaling on LCD's.
RESULTS: The only change that affected the anomaly was in CR=[x,y,z], the
setting for cursor type.
My setting is: CR=113,79,102,0. The factory setting is: CR=0,199,102,4. The
first value [x] is the important one in this case. CR=113 gives me a gray,
non-blinking cursor (My IT= setting gives me the block shape). When I
changed the first value to zero, CR=0[,y,z], my regular cursor went from
non-blinking to blinking. Now, when I invoked CLIP, instead of getting the
double cursor, my regular cursor simply changed shape, jumping from small
to medium, or medium to large, depending on the setting in TITLE
BAR==>PROPERTIES==>OPTIONS==>CURSOR SIZE. As a final note, if I start XY,
switch to FULLSCREEN, then invoke CLIP, there is no anomaly. Works fine.
But if I then ALT-ENTER back to the DosBox, the second cursor is there,
waiting for me. So this seems to be a VDM problem.
There are two old reports of double cursors, both mentioned recently in a
post, though neither involved a specific routine. Also in old posts --
search "Cursor Type" -- the setting CR=[x,y,z] is implicated in other
screen anomalies, though none of the solutions effected then work with my
problem. Again, XY is running well in all other respects.

I'd be grateful for any suggestions.

Michael Norman
=================================================
I. SETUP: XyDos 4.018 running in a VDM (DosBox or DosWindow) on an IBM T41
with XP SP2 and TAMEDOS (out of the box, no switches set). Running in the
background are Symantec AntiVirus (Corporate) and LiquidView, a utility
that sets a few appearance settings for LCD's. I have all the latest
drivers. LCD runs native at 1400X1050. ClearType is selected. XY runs well.
I cleaned up an untidy startup (latest version appended) and fixed errors
in the PATH and .KBD file that were causing some screen issues months ago.
U2, save the CLIPW routine seems to be running well too. Ver. 117 is
installed with the latest .REG. A copy of KMD.EXE is in
C:\Windows\system32. I use ACCENTS, CALLUP, SAVESESS and CLIP every day.

II. STARTUP.INT:

BX DEFAULT DR=C:\XY\Q2 ;*;
BX LOAD C:\XY\SETTINGS.DFLQ2 ;*;
BX LOAD C:\XY\XY4.KBDQ2 ;*;
BX LOAD C:\XY\XY4.MNU+C:\XY\XY4.DLGQ2 ;*;
BX SETP 1Q2 ;*;
BX LOAD C:\XY\XYWWWEB.U2Q2 ;*;
BX DSORT F,EQ2 ;*;
;*;
BX LOAD C:\XY\PERS.SPLQ2 ;*;
NR BC BX DIRQ2