I am building an FLTK application in Windows XP under cygwin.
When I pass "-mwindows" to the linker, it behaves as advertized, and I don't get the command window popping up. However, when i run the same application under windows 7, a black console window pops up as if I hadn't passed -mwindows! does anyone know how i can debug this problem?
Thanks,
Woody
ak2 was right, i needed to update Cygwin.
Related
Hello Computer enthusiasts,
i try to run my electron app on windows pe.
When i try to start the app trough the "startnet.cmd" nothing happens.
If i want to start it over "procex64.exe" (Windows Process Explorer, from Sysinternals) i get the error that some ddl's are missing
msdmo.dll
dxgi.dll
d3d9.dll (DirectX ?)
dxva2.dll
Anyone know what this is, how i can fix that problem ?
Thanks for any advice.
Found a solution:
copy they files from a full windows installation to your windows pe image,
c:\windows\system32:
BCP47Langs.dll
d3d9.dll
d3d11.dll
dxgi.dll
dxva2.dll
msdmo.dll
(Tested/Found on Windows 10 Pro)
Is just a simple electron app with a single page and a few buttons. Perhaps there are other *.dll's if you work with media files or similar.
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?
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.
I'm sorry if this is the wrong place but I really don't know where to go for something like this.
I did a fresh install of Windows 8.1 on my new SSD and the context menus for the task bar looks like this now...
I realize this may not be the right place to post, but could you point me in the right direction? Thanks!
The solution was to uninstall Windows Update KB3072318.
https://www.reddit.com/r/techsupport/comments/3f4yz9/my_jump_list_icons_are_huge_and_weird/
You get this graphical glitch because you use a custom Windows 8 theme under Windows 8.1. Microsoft changed the format a bit. StartIsBack+ (for Windows 8.1) fixes this issue and restore the Win7 Start menu for a better Windows 8.1 UX.
Ok, forget my previous answer! It's got nothing to do with the SSD.
I just found a fix/workaround:
Just make a clean install with the internet completely disconnected and only connect after the setup is fully finished.
Also, this way, you won't even see the windows 10 upgrade notification on the setup.
Hope this helps...
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.