I downloaded device "Google Nexus S - 4.1.1-API 16-400x800" in my Genymotion player. When I try to start the device, player start to loading android and after about half minute pop up window with the message "player.exe stopped working".
I managed to start the device from virtual box without any problems.
Why I cannot start the device from Genymotion player?
have you checked "virtual device path" in genymotion go to vbox folder ?
if not try make vdp to C:\Users{comp. name}\AppData\Local/Genymobile/Genymotion/deployed/
Related
When I connect a device to the computer using USB virtual COM port and open the port in my application (in Qt, QSerialPort), it receives nothing.
When I open the port in PuTTy, it works as expected.
Surprisingly, after closing PuTTy and opening the port in my application again, it started to work as expected.
This problem only occurs with some devices, namely Raspberry Pi Pico, but not with other devices like STM32 USB VCP and USB-UART transceivers.
The likely cause is that the USB device needs to have the DTR signal (which is part of RS232) set to high in order to start transmitting. (many devices disregard the value of DTR, some do not)
Use serial->setDataTerminalReady(true); on QSerialPort after opening it.
PuTTy seems to set it to high after opening, but not set it low on closing. That's why it makes it work in your app after opening it once.
I created a VR experience in Unreal Engine, and inside the VR world, there is a button which can open an external exe, which is also a VR experence. It's like a VR menu room (Unreal application) and a mini VR game (not created by Unreal and is an external exe). When you play the mini game, Unreal VR menu is still open at the back.
I tried different ways to open external exe, such as:
FPlatformProcess::CreateProc
FMonitoredProcess
FInteractiveProcess
They can all successfully launch external exe, but the problem is, when the external exe is done playing and closed, the Unreal VR menu application will lose vision tracking of Oculus. This problem only happens if the external exe is a VR application. I tried to launch a regular exe, such as browser, and there is no lose tracking problem when I "alt tab" to jump back to Unreal VR application.
This is what I got from output log:
LogHMD: Vision Tracking Acquired
LogHMD: Lost Vision Tracking
Is this a bug of Unreal? Is there any way which can let Oculus retracked by Unreal after running an external VR exe?
Many thanks!
Oculus drivers should only handle one process at a time, so whenever that new application is starting, Unreal should give up its connection to the service because someone else is requesting the HMD to render those VR frames now. As a dedicated output, both applications issuing frames at the same time can't be a good thing.
Regarding your context, I suggest you try invoking the "Stereo On" Console Command to re-enable your HMD, though you might want to also try the Oculus specific "HMD Enable" command before hand.
Personal concern: Keeping that menu in the background must be consuming resources as well and, in VR, that's an optimization issue you might have to address eventually.
I try to start MINIX in VmWare, however, there it is stucked in "Started VFS:8 worker thread(s)"
I don't know why? does anyone have the problem?
Normal boot process continues with mounting /dev/c0d0p0s0..2
Q: Can't start?
A: Can. Follow the MINIX step-by-step scenario for VmWare hypervisors
http://wiki.minix3.org/UsersGuide/RunningOnVmware recommends for
Running on VMware
This page describes the process of installing MINIX 3 on VMWare.
1. Preliminaries
Please install VMWare. VMWare binaries can be downloaded from their webpage.
2. Virtual Machine Setup
Before you install Minix 3, you will need to create a new virtual machine configuration. The VM configuration specifies the parameters of your Virtual machine, e.g., how much memory you want the VM to use, how big you want the virtual hard disk to be, etc.
2.1. Create a Virtual Machine -- case: VMware Server
In the main menu of VMware, select New Virtual Machine.
Press Next in the Welcoming Screen.
At the Virtual machine configuration menu, we select Typical.
At the Select a Guest Operating System, select Other and Version Other.
For Virtual Machine Name, write Minix3 (anything would work).
At the Network Type screen, select Use bridged networking.
For Disk Capacity, enter something around 2GBs, although even smaller values would work. That is the size of the virtual partition where Minix will be installed. Tick the Allocate all disk space now.
Pressing Finish will create the Disk Image and the Virtual Machine that we will run.
2.2. Create a Virtual Machine -- case VMware Workstation and VMware Player (version > 3)
In the main menu of VMware, select New Virtual Machine.
At the Wizard, select Typical; and then, press Next.
For the Guest Operating System Installation, select I will install the operating system later; and then, press Next.
At the Select a Guest Operating System, select Other and Version Other.
For Virtual Machine Name, enter Minix3 or some other meaningful name.
At the Specify Disk Capacity, enter 2GBs, which is enough for all packages and sources. You can make it larger if you need to add more source files.
At the Ready to Create Virtual Machine, ensure that Power on this virtual machine after creation is not checked; and then, press Finish.
You will need to edit the memory settings according to your needs. In the Devices section, select the Memory, and adjust the memory accordingly. Note that, in order to run the X Window System on Minix, you need at least 384MB.
2.3. Create a Virtual Machine -- case: VMware Player (version < 3)
If you are using the free VMware Player, you do not have the ability to create new virtual machines. The simplest way around that is to use EasyVMX to create your new (empty) virtual machines.
Choose the Super Simple virtual machine creator at http://www.easyvmx.com/.
Name the machine whatever you want.
Operating System: Other OS (Note: choose the one that is NOT 64-bit).
Choose appropriate memory and storage sizes (e.g., 512 MB Memory and 2GB storage).
Don't worry about the LiveCD ISO, leave that blank (it will be dealt with, later).
Press Create Virtual Machine.
Download the compressed file, and unpack it. It should contain a directory with a bunch of VMware files.
Start VMware Player, choose Open an existing virtual machine, and select the .vmx file in the directory you just unpacked.
Once the virtual machine starts, go to the Devices Menu; and, in the CD/DVD item, choose Connect to Disk Image File (iso). Select the Minix3 ISO that you downloaded from the Minix 3 web-site.
If necessary, reset the machine with Ctrl+R; and, it will boot from the ISO.
2.4. Installation
Assuming you have downloaded and decompressed a MINIX 3 ISO image from the download page, you can mount the ISO file:
Select Minix3 in the Inventory List on the left.
In the Devices section, double-click on CD-ROM.
Select Use ISO Image.
Browse, and select the .iso Minix image that you downloaded earlier.
Then you can follow the normal installation instructions.
When the installation is over, type
shutdown
When you get the d0p0s0> prompt, enter off to shutdown the Virtual Machine.
I would like to open a custom finder window on plugging in a USB drive without activating any applescript on the Mac.
I know for sure that it is possible because, I have a USB from VMWare (VMware fusion app) that does the same. As soon as I plug in the Fusion app USB, it opens up a custom finder window.
Could someone help me out with this please?
Have you taken a look at this?
http://jordan.broughs.net/archives/2008/03/creating-cross-platform-windows-and-mac-installer-cds
It rounds down to creating a custom .dmg and then burning it to the usb key with the following command sudo dd if=~/path/to/image.dmg of=/dev/rdisk{N} bs=1m
where {N} should be replaced with the correct disk number that you can lookup at: diskutil list
That's all there is to it.
I have an application that uses DirectX to capture the screen. The application works fine locally, however when I run it through a remote desktop session the IDirect3D9::CreateDevice function fails:
d3dpp.Windowed=WINDOW_MODE;
d3dpp.Flags=D3DPRESENTFLAG_LOCKABLE_BACKBUFFER;
d3dpp.BackBufferFormat=ddm.Format;
d3dpp.BackBufferHeight=nDisplayHeight=gScreenRect.bottom =ddm.Height;
d3dpp.BackBufferWidth=nDisplayWidth=gScreenRect.right =ddm.Width;
d3dpp.MultiSampleType=D3DMULTISAMPLE_NONE;
d3dpp.SwapEffect=D3DSWAPEFFECT_DISCARD;
d3dpp.hDeviceWindow=hWnd;
d3dpp.PresentationInterval=D3DPRESENT_INTERVAL_DEFAULT;
d3dpp.FullScreen_RefreshRateInHz=D3DPRESENT_RATE_DEFAULT;
if(FAILED(g_pD3D->CreateDevice(D3DADAPTER_DEFAULT,D3DDEVTYPE_REF,hWnd,D3DCREATE_SOFTWARE_VERTEXPROCESSING ,&d3dpp,&g_pd3dDevice)))
{
ErrorMessage("Unable to Create Device");
return E_FAIL;
}
I am using Windows 7 to access Windows Server 2008 R2 with RDP.
What exactly is wrong here? I read that its possible to do use Direct3D through RDP.
I don't know the exact reason for failure, but I can give you a direction.
When you connect through the RDP the Windows doesn't load your native video driver at all, and nothing is actually displayed on the monitor. Instead the system loads the RDPDD virtual video driver, which draws everything in the system memory, and sends it to RDP client over the network. This is how remote desktop works.
So that your native video card/driver is not involved at all. RDPDD is a very minimalistic "frame buffer" driver, it does not support Direct3D/DirectDraw at all.
OTOH you call CreateDevice with D3DDEVTYPE_REF parameter, which should work even if you don't have D3D-compatible video card, the D3D should be emulated in software. Hence - I don't know why this happens. I can guess that the problem may be within the D3DPRESENT_PARAMETERS parameters. Perhaps some of them may not be emulated.
Try to check the error code, play with D3DPRESENT_PARAMETERS .
Haha, the problem was I had not the DirectX drivers installed. After it works!