Nice ones, especially the clipboard test. I came across this question many
times before, without a proper solution. Will see what Raymond has to say.
--
Ramesh, Microsoft MVP
Windows XP Shell/User
Windows XP Troubleshooting
http://www.winhelponline.com
"David Candy" <.> wrote in message
His form has been poor. Flintoff has taken on the role of stock bowler
instead of strike to cover for Kallis.
I just posted this to Raymond's suggestion box.
There are some problems, not that common, where cut and paste stop working.
I thought about it and came to the conclusion that an app has opened but not
closed the clipboard. So I wrote a program to examine the clipboard. I
didn't know how to test it (I don't have that problem) so I wrote some
programs to open and close the clipboard and confirmed that symptons people
report match that of a locked clipboard (in notepad copy is available but
does nothing and paste in not available).
If a invalid hwnd (and GetActiveWindow is invalid in this sense but not
GetDesktopWindow() but this might be because I'm passing someone's else's
hwnd) is passed to openclipboard() then any attempt by another program to
open it will fail but will unlock the clipboard so a second call will work.
I have a sense and so do others that one frequently has to copy data twice.
Do you know anything about this?
* All references to lock is the state of the clipboard not memory lock
functions a la 16 bit clipboard.
Also I asked Larry O via mail this
why are some stop codes in the form
0x1nnnnnnn which has the same meaning as 0x0nnnnnnn. Is this always true
(not all stop codes are documented as I found yesterday).
But he, being a low level programmer, doesn't know what a stop code is. So I
had to call it a BUG CHECK CODE (it's official name - stop is only in the
UI).
Yesterday I found one of your suggestions in the list. Can't remember what
you asked. Did it get answered?