I am trying to control a windows 10 laptop from a Raspberry Pi 4 with Raspbian. I would like to do this over an HDMI and/or USB connection between the two devices. It does appear that accessing a windows 10 computer via CEC connection through the HDMI is not feasible. is anyone aware of other ways to make this work?
I'd like to be able to see the windows 10 desktop from the Raspbian GUI and interact with it with a mouse and keyboard connected to the Raspberry Pi.
Related
I installed "onboard" as a virtual keyboard on the system. It looked much nicer and more useful than matchbox. I went into the settings and chose the auto open option when I edit the post. after that i restarted my raspberry pi. As it didn't come on automatically, I couldn't run it from the terminal or the menu normally. The error I get when I try to run it from terminal
Hej blackmamba,
I had the same issue with the on screen keyboard florence. After I installed at-spi2-core, it didn't crash anymore, though i could not get it to open automatically.
So I tried installing onboard and everything worked quiet well. Might be a hint..
regards, jarvis
Raspberry Pi B+
5.10.63 Kernel
Debian Buster 10
Waveshare 10.1" HDMI LCD Touch Display
I want to run my GUI in Raspberry PI but i dont want Raspberry PI's desktop to seen and Nobody can acces the desktop or my codes. Is that possible? if it is how ?
by the way i coded my gui by Python and Pyqt.
I am looking for a way to install noobs raspbian from network. I mean i do not want to connect an hdmi TV, mouse or keyboard.
What i read in documentation is to download noobs (full version) and copy files into sd card. I have read i need to change something in recovery.cmdline file (Adding vncinstall word).
This works for the first raspberry boot: I can see installation screen through VNC. I have choose "Raspbian + pixel" installation. Then, I can see the progress bar.
But at the end of the installation, when the raspberry reboots, i have no VNC, neither ssh or telnet server and at this time i need to plug an HDMI TV, mouse and keyboard.
Do you know how i can automaticly launch a VNC or SSH server without having to plug a TV and keyboard ?
Thanks
I am using Windows Insider Build 14342 windows 10 OS. Trying to connect to raspberry pi 3. I have installed the Iot Core in Raspberry and I can connect to the device using putty and powershell. The visual studio for some reason doesnt deploy my Application.
Its a basic blink example from ms-iot github. I have set ARM, Remote device and gave ip address of the device, selected Universal(unencrypted protocol) in properties of the project.
The project builds fine and doesnt deploy to my device. Am i missing something.
I had this problem before one week. Here are steps I use to solve this issue:
Open Network and sharing Center.
click on your Ethernet connection
click property
Select IP4
Change your IP to be in same rang with your raspberry pi
After that your visual studio will able to detect your device automatically.
I made an WinCE 6.0 R2 image and load it into VMWare Player 3.1.3. The host operating system is a Windows XP Sp3. I followed this article and all worked fine (the article uses VMWare Workstation, but it worked fine also with VMWare Player).
My final goal is from the virtual machine WinCE to use the Bluetooth USB dongle attached to the Windows XP host computer. In the WinCE image I had added support for Bluetooth USB like in this Mike Hall's post. Also I want to mention that I had included support for USB Host when I created the BSP, and also USB drivers are checked.
When I go in WinCE -> Control Panel -> Bluetooth Device Properties, Bluetooth Manager is launched. But if I try to make a "Scan device" I am getting the following error:
Bluetooth hardware error 10050 (controller not present)
But the dongle is attached to the VMWare Player and disconnected from the host, so theoretically the transport layer is controlled by the virtual machine and WinCE can talk with EHCI of the USB.
Can anyone give me a hint to follow? Any suggestions are welcome.
I have no idea whether the stuff described at http://www.codeproject.com/KB/windows/bth4devemul.aspx is required in your case...
There the FreeBT.NET stack is installed on the host PC to enable the WM emulator to use a host-attached Bluetooth dongle...