I've got what seems to be a small problem but am pretty stuck at the moment.
I have developed a tool a while ago, that is used to change settings of the Ewf on Win 7 embedded.
The main functionality of the tool was to run ewfmngr.exe (commandline) with different commands depending on what the user set in the programs GUI.
This works fine in Win 7, but for Win 10, nothing happens.
I do not get any errors, when debugging, all methods return values indicating, everything should have worked.
However the settings are not applied.
When I type the commands directly into the command line everything works as it should.
My application was always started with "run as administrator".
What did they change from Win10 to Win7, that causes this problems and what can I do against it?
Related
Using the ViewSizePreference.UseHalf works great for a Windows 8.1 app running in Windows 8.1. However, when I run the same app on Windows 10, I don't get the split screen effect. I guess that may be expected behavior as the UI is quite different, but wondering if there is any kind of workaround for this.
Thanks.
Split screen launching (that is, ViewSizePreference.UseHalf) is only supported in tablet mode.
This is a problem I only see in vim but I am hoping someone can provide advice on what to look for (with google code shutdown, I cannot submit bug reports for vim).
On x64 Windows 8.1 (it works fine on x64 Windows 7) vim/gvim works fine with the windows clipboard until you launch a web browser (chrome, firefox, opera, ie). When the browser is running, vim can place text on the clipboard but cannot get text from the clipboard. When the web browser is closed, the clipboard starts working again.
I have tracked the problem down to IsClipboardFormatAvailable(CF_UNICODETEXT) returning non-NULL but GetClipboardData(CF_UNICODETEXT) returning NULL under these conditions. It seems to be something specific to how vim is using the win32 api (probably different calls than these) because simple test apps that I write doing this work fine.
I have tried running with different compatibility settings and running as administrator but nothing makes a difference. This behavior is the same for both 32-bit and 64-bit builds created using Visual Studio 2013 Community and 2010 Professional.
What is the most puzzling is that the official 32-bit build (very old at this point) works fine but my own build off of the exact same tag (or every other build I have found on the internet) does not work.
For the curious there are instructions on how to get and build vim on windows here (note - I am not the blog author): http://solar-blogg.blogspot.com/p/vim-build.html
I'm running Python 2.7 with ArcGIS Desktop 10.1 on Windows for Server (2 Xeon 2.13 Ghz processors).
Is it possible to suppress or automatically close the dialogue box from Windows that says "python.exe has stopped working" when python crashes? I have a continuously running, multiprocessing script that sometimes crashes for unknown reasons (working on that). When I click to close the crash report window, the script restarts and everything is okay. I want this to happen automatically until I can track down what is causing the crashes.
Thanks very much!
Doug
Procedure for disabling the Windows Debugger dialogue box found here:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204634(v=vs.85).aspx
This prevents the debug dialogue box that requires the user to click [Debug] or [Cancel] if python crashes.
However, there is now another Windows dialogue box that says "python.exe has stopped working. Please close the program" with a button [Close Program]. Sheesh!
The dialog you refer to is part of Windows Error Reporting.
The exact method varies between editions of Windows (Windows 7 instructions here, Google will happily provide for other versions...), but if you disable this feature of Windows, your crashes will happen a lot faster(!).
This is an simply an arcpy bug. You can try to avoid using the steps that are causing the crash, but it generally happens under different tools when used to process through a long list of data.
The only workaround I have found is to make my script save its progress along the way to disk so if you restart the process, it knows where to pickup from.
If you then disable windows debugger message by altering the registry (see below), you can then just repeatedly execute the script in cmd.exe until it completes the entire batch without having to close the process manually every time in between.
I know this is an awful workaround, but it is quite uncommon to have a python library kill off the python interpreter.
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI = "1"
DWORD HKLM or HKCU\Software\Microsoft\Windows\Windows Error Reporting\Disabled = "1"
I am trying to programmatically open the windows 7 on screen keyboard (osk.exe) from my program.
I found a good guide for this on this page and it works quite well when UAC is turned off.
When UAC is turned on, it is not opening the program at all however, and I can't find why. No UAC prompt is shown when opening the keyboard from the start menu, so it doesn't appear to need administrative privileges.
Is it just because the executable is located in the windows system folder, and if so, is there another way to launch a program that would work?
The error returned is 3, ERROR_PATH_NOT_FOUND, possibly because 'sysnative' path is not working with UAC enabled.
Trying to run "osk.exe" without path also fails, with an error "Could not start the On Screen Keyboard"
Finally, running "C:\Windows\system32\osk.exe" fails with error code 5: SE_ERR_ACCESSDENIED when I tried to use it with redirection turned off (as suggested in this question)
I tested the c++ code sample you refer to in your message. The routine started either from VS devenv or as a standalone exe did always show the on-screen keyboard under any available UAC mode. My OS: Windows 7 Ult. SP1 64-bit.
In the current project, I'm making an icon overlay. The actual implementation is completed.
And I made sure that it worked well in WindowsXP and Windows7.
But I want to appear to overlay icon immediately without restarting the explorer process.
So I found a way that SHLoadNonloadedIconOverlayIdentifiers function signals the shell and then load the nonloaded Shell Extension dll.
I make sure in the MSDN that minimum supported clinet of this function is Windows 2000 Professional.
In Windows7, this function worked fine, but it did not work in WindowsXP.
I would like to know why.