dechamps / laplock

Auto-lock your Windows computer when the lid is closed or the screen turns off.

laplock

Author: Etienne Dechamps (a.k.a e-t172) [email protected]

https://github.com/dechamps/laplock

This extremely small (102 lines, 21KB binary) C++ program allows you to automatically lock your Windows computer on two events:

• The computer is a laptop and its lid is closed;
• The computer screen is turned off. Note that this probably won't work with the power button of your monitor since the system is not notified when this happens; however, it works when the screen is turned off automatically after the delay specified in the Windows power management options.

laplock runs on Windows Vista, 7, and probably later versions; it won't work on Windows XP, since it doesn't implement the necessary power management interface.

Compilation

There is only one C++ file and it should compile using any Windows compiler. Project files are provided for Microsoft Visual C++ 2010. Note that you'll need the Windows SDK version 7.0 or greater.

Usage

Just run it. At first, nothing will happen; this is normal as laplock runs silently in the background (you can check this using the Windows task manager). laplock will keep running until you log off or kill it. It is recommended to add laplock to your Startup folder; then you can happily forget about it.

Note that laplock listens intelligently for events; meaning, it doesn't consume any CPU at all while waiting.

laplock's Issues

Locking After signing in

Hi,

If I start my laptop while it's on a docking station when I login laplock will start then lock the device, is there a way to prevent that ? If I login when the laptop is on the docking station it should not lock only once I open and close it again.

also thank you for all your work on this, it is very much appreciated!!!

Nothing happens when I ran installer

I downloaded https://github.com/dechamps/laplock/releases/download/laplock-0.2/laplock.exe, but found that the program seems to be immediately exiting without ever showing any windows.

New release?

Could you generate a new release (.exe file)? I noticed a number of commits since the initial release and it would be nice to have a new binary to go with the new source code for those of us who don't have access to a development system.

Unable to disable it

I wanted to disable it, so I disabled it via Task Manager, and it's still locks. Can someone help me about that!? (I'm on Windows 10)

How to add cli for this program

I need to add CLI for this. When the user close that cmd window application should be terminated

Code snippet for preventing multiple instances running

This simple app is very useful.

Here's the code I added to my project to prevent multiple instances from running.

I tested it briefly and it seems to work...it should be cleaned up to your standards. My Win10 machine appears to remove the mutex if the executable is ended using Task Manager so it should do so if the executable somehow crashes.

The code is basically the bottom of 'WinMain'.

========================= code added below here ===================================

wchar_t* convertCharArrayToLPCWSTR(const char* charArray)
{
wchar_t* wString = new wchar_t[4096];
MultiByteToWideChar(CP_ACP, 0, charArray, -1, wString, 4096);
return wString;
}

}
}

int CALLBACK WinMain(HINSTANCE instance, HINSTANCE prevInstance, LPSTR commandLine, int cmdShow)
{
CHAR szUniqueNamedMutex[] = "laplockUniqueNamedMutexZZTopRox";
LPCWSTR lpcwstr_app = laplock::convertCharArrayToLPCWSTR(szUniqueNamedMutex);
HANDLE hHandle = CreateMutex(NULL, TRUE, lpcwstr_app);
if (ERROR_ALREADY_EXISTS == GetLastError())
{
// Program already running somewhere
return(1); // Exit program
}

return laplock::WinMain(instance, prevInstance, commandLine, cmdShow);

// Upon app closing:
ReleaseMutex(hHandle); // Explicitly release mutex
CloseHandle(hHandle); // close handle before terminating
return(1);

}

Log Errors to Windows Eventlog

Hi and many thanks for this nice piece of software.

I have found, that errors will be locked to file, but only when a logfile is definied.

It would be better to log errors always in the windows eventlog and additionally to the logfile.

Thanks

Still there after Removing

After removing the exe from Autostart, its still doing the same thing as your tool did, but its not even running anymore in Taskmanager, im kinda spooked, whats happening ?