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
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.
Using Blender 2.82a I encountered this screen glitch:
But I had a similar issue with Photoshop 2020 where the GUI had similar glitches. And lastly, Minecraft with the SevTech Ages modpack. This doesn't happen with other software (Firefox, Excel, VSC, Sublime Text, WSL). This makes me think it's should be a graphic drivers issue. I uninstalled the NVIDIA drivers and left Windows reinstall them. I didn't encounter the issue again yet. Can anyone confirm this is a bad drivers issue? I couldn't find much information online (or didn't know what to search for).
I cannot assuredly say that this is a driver problem, but the same happened with me with my old PC. My old PC was very low-end. It was very slow in Blender, but got the work done. To make my PC faster, I saw a youtube tutorial which showed that going to System > advanced system options > graphics and switching off all 'fancy' features will make your PC faster. Doing this resulted in the same glitches in blender and inkscape, but got fixed by switching those options bak to what they were before.
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).
I am running into hardware issues that perhaps someone here knows a workaround. I am using a PC and windows.
For several years I have been making interactive installations using video tracking: the Jmyron library in Processing, which has functioned marvelously for me. I use this set up: cctv type microcameras to a multiplexer, the I digitize this signal via a firewire cable to a pci card. Then Processing reads these quads (sometimes more) as a single window, and it has always worked (from windows xp all the way to 7). Then comes windows 8: Processing seems to prefer the built-in webcam to the firewire bus. On previous version of windows, the firewire bus would naturally override the webcam, provided I had first opened a video capture in Windows Maker, and then shut it down before running the Processing sketch. In Windows 7, which had no native video capture software, I used this great open source video editor called Capture Flux. The webcam never interfered. With Windows 8, no matter what I try, Processing defaults to the webcam, which for my purposes is useless. I have an exhibition coming up real soon, and there is no way I am going to have the time to rewrite all that code for Open CV or other newer libraries.
I am curious if anyone has had similar problems, found a work around? Is there a way of disabling the webcam in Windows 8 (temporarily of course, because I need it to be operational for other applications), or some other solution?
Thank you!
Try this:
type "windows icon+x" choose device manager (or use run/command line: "mmc devmgmt.msc")
look for imaganing devices, find your integrated webcamera
right click on it and choose disable - now processing should skip the device.
Repeat the steps to reenable the device.
Other solution would be using commands in processing:
println (Capture.list()); (google it on processing.org) this way you will get all avaliable devices and you can choose the particular one based on its name.
Hope this helps.
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.