James_stillman
asked on
WIN NT Disable CTRL+ALT+DEL
How can I disable CTRL+ALT+DEL in win NT I already have some codefor the system ParametersInfo API call that is supposed to disable C-A-L but it does n't I can only assume that this API does not work in WIN NT(Security issue?) or needs some different parameters passed to it.
Any Ideas
James
Any Ideas
James
wow...that's strange....I posted ths above comment 4 mins before you posted the question....a little bit of logic tells me this is not right...but anyway....:)
He needs to disable it because of a screen saver.
ok....sorry....he didn't mention that....but I'm guess ing SPI API will not work with WinNT the same way as Win9.x
"4 mins before you posted"
Known EE bug...
Anyway. You're right. You cannot lock/disable/anything the whole box on an NT machine. It is a security issue.
Known EE bug...
Anyway. You're right. You cannot lock/disable/anything the whole box on an NT machine. It is a security issue.
ASKER
What so there is no way to get around this? How do people write screen Savers with internal security or do they just NOT.
:^[|]
James
:^[|]
James
It depends entirely on what you're trying to do.
A screen saver in NT does not lock the system, it merely creates a new desktop and switches to that. Any applications that are already running will remain so.
But if the only purpose of your question is to stop the user from interfering with the NT machine, you can achieve this quite easily. Write your own screen-saver and activate it password-protected.
A screen saver in NT does not lock the system, it merely creates a new desktop and switches to that. Any applications that are already running will remain so.
But if the only purpose of your question is to stop the user from interfering with the NT machine, you can achieve this quite easily. Write your own screen-saver and activate it password-protected.
ASKER
Caraf_g: I know this >>>>>A screen saver in NT does not lock the system, it merely creates a new desktop and switches to that. Any applications that are already running will remain so.
But what I need to do is to have some sort of internal security so that when my SS starts a user cannot exit it unless they enter a password into my system and then they can have the option of having the additional windows password.
What I need is a way to do this if there is any.
Cheers
James
But what I need to do is to have some sort of internal security so that when my SS starts a user cannot exit it unless they enter a password into my system and then they can have the option of having the additional windows password.
What I need is a way to do this if there is any.
Cheers
James
You cannot do this with NT. Since it will violate its security. It's only possible on win9x platforms.
ASKER
AAAAAAAAAAAAAAAAAAAAAAAAAA
:^(
Cheers Anyway.
:^(
Cheers Anyway.
Never say never, there is always a way. It may cost some time or money but it can get done. Check out this web site:
http://www.visualautomation.com/comprod/secure4.htm
This will do what you want.
Frank
http://www.visualautomation.com/comprod/secure4.htm
This will do what you want.
Frank
frankd,
If your user has NT administrator rights on the PC in question and they know what they're doing your $195 piece of software will be powerless to prevent them from doing whatever they want.
If your user has NT administrator rights on the PC in question and they know what they're doing your $195 piece of software will be powerless to prevent them from doing whatever they want.
You might want to try installing a shell hook by passing a WH_HOOK to SetWindowsHookEx (check MSDN). VB has an AddressOf Function which I've heard can be used to supply API calls with the function pointers they are looking for. So you may be able to write a Shell hook and respond to HSHELL_TASKMAN messages with TRUE (or return a long 1 in VB). This should disable the windows task manager. (see MSDN under ShellProc)
If the addressOf function doesn't work, you could always write a DLL in C.
If the addressOf function doesn't work, you could always write a DLL in C.
You might want to try installing a shell hook by passing a WH_HOOK to SetWindowsHookEx (check MSDN). VB has an AddressOf Function which I've heard can be used to supply API calls with the function pointers they are looking for. So you may be able to write a Shell hook and respond to HSHELL_TASKMAN messages with TRUE (or return a long 1 in VB). This should disable the windows task manager. (see MSDN under ShellProc)
If the addressOf function doesn't work, you could always write a DLL in C.
If the addressOf function doesn't work, you could always write a DLL in C.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
may I ask why you need to disable the box?? WinNT is already secure in its own coding....I don't see the reason to disable the box....if you disable it...how are you going to log on and log off???