Users getting in the way

HPROS · Post by **HPROS** » Tue Sep 30, 2003 12:30 pm

Is there any way to restrict input while my macro is running? The issue is that when I launch an application on a scheduled basis it may begin while a user is at the workstation and this causes issues. I often begin by minimizing all windows which helps, but can I restrict them altogether? If not, any ideas?

This would solve a lot of issues!

Thanks

Bob Hansen · Post by **Bob Hansen** » Wed Oct 01, 2003 4:07 am

This is an untested, off the top of my head idea:

At the beginning of the macro, go to the Device Manger, properties of keyboard and mouse and disable them from the profile. Display a Message Box explaining that system is busy. They should not be able to make message go away or do anything else. Message should include warning not to shut off machine, dead mouse/keyboard are "normal" at this time. At the end of the macro, Close message box, go back to Device Manager and enable them again.

HPROS · Post by **HPROS** » Wed Oct 01, 2003 10:27 am

Thank you Bob. I will try and test it when I get back in the office. I am out on business travel for two days... I will let you know.

HPROS · Post by **HPROS** » Sat Oct 04, 2003 2:31 pm

I tried to disable the keyboard and mouse, however it doesn't seen to be an option. The only choices seem to be with the interupts and drivers.

How are other folks addressing this issue? For example many macros play out on a workstation and can easily be thrown off with accidental operator activity.

I was wondering about registry entries, or the use of a second device profile, however I don't want to have to reboot each time for values to take.

Any thoughts?

Bob Hansen · Post by **Bob Hansen** » Sat Oct 04, 2003 5:41 pm

I do have those options in WIN98SE.

But I just tried them, and they did not work.

They were disabled, but I was still able to use the keyboard and mouse.....so much for that idea...... (I told you it was untested).

Lumumba · Post by **Lumumba** » Sun Oct 05, 2003 12:14 am

Run Program>RunDll32.exe Mouse,Disable
Run Program>RunDll32.exe Keyboard,Disable

Run Program>Command.com /c c:\windows\system32\rundll32.EXE shell32,SHExitWindowsEx

Seems to work with W98

Bob Hansen · Post by **Bob Hansen** » Sun Oct 05, 2003 4:35 am

Would these then be followed with an "Enable" version of the command when done?
============================

Thanks Lumumba...........

How about pointing to a good source for the RunDll32 functions?

Or perhaps I am looking for a list of DLLs and their explanations? I see no mouse/keyboard dll file, so I guess that "objects" are called by RunDll32? OK, so where do I get the list of objects and their methods?

It should be obvious that I don't even know the correct questions to be asking, but I am sure you understand my basic question - What can RunDll32 do for me, and how do I make it happen?

Looks like I will have to get familiar with this command. I guess it's off to MSDN.......

Lumumba · Post by **Lumumba** » Sun Oct 05, 2003 1:00 pm

I've found this: RunDll Commands

Haven't checked the sample (I don't use W98). The above mentioned should "refresh/reload" the registry without a restart. So (many) changes made to the registry could be used ad hoc.

Therefore disable mouse/keyboard should/could be used separately (I guess

).

Param -1 refreshs Destop&Explorer.

BTW: to enable both (mouse/keyb) a restart seems to be mandatory.

Bob Hansen · Post by **Bob Hansen** » Sun Oct 05, 2003 4:33 pm

Thanks for the link, Lumumba.

From MSDN I have determined that looking at the shell32.dll may also be a clue for more tools.