| "The Big Brother" Delphi code toolkit - PART 2 | ||||||||||||||||||||||
| Page 1: Quick intro to dWinLock | ||||||||||||||||||||||
It's been more than a year I've written an article describing how to use Delphi in order to create a "Big Brother Windows Application - going undercover: hiding from the task list, disabling task-switch, removing from the TaskBar, disabling shut down"... all using Delphi and API calls.
Many Delphi developers were happy to find all the "required" code samples in one place... For several weeks I've been searching the Internet for the simplest and yet the best solution to enable a Delphi developer to take FULL control over the Windows system - never mind whether it's Win95 or Win XP. dWinlock overview ![]() All options can be activated or deactivated during runtime. Therefore it is not necessary to reboot your system after making changes. Using dWinlock from code
After a call to the previous two lines, the user will be unable to, let's say, start the Windows Explorer by pressing Windows Key + E; of course he wont even be able to switch between started application using ALT-TAB. This really worksBut how? The component comes with an DLL called dGina.dll. Hm, does that mean that when deploying an application that uses dWinLick you need to deploy the dll too? Well, yes! Hm again, Delphi is known as the RAD tool that enables you to deploy (in most situations) only the application exe file to your customers. Later in this article I'll show you how to store dGina.dll inside your Delphi exe and extract it if needed! Yes, after that you again need to send only one file to your customers.Next page > About dWinLock and dGina.dll > Page 1, 2, 3 |
||||||||||||||||||||||


