New User, Welcome!     Login

Dr Watson

Re: SEPKILL /im SMC.EXE /f

>>>>>> way.
>>>>>> >>>
>>>>>> >>> drwtsn32 -p %pid%
>>>>>> >>> where pid is the process id for smc.exe
>>>>>
>>>>> There's nothing remarkable about this at all. If you tell Dr Watson to
>>>>> debug any process id, it's going to end the process. Or at least it 
>>>>> did
>>>>> to half a dozen applications I tested it on :)
>>>>>
>>>>> Then again, you need administrator privs for this, so really, the same

Re: SEPKILL /im SMC.EXE /f

>>>>> way.
>>>>> >>>
>>>>> >>> drwtsn32 -p %pid%
>>>>> >>> where pid is the process id for smc.exe
>>>>
>>>> There's nothing remarkable about this at all. If you tell Dr Watson to
>>>> debug any process id, it's going to end the process. Or at least it did
>>>> to half a dozen applications I tested it on :)
>>>>
>>>> Then again, you need administrator privs for this, so really, the same
>>>> argument here applies as above. If you have this level of access, why

Re: SEPKILL /im SMC.EXE /f

>>>> way.
>>>> >>>
>>>> >>> drwtsn32 -p %pid%
>>>> >>> where pid is the process id for smc.exe
>>>
>>> There's nothing remarkable about this at all. If you tell Dr Watson to
>>> debug any process id, it's going to end the process. Or at least it did
>>> to half a dozen applications I tested it on :)
>>>
>>> Then again, you need administrator privs for this, so really, the same
>>> argument here applies as above. If you have this level of access, why



Copyright © 1995-2012 LinuxRocket.net. All rights reserved.

Nearly all of LinuxRocket's features are free. Be kind and donate to the cause!