'긁적긁적..'에 해당되는 글 5건

  1. 2016.02.26 MS driver sample bsod
  2. 2016.02.18 vmware host/guest 이동 할때 numlock 토글 문제
  3. 2016.02.03 office군 제어 관련 자료
  4. 2015.12.16 __debugbreak enable/disable
  5. 2015.11.18 get sid from sessionid
2016. 2. 26. 13:54

git에서 Windows-driver-samples/filesys/miniFilter/delete/  프로젝트를 받고 윈7에서 돌려보니까


bsod발생...


읭? 왜이러지 하던중 발견했습니다...

 



제 환경은 vs2015환경입니다


나중에도 잊지 말기!

'긁적긁적..' 카테고리의 다른 글

vmware host/guest 이동 할때 numlock 토글 문제  (0) 2016.02.18
office군 제어 관련 자료  (0) 2016.02.03
__debugbreak enable/disable  (0) 2015.12.16
get sid from sessionid  (0) 2015.11.18
Posted by GRoovAllstar
2016. 2. 18. 12:17

저는 리얼포스 키보드 사용중인데 키보드에 키패드가 따로 없고 문자키에 혼용되어 있습니다.


num lock 키를 누르면 문자키가 숫자키로 토글되는데요...


vmware로 이동하면 자꾸 num lock이 토글되서 짜증이 ㅎㅎㅎㅎㅎ


여기저기 찾아본 결과 해결은 했는데 정확하진 않아서 일단 올려봅니다.


1. vmware bios booting(guest os 부팅 시 F2)


num lock off 설정(해당 설정은 구글링하면 많이 나옵니다)


2. host / guest 키보드 관련 레지스트리 설정


키 : HKEY_CURRENT_USER\Control Panel\Keyboard

이름 : InitialKeyboardIndicators

값 : 0


저는 1번 방법으로만으로는 되지 않아서 2번방법까지 해봤더니 되더라고요..



'긁적긁적..' 카테고리의 다른 글

MS driver sample bsod  (0) 2016.02.26
office군 제어 관련 자료  (0) 2016.02.03
__debugbreak enable/disable  (0) 2015.12.16
get sid from sessionid  (0) 2015.11.18
Posted by GRoovAllstar
2016. 2. 3. 14:40

최근에 office군 관련 제어 작업 진행 중에 있습니다만... ㅠㅠ


어렵네요..


관련 링크


자동 저장 파일, 생성된 자동 저장 파일(.ASD) 파일의 복구 방법에 대한 자주 문의되는 질문에 대해 설명

https://support.microsoft.com/ko-kr/kb/601987



[Office] 손상된 오피스(Excel, Word, Powerpoint, Outlook) 파일 복구 관련 문서

http://blogs.technet.com/b/koroffice/archive/2009/09/22/office-excel-word-powerpoint-outlook.aspx


Word에서 임시 파일이 만들어지는 방식에 대한 설명

https://support.microsoft.com/ko-kr/kb/211632


동작 간 operation 분석은 다음 기회에 ㅎㅎ

'긁적긁적..' 카테고리의 다른 글

MS driver sample bsod  (0) 2016.02.26
vmware host/guest 이동 할때 numlock 토글 문제  (0) 2016.02.18
__debugbreak enable/disable  (0) 2015.12.16
get sid from sessionid  (0) 2015.11.18
Posted by GRoovAllstar
2015. 12. 16. 19:35

sx, sxd, sxe, sxi, sxn, sxr, sx- (Set Exceptions)

The sx* commands control the action that the debugger takes when an exception occurs in the application that is being debugged, or when certain events occur.


Remarks

The sx command displays the list of exceptions for the current process and the list of all nonexception events and displays the default behavior of the debugger for each exception and event.

The sxe, sxd, sxn, and sxi commands control the debugger settings for each exception and event.

The sxr command resets all of the exception and event filter states to the default settings. Commands are cleared, break and continue options are reset to their default settings, and so on.

The sx- command does not change the handling status or the break status of the specified exception or event. This command can be used if you wish to change the first-chance command or second-chance command associated with a specific event, but do not wish to change anything else.

If you include the -h option (or if the cc, hc, bpec, or ssec events are specified), the sxe, sxd, sxn, and sxi commands control the handling status of the exception or event. In all other cases, these commands control the break status of the exception or event.

