I just closed a Cygwin window by means of an involuntary rogue mouse-click. A python script was running and it was about to complete its execution. So sad...
How do I enable any type of confirmation alert box option before closing an opened Cygwin window?
Do I need to configure something? I could not find any such options yet.
Mintty, the default Cygwin terminal, has an option to ask confirmation before closing.
Related
When apps crash, Windows used to popup a dialog box saying {Program} has stopped working with a Close button. I no longer see this dialog box on Windows 10. How do I get it back?
I thought perhaps I messed up some registry setting, so I downloaded a Windows 10 VM from Microsoft, crashed a program in the VM and I still didn't get a dialog box. So there must have been some change to Windows.
I tried tweaking the AeDebug registry key, but still couldn't get the dialog box back.
The reason I like the dialog box is because it tells me right away that some program has a problem that I can investigate further.
As described here, you need to set the Windows Error Reporting setting DontShowUI=0 with the Registry Editor or Group Policy Editor.
sounds a little dumb when i tell that but, when app stops working for me i usually press the left mouse button a lot in the windows (of the app) until it will display the message to end the process
I'm using a program called desklock which closes explorer/desktop and blocks hotkeys so that a user can only start programs by buttons on a small window. This will be going in as a touch-screen only HMI system, so I need to be able to launch the on-screen-keyboard. I have a button on the window for this, but whenever I try it, I'm always given the error, simply "could not start on screen keyboard" I've tried launching osk.exe directly, launching a shortcut to it, and launching a script to start it. All three methods work standalone, but when launched by this button, nothing works
If you O.S is a 64bit and you are trying to launch osk.exe from a 32bit application you might experience this problem.
This sould be caused by the File System Redirector which redirects calls to C:\Windows\System32 to C:\Windows\SysWow64.
I have the same problem with the osk.exe in C:\Windows\SysWow64 on Win10.
Attempting to open logman.exe on a Windows 2008 server is somehow harder than it looks.
It launches, and then immediately quits without any warning or pop-up. I attempted to "Run as Administrator" but it does the same without any prompt. Is there any way to figure out why it is doing this? Perhaps it is something in my permissions/policy -- how would I go about fixing it or finding out what it is? I've attempted to launch it on multiple machines but the issue still persists.
I am an idiot. You have to open the command prompt, and then run 'logman.exe'. Leaving this up in case anyone else gets brain farts.
I just installed evans debugger and when i click the program it never opens. im running suse linux 11.1.The program installs fine and shows up in my menu but never opens
Try to debug it the naïve way:
Open up Terminal.
Find the name of the executable that links to your debugger (editing the menu entry might show you the command that is run when you click on the menu item).
Run this command via Terminal.
Post the output so that we can actually see what's making the program not work.
I updated a working Cygwin/Screen setup on Windows 2k3 Server to Cygwin v1.7.2 and Screen 4.00.03. After updating, backspace no longer works. I haven't made any changes to my system or configuration. The Cygwin update went fine, and I don't have any custom changes in /etc.
Any ideas?
This has been confirmed as a bug and is scheduled to be fixed. See this thread on the Cygwin mailing list for details.
Try this at command prompt:
C:\cygwin\bin\bash --noediting