Re: CLIPW (Debugging, check list)

[Michael Norman michael.norman@xxxxxxxx]

At 1/10/2005 03:46 PM -0500, Robert Holmgren wrote:
> Put your one copy in C:\WINDOWS\system32. NOT in
> C:\WINDOWS\system! C:\WINDOWS\system is for old Windows
> v3.x drivers, and nothing else. It is there for compatibility
> with 16-bit programs, and no other reason -- because 16-bit
> programs tend to look for a directory with that name.
> C:\WINDOWS\SYSTEM is not even in the PATH! I told you to put
> the DLL at the top of the PATH. So why put it in a directory
> that isn't even in the PATH?
First, thanks very much for thinking about this. I used the check list you
sent to Paul Breeze as an orthodoxy because I thought perhaps I had two
problems, the obvious video problem and a problem with the routine (It did
not appear to be creating CLIP.TXT when it was supposed to and when it did,
the TXT file had an archive bit.) So I simply covered myself by putting
the DLL in both folders. It wasn't clear from the Breeze post that some of
the instruction on the .DLL was, I'm guessing, exclusive to his system; In
fact C:\Windows\System32 was first in my PATH and there was indeed a copy
of the .DLL in that folder. I just added a copy to C:\Windows\System, not
knowing the folder's provenance or sure of its purpose.
> I want you to paste the following commands EXACTLY as
> written onto the XyWrite command line, and execute any (or all) of
> them, individually, one at a time, in a Desktop XP window:
[NB: My cursor is set to a non-blinking block cursor. I executed each
string from both the CMline and from the Text. I quit the program and
returned after each test.]

1. dos/nv/x/z /c cmd /c exit
CMline results: Bottom of cursor starts to blink and cursor stays at end of
command string, but if I CC into the text, a regular block cursor appears
at Col 1, line 1, and a small blinking cursor is left behind at the end of
the command string on the CMLine -- the so-called second cursor. It was as
if the second cursor was under the regular cursor, blinking through it as
it sat at the end of the command string and stayed there after I CC'ed the
regular cursor into the text.
TEXT results: Same effect as above. One cursor to start with the bottom
blinking; I hit any key and move the cursor to the next Col or line,
whatever, and a small blinking cursor stays behind in the original
position, giving me two cursors in the text, my regular block cursor and a
small blinking cursor.

2. dos/nv/x/z /c cmd /c ver > $ver$.tmp

CMline results: Same as above.
TEXT results: Same as above, but... After I move the block cursor to any
new position, then XC the string a second time, the blinking cursor moves
underneath my regular cursor. If I move the block cursor off the top of it,
as it were, to yet a third position and again execute the string, the
blinking cursor again follows and slips beneath the block cursor, and so on.

3. dos/nv/x/z /c cmd /c mem.exe
CMline results: This time the regular cursor stays at the end of the
command string on the CMline line AND a blinking cursor appears *on its
own* in the text area, position: Col 1, line 8. No more hiding underneath
the block cursor. In addition this SOMETIMES turns NUMLOCK on. Quit the
program several times and repeated this. Same results.
TEXT results: Same as above. Two distinct cursors, one normal, one small
blinking cursor. Note: the small blinking cursor always appears 11 lines
down from the line regular cursor and always sits in Col 1.
> Is this what you've been talking
> about?
Yes. When I run CLIP I get the same behavior as I did when I ran strings 1
and 2 above -- a small, medium or large cursor (depending on the setting in
the *Cursor-Size* drop-down dialog), always appears underneath the regular
cursor. CMline dos/nv gets rid of it.

Thanks.

Michael Norman