I am using VMWare Player 6.0.3 build-1895310 on Windows 7 (host) running CentOS 5.9 as Guest OS. I have always had this sporadic problem, wherein when I start my Guest OS the login screen of CentOS seems to be using fullscreen, but when I login (90% of the time), the desktop is never in full screen and there is nothing I can do to change the resolution.
I also have the latest VMWare tools installed.
[root#localhost ~]# vmware-toolbox-cmd -v
9.6.2.31837 (build-1688356)
[root#localhost ~]#
I have tried the following things:
Restarting VMWare Player multiple times, then suspending the VM and restarting the VM
Reinstalling the VMWare Tools
Its only with some combinations of the above two steps, that I can see rarely my desktop screen in fullscreen. But 100% of time, the login screen is always in fullscreen.
When i logout, I again see the full screen login screen
This is how the login screen looks always (fullscreen):
This is how the desktop screen looks 90% of the time (NOT fullscreen): Please help!!!
I had the same issue today.
It seems that an xorg.conf magically appeared, only with a display entry in it.
In my case I had to remove the xorg.conf and restart the vm.
Kind regards
Urs
Related
I just downloaded the MacOS Big Sur Beta 3. The problem is when I'm trying to open XAMPP, you can see the application jumping on the dock but it stops right away without doing any action. Is it possible to access my files without running the XAMPP VM?
Same thing happens to me… Until it gets fixed, you can use the console interface:
sudo /Applications/XAMPP/xamppfiles/ctlscript.sh start
I have a Raspberry Pi 4B running under NOOBS. I have installed XRDP to be able to access the Raspberry from Windows.
The remote connection is working fine but whenever I launch an application (ex: Chromium) from Windows, I don't see anything happening. If I check directly on the screen connected on the Raspberry, I see that the application is running there.
It looks like whatever I launch on the remote desktop screen, the output goes to the native screen and I can't see it in the remote desktop window. I'm connected with exactly the same user on both sides.
Do you have any idea how to solve this?
Raspberry is known for not beeing compatible with any VNC Software.
You should try RealVNC first which comes with NOOBS. Make sure you have the latest version.
sudo apt-get update
sudo apt-get install realvnc-vnc-server realvnc-vnc-viewer
At your desktop select Menu > Preferences > Raspberry Pi Configuration > Interfaces.
Ensure that VNC is Enabled.
Now get your RealVNC Application for Windows and youre ready to go.
Another alternative is TightVNC, which works in most cases fine, too.
I have just installed VMWare Workstation 12, but since the VMWare Tools has been upgraded in the guest Windows XP, I can see only a black screen (the host is a Windows 7 on a Dell Inspiron 15 notebook). The booting process is visible, but the login screen is already black.
I can hear the login sound, I can start apps (in Unity mode), but every window is completely black.
After uninstalling the VMWare display adapter in Safe Mode, it works again in simple VGA mode. I have removed and reinstalled VMWare Tools and the screen is black again.
Any ideas?
It finally has been solved by turning 3D acceleration off at Display settings.
I am following the instructions given HERE
I can install it to the vmware hard disk fine and get it running, but then it says to open a terminal and execute su
The terminal says that it cannot make me a root and nothing else
I am not able to go any further after this and so the internet isn't working in the virtual machine
Moreover, the internet works if I was just using the live CD version, without me having to do anything else
How do I get root permissions in android x86 on VMware?
--- EDIT---
After playing around some more with this I have noticed another problem: when I try to start the virtual machine, most of the times it reaches the Chrome coloured android startup logo, the logo animates continuously but the screen is sort of stuck at that phase. And if I loose focus to the vmware window and come back, I see that the window is blank and I am not sure if the virtual machine is even further loading or not. How do I properly get Android x86 to work on vmware (with full install on it's virtual hard disk and not just the live CD version? Should I try other virtual machines? I have not been able to get others such as qemu and bochs to work in the past and see that vmware is the easiest and most stable option, so I would like to run this in vmware if possible.
check here www.bitdirect.nl/?p=128
I followed this with a few little tweaks here and there and it worked perfectly.
only downside is transferring data outside of the android os is a pain.
I am new to both the android and android development so I'm not on familiar ground here.
When I start the emulator I have no service. Therefore I have no internet connection on the emulator.
I am running Windows 7 and I generally run the emulator via eclipse.
My host machine is connected to the internet via the Local Area Network. There is no proxy.
I have tried:
Disabling all network adapters except for the Local Area Network [link]
Running the emulator from cmd line with: emulator -avd -dns-server 8.8.8.8
Reinstalling the SDK Tools 9 and Platform Tools (rev 2).
Restarting the machine! :P
Is there a setup needed to specify to simulate a 3G connection? Or could this be a Windows 7 permissions issue? Or am I doomed like these folks: link link
Ah! found the solution.. I uninstalled the entire SDK and reinstalled it to C:/Android. I deleted the C:/Users/[your-name]/.android folder and recreated an avd. Voila.. Something in there worked!
[edit]
Actually it looks like you have to keep restarting the emulator until it connects. I will often get no service so I restart a bunch of times till it works.
I found that 'Airplane Mode' was enabled by default in the standalone android emulator - this may also be the cause in the sdk version. Turning this off (by holding down the red power button until the menu came up, and then toggling the airplane mode button/section) allowed the emulator to 'find service' and connect properly through the LAN.