When you are setting the break status, these commands have the following effects.


Command Status name Description

sxe

Break

(Enabled)

When this exception occurs, the target immediately breaks into the debugger before any other error handlers are activated. This kind of handling is called first chance handling.

sxd

Second chance break

(Disabled)

The debugger does not break for a first-chance exception of this type (although a message is displayed). If other error handlers do not address this exception, execution stops and the target breaks into the debugger. This kind of handling is called second chance handling.

sxn

Output

(Notify)

When this exception occurs, the target application does not break into the debugger at all. However, a message is displayed that notifies the user of this exception.

sxi

Ignore

When this exception occurs, the target application does not break into the debugger at all, and no message is displayed.

 

When you are setting the handling status, these commands have the following effects:


Command Status name Description

sxe

Handled

The event is considered handled when execution resumes.

sxd,sxn,sxi

Not Handled

The event is considered not handled when execution resumes.

 

You can use the -h option together with exceptions, not events. Using this option with ch, bpe, or sse sets the handling status for hc, bpec, or ssec, respectively. If you use the -h option with any other event, it has no effect.

Using the -c or -c2 options with hc, bpec, or ssec associates the specified commands with ch, bpe, or sse, respectively.

In the following example, the sxe command is used to set the break status of access violation events to break on the first chance, and to set the first-chance command that will be executed at that point to r eax. Then the sx- command is used to alter the first-chance command to r ebx, without changing the handling status. Finally, a portion of the sx output is shown, indicating the current settings for access violation events:


0:000> sxe -c "r eax" av 

0:000> sx- -c "r ebx" av 

0:000> sx 
 av - Access violation - break - not handled
       Command: "r ebx"
  . . .  


disable : sxi bpe

enable : sxi bpe


http://stackoverflow.com/questions/9099586/how-can-i-remove-breakpoint-ntdlldbgbreakpoint0x1-in-windbg



'긁적긁적..' 카테고리의 다른 글

MS driver sample bsod  (0) 2016.02.26
vmware host/guest 이동 할때 numlock 토글 문제  (0) 2016.02.18
office군 제어 관련 자료  (0) 2016.02.03
get sid from sessionid  (0) 2015.11.18
Posted by GRoovAllstar
2015. 11. 18. 11:34
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
bool get_sid_from_session_id(__out LPTSTR &string_sid, __in DWORD session_number)
{
    bool result = false;
    HANDLE current_user_handle = nullptr;
 
    do
    {
        if (FALSE == WTSQueryUserToken(session_number, current_user_handle))
        {            
            break;
        }
 
        DWORD dwSize = 0;
        BYTE * token_information = nullptr;
        if (FALSE == GetTokenInformation(current_user_handle, TokenUser, 
            static_cast<LPVOID>(token_information), 0, &dwSize))
        {
            if (GetLastError() == ERROR_INSUFFICIENT_BUFFER)
            {
                token_information = new(std::nothrow) BYTE[dwSize];
                if(nullptr == token_information)
                {
                    break;
                }
 
                ::memset(token_information, 0, dwSize);
            }
            else
            {                
                break;
            }
        }
 
        PTOKEN_USER token_user = reinterpret_cast<PTOKEN_USER>(token_information);
        if (FALSE == GetTokenInformation(current_user_handle, TokenUser, 
            static_cast<LPVOID>(token_user), dwSize, &dwSize))
        {            
            break;
        }
 
        if (FALSE == ConvertSidToStringSid(token_user->User.Sid, &string_sid))
        {            
            break;
        }
 
        if (nullptr != string_sid)
        {
            result = true;
        }
 
    } while (false);
 
    if (nullptr != current_user_handle)
        CloseHandle(current_user_handle);
    current_user_handle = nullptr;
 
    return result;
}
cs


__out 의 string_sid는 ::LocalFree를 해야함.

https://msdn.microsoft.com/ko-kr/library/windows/desktop/aa376399%28v=vs.85%29.aspx



'긁적긁적..' 카테고리의 다른 글

MS driver sample bsod  (0) 2016.02.26
vmware host/guest 이동 할때 numlock 토글 문제  (0) 2016.02.18
office군 제어 관련 자료  (0) 2016.02.03
__debugbreak enable/disable  (0) 2015.12.16
Posted by GRoovAllstar