Sas window winlogon.exe application error

sas window winlogon.exe application error

Find answers to Windows XP displays SAS winlogon.exe application error memory at address unable to write to location from the expert community at. I am getting the error after installing the upgrade from 98SE to W2. The exact error is SAS window.winlogon.exe No Disk There is no disk in the drive. The message body indicates that the problem is that 'c:\windows\winlogon.exe'. The cacls would have provided the permissions to access the file.

Related Videos

What if you delete winlogon.exe on your computer?

Sas window winlogon.exe application error - apologise, but

:)">

My goal is to exceed Bill Gates.
SetROP2(R2_XORPEN) and don't forget to redraw the old line before drawing the next one.

--
-Blake (com/bcdev/blake)
Hi.
I do so.The color of the line I drawn is changed.But the line didn't dispear.Why?
That's the second part of what I wrote earlier. You have to remember the coordinates to which you last drew the line. Then on a mouse move you redraw it again at the old location to erase it and draw it at the new location.

--
-Blake (com/bcdev/blake)
I know the principle of the procedure.I use the SetRop2() function to realize it.But which parameter should I select? R2_NOT? Or R2_XORPEN?Almost all parameter I had test.None looks like correct.
And I've another question.I wrote message processed module associate to mousemove to draw line.But when the window is restore from behind other window,the line dispeared.Why?How can I resolve it?
Please help me!If you resolve my question,I can buy some gift for you if you want.;)
R2_NOT will work, it simply inverts the background pixels and ignores the pen.

R2_XORPEN will work better, as it lets you controlly the visual result better, using a dashed pen for example.

If it isn't looking correct I suspect you are not redrawing over the previous line exactly.

Things you draw during mousemove are not permanent. Your application needs to redraw everything, including the newly added line, when handling WM_PAINT as well.

--
-Blake (com/bcdev/blake)
I have laboriously coded around this little problem for years and I know that the solution is quite simple. But I am resistant to change and hate having to delve into documentation.

I am getting that "class already defined" error message when I include the same header file in more than 1 source file.

Here is what is happening:

ClassX - a user defined class
Window1 - the apps main window
Window2 - a modal dialog box invoked from Window1

Window1 has an instance of ClassX and so has "#include ClassX.h" in its header file (and won't compile without it of course)

Window2 has an instance of ClassX and so needs to "#include ClassX.h" in its header file

But it can't because it throws that error "C2011: 'ClassX' : 'class' type redefinition" error


Why is it that you can include headers like "afxdb.h" in a zillion files and not get this error?

If the compiler knows that the class is already defined, then why does it need the header file in both places?