I have a problem with Windows Phone emulator in VS13, I am developing a quiz game.
When I run my program, virtual machine turns on, everything goes fine, after that it builds my program and finally it works, but only for several seconds.
I can do whatever I want during these seconds, I've even managed to start the game, but after 7-8 seconds the emulated phone screen turns gray.
I've checked what happens with the virtual machine in Hyper-V manager, it seems to stop due to lack of memory, am I right with this conclusion?
And if I'm right, what can I do to solve this problem with memory apart from upgrading my PC? :)
I'm using Windows 8 installed as a virtual machine via VMWare Workstation.
Here are two screenshots of my gray screen - one is WF emulator and the second one is the same screen, but opened via Hyper-V manager (it says "not enough memory" in the bottom line).
Related
Host machine: Debian 10 running NoMachine 7.2.3
Settings:
Specified H264
User Hardware Encoding enabled
Use Specific Frame Rate enabled (60FPS)
Use Acceleration enabled
Client: Windows 10 running NoMachine 7.2.3
Both machines have monitors attached.
Using NX protocol for connection.
FullScreen / Scale to Window / Desktop is currently 2560x1440 (reduced from native while testing this issue)
Specific issue:
I do a ton of work in the terminal and when viewing desktop via nomachine, the terminal caret is randomly not visible. The same issue is less noticeable with right click menus and other areas of "visual updates in small screen space." If this were another remote desktop vendor I would try to find the "don't update just regions" setting to force the entire display to update regularly, but I can't find similar settings for nomachine. I have a dedicated gigabit connection between the two machines with no other traffic on that line, so bandwidth is not an issue.
To recreate:
I disabled caret blink (using universal access / accessibility settings) so the caret is a solid block in terminal / vi. If I edit a text file in vi and move up and down, the caret will only update visually every other line or so (verified on the physical screen it is moving correctly). Same if I highlight or insert, etc. You inevitably miss a character or so or lose your place).
I have tried changing speed vs quality slider, resolutions, swapping from h264 to VP8, etc.
I have disabled:
multi-pass display encoding
frame buffering on decoding
client side image post-processing
Nothing seems to change this specific issue. Yes I can make dragging a quarter-screen-sized terminal window smoother, but that doesn't help me follow the caret in vi/vim. Both machines are nicely spec'd (client has 16G / RTX2080, server has 32G / GTX1080)
Is there a way to get nomachine to update all the screen all the time, or at least better refresh small areas like a terminal caret?
(OP): Based on a night of troubleshooting, the issue seemed to be either:
An issue with the Debian install of the nvidia drivers
The server machine is a laptop with a broken main screen (but with an HDMI external monitor plugged in). The Debian X-server may have been confused as to whether it was headless or not and caused issues with nomachine (which tries to detect headless and start a virtual session).
The solution to this exact problem would be to disable the GUI and force a virtual session, per https://www.nomachine.com/AR03P00973 (dummy dongles won't work because the laptop's main display is not a standard plug).
In my specific case, I needed GUI access on the server at times so I couldn't use the above methods, and I could not remedy the problem with Debian, so I wiped the system and installed Ubuntu 20.04, which is more forgiving with graphics drivers and monitors. After setting up the Ubuntu system as similarly as possible to the Debian system and letting the proprietary nvidia drivers auto install, nomachine connected at the same resolution and worked perfectly, without the lag in small screen areas.
I'm in an unusual spot. The built in screen on the laptop I'm using right now is broken so bad I can barely see anything besides random flickering lights on it. Because of that, I got and plugged in a monitor to my laptop. This moniter works fine once Windows 7 has already loaded.
The issue is: I'm trying to open the BIOS/boot menu to live boot off of my USB, but I can't see anything. How do I make it so that I get visual output on my monitor early enough to open the BIOS/boot menu?
If it's a Dell laptop, try FN&F1 or F1
Dell Forum
I was hoping someone can point me in the right direction regarding an issue I am having with the message "Error creating window handle". I know this usually points to a memory leak problem with the code, however this only happens on a single machine. If the code was the issue, I would be expecting it to happen on other machines as well.
I have other machines that this application runs on that do not run into this problem. I have tried reproducing in on my development machine and other machines in the office. Neither has been successful. I have tried watching the memory in Task Manager on the offending machine and it does not skyrocket up before it throws the error.
The offending machine is running Windows XP Professional SP3. Any ideas on how to proceed would be great.
Thanks
I have just had the same problem in two different applications. For us, the problem was triggered by setting the Windows theme to "Windows Classic" rather than "Windows XP Style". The control that fails is a System.Windows.Forms.ListBox inside a Developer Express XtraLayout container, and our fix is to replace it with a DevExpress.XtraEditors.ListBoxControl.
I'm running DirectX application on the server (Windows Server 2003) and it does not have window (normally, running on PC, it has window). The issue is that I want to take screenshot of it from it (and save it to the png picture). When running on PC, this is working:
Surface backBuff = Device.GetBackBuffer(0, 0, BackBufferType.Mono);
SurfaceLoader.Save(fileName, ImageFileFormat.Png, backBuff);
But on server, the only thing I'm given is black picture (with right size).
Is it possible to take screenshot of directX app without window?
Thank you very much for answers
The solution is quite simple: running the app from script that is running under another user than IIS.
I understand this is an old technology, but I have been using it forever and own the software so I can't really change. I just installed Fireworks 6.0 on a Windows 7 box and even thought I can use the keyboard to get to my tools I can't actually CLICK any of my tools. It is the strangest thing I have ever seen. Could this be a Windows 7 issue because I've installed this product countless times on Windows XP machines and I can't ever remember this happening....HELP!
The issue with using Fireworks 6 ended up being even more bizarre than I originally thought. On my new laptop running Windows 7 I can not click to anything in my toolbox HOWEVER when I put Fireworks on my second monitor I can click everything in my toolbox. I found this out quite by accident.
I had an issue with old fireworks on windows 7 where it would not save preferences, one of the fixes was to enable compatibility mode and set it to run as administrator, you can do this by right clicking on the fireworks icon.
Hope that helps this problem too.