Keep user from ctl+alt+del to kill app 2

[jadams0173]

I've read on this forum that disabling or circumventing the ctl+alt+del keys is anything from VERY dangerous to not possible. So how do you keep a user from killing an app this way? I have an app that the users are killing this way instead of entering the data.

I have looked into ways to make it not show up in the task list but have been unsuccessful at this. Any suggestions?

 

[tsdragon]

It seems to me that there is some other issues involved if your users would rather use the task manager to kill your app than do whatever they are supposed to do. Maybe instead of trying to prevent them from killing the app you should be trying to prevent them from wanting or needing to kill the app.

Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard.

 

[strongm]

>circumventing the ctl+alt+del keys is anything from VERY dangerous to not possible

It is not possible from VB (on NT-based systems)

The comments about it being dangerous are not VB issues ...

 

[jadams0173]

Here is why the user kills the app and I'm open for suggestions.

The user inputs a tool number that is required for a job and the app returns the location of the tool.

The user should scan a barcode on the tool into a modal form to signify they physically had the tool and the date and time it was removed from the tool room.

Instead of scanning the label they take the tool and run. The pc is located beside the only door in and out of the tool room and the scanner is wireless. I don't know how to make it easier for them.

Scanning the label captures needed data and verifies that the label scanned matches the data that was searched for. Plus management wanted it...

 

[EBGreen]

This is a management issue. Fire a couple of people for it and I bet the problem will go away.

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[trollacious]

Make them enter a user ID to get the info, and then record their ID, the time, and the tool ID when the location info is returned. That way it'll be easier to track who was asking for what when, whether they actually got the tool or not. This should help get the workers' attention, too.

Lee

 

[gmmastros]

I like EBGreen's suggestion, but it may not be practical. Here's another suggestion.

I assume the user is logging in to the app. If not, then you should change it so this happens. If a user does not log out after a pre-determined time, then automatically log them out.

When a user searches for a tool, write a small file to the hard drive to indicate which user searched for a tool, and what the tool is. After they barcode the tool, delete the file.

When the app starts up, check for the file. If it exists, you know a search was done, but not a barcode scan. At this point, you can send an email to a supervisor. They can check the inventory, if the tool is missing, then the supervisor can have a 'chat' with the employee.

Of course, the 'chat' would have to be company policy.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[cyoung]

This may be a good case for RFID tags on the tools....

 

[jadams0173]

I like EBGreens solution to and that has been my answer to management. Make a few examples...but I'm wasting my breath when I say that.

gmmastros,
I currently store every tool that is searched for and who searched, date, time...etc. That's how I know they aren't following the rules. There should be 2 entries for each inquiry. The first having all the label data empty and the second the data should be populated and the timestamp difference should be a very short interval.

cyoung,
I have brought up RFID to my boss. I told him if we were serious about capturing this data, then that would be the only "sure" way of getting it. Then he brought up cost and I think it died there when I did a little quick internet research and showed him the data.

Thanks for all the input!! I'm not going to try to manage the people with application any longer. I'll leave that up to someone else!

I'm still open for suggestions! Thanks to all who contributed!

 

[WZUP]

jadams0173,

I feel your pain, if employess are getting their own tools, without recording them I would modify the program that would require them to enter ther employee clock number or badge number, password before displaying the tools locations.

 

[EBGreen]

Pretty sure that ibnformation is being captured already:

"I currently store every tool that is searched for and who searched, date, time...etc. That's how I know they aren't following the rules."

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[WZUP]

Without management support/enforcement what else do they expect you to do?

 

[MattSTech]

Hire a tool crib attendant. Put a cage up. And lock the door. Other than that the only way to convince them they should use the system is allow them to run out of a few tools and when they complain... remind them that if they would use the software it wouldn't have happened.

Matt

 

[Sheco]

I think some kind of motion-controlled alarm would be cool.

You could make it out of an electric eye like the kind that are solds as safety features for garage door openers. It has a beam emitter on one side and a photoelectric cell on the other and it used to keep the door from smushing your children. Anyway, it has a little wire that runs back to the control unit... current on the wire signals the control unit to stop and/or reverse the motion of the door.

Anyway,you could make this a computer controlled alarm by pairing the electric eye with a loud siren and a pair of relay switches. What is a COM port really but a programmable switch? You could make a little OCX or ActiveX exe to monitor the COM port or, more likely, put some power onto one of the lines. This current would flip a relay switch and sort of "arm the alarm".... the alarm will only sound when both the COM port is activated AND the electric eye is activated.

[tt]
------| <- electric eye power
|
---------
| emit | -> -> -> ->|
--------- | reflect
| detect| <- <- <- <-|
---------
|
| <- electric eye signal
|
|
---------------
|low current |
|relay switch |
---------------
| |
_____| | <- switched signal
DC power |
RTS from |
COM port |
|
|
---------------
|high current |
|relay switch |
--------------- --------
| | | loud |
----| |---------| horn |
120v AC switched --------
wall power power
[/tt]

Or, with a slight modification, you could split it into two logical programs, one that raises an event when the electric eye is triggered and a second one that just controls the on/off state of the siren. This, coupled with a blatantly visible security camera should do the trick.

 

[BobRodes]

Star for a good laugh, Sheco. Reminds me of the "pumpkin alarm." One of my brothers, back in the day, created a fabulous "jack-o-lantern". Even had a carrot in his nose, and a blue wool cap. Under said pumpkin was a "reverse button" (off when pushed, on when not pushed). Wires led to a bank of 2 1000-watt spotlights, a flashing red light, and a loud siren. Concealed near said pumpkin were half the kids in the neighborhood and a large quantity of eggs. No doubt the rest of the story can be left to the imagination.

Fortunately, this was in the days before the drive by shooting was popular....

Bob

 

[macleod1021]

Could we also add a voltage pad that will give the person an electric shock if they don't use the scanner? And progressively make it stronger for each time they skip the process. I'd have a fun time watching that on a webcam

 

[Ovatvvon]

jadams0173,

I know how you can keep your VB app from displaying in the Ctrl-Alt-Del list; but it will only keep it off the "Applications" tab...it will still be displayed in the "Processes" tab.

If you're still interested, let me know, and when I get home tonight I'll relook up how I did it in an old application I wrote once, and post it.


-Ovatvvon :-Q

 

[EBGreen]

Then make sure the process name is suitably ambiguous and you'll have the beginnings of a nifty little virus.

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[Ovatvvon]

EBGreen,

If he is asking how to keep it out of the task list, then I doubt he is capable of writing anything harmfull enough to not be caught by anti-virus software. I'm sure he also realizes that programs also tack on computer identifying information so that if the Government gets ahold of the program (or any truly savvy programmer), they can often times identify who created it (or at least which computer created it, including IP, date/time, etc.)

Just my thoughts. Do you think otherwise?

-Ovatvvon :-Q

 

[EBGreen]

It was an obviously abysmal attempt at humor.

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]