Disabling Control+Alt+Delete 1

[Stewart531]

I'm having trouble disabling Control+Alt+Delete. I have seen some sample code on the web that all looks similar to this:

Private Const SPI_SCREENSAVERRUNNING = 97&

Private Declare Function SystemParametersInfo Lib "User32" Alias "SystemParametersInfoA" (ByVal uAction As Long, ByVal uParam As Long, lpvParam As Any, ByVal fuWinIni As Long) As Long


Dim lReturnCode As Long
Dim bOld As Boolean


lReturnCode = SystemParametersInfo(SPI_SCREENSAVERRUNNING, True, bOld, 0&)



For some reason, this code doesn't work for me. Anyone know why or have any suggestions? Thanks.
-Dave

 

[ADoozer]

see your other thread thread222-541812

If somethings hard to do, its not worth doing - Homer Simpson
------------------------------------------------------------------------
A General Guide To Excel in VB FAQ222-3383
File Formats Galore @

http://www.wotsit.org

 

[vanvb]

I looked at this for a little while too and I thought I had an answer, but ADoozer is right. Windows uses the fact that it is the ONLY program that can trap ctl-alt-del as a safety. If your network is set up this way, you will notice that using CAD brings up the screen to enter your password to log on. If you could trap this keyboard entry in your program, you could steal passwords by making a screen identical to the windows password screen, and get the user's password. That's why sercurity-aware versions of windows(2k,xp), will not let you trap CAD. Look at using a goup policy or something that windows controls if this is a company computer that you need to "lock-down".

 

[chiph]

Actually, there *is* a way to do it on a WinNT/2k/XP computer. It involves using C/C++ and the kernel debugger to write a replacement GINA DLL. This is not for the faint of heart, because if you get it wrong, you can't boot your OS, and you have to restore from a drive image.

My suggestion is, unless you're willing to spend several thousand dollars learning kernel-level development, buying a second PC to act as a kernel debugging terminal, a couple of expensive debugging tools, and about 6-9 months of your time, it's not worth it. There's probably only about 75 people in North America who have sucessfully done this, and half of them work for Microsoft.

Chip H.

 

[ADoozer]

hehe... what strongm said in the pointer to the pointer to the pointer to the other thread.

If somethings hard to do, its not worth doing - Homer Simpson
------------------------------------------------------------------------
A General Guide To Excel in VB FAQ222-3383
File Formats Galore @

http://www.wotsit.org

 

[Stewart531]

Thanks for the help!