I am starting up with Azure.
Got one Azure machine with Windows 10.
Logged in with RDP.
But not able to control volume with in RDP window.
I have to go back to my original window and change volume.
And volume button in the RDP window is does nothing when clicked:
When I opened Adjust system volume:
Getting No audio device installed message:
How can be the volume controlled from Azure machine logged in from RDP?
It started working after setting up Sounds.
Right clicked on speaker icon in system tray, the below menu appeared:
Clicked on Sounds, below pop-up appeared:
Clicked Yes to enable Windows Audio Service, below box appeared:
Cliked Ok to set the scheme.
Now I am able to play music and listen. Can control volume.
Related
`Has anyone seen the following error in Datawedge 3.2.4:
Error : Scanner : SCN1: Failed to get supported RSM attribute count. Error=a0000012
Error : Scanner : SCN1: Scanning failed. Error : a000001d .
If so do you know the cause or fix?`
One possibility is that your scanner is trying to connect by wireless or Bluetooth to a nearby network. Finale Data Collector operates in disconnected mode, so you don't need any wireless communication on the scanner. You can turn off the scanner's wireless modes to eliminate any pauses from the start menu or Windows icon on the task bar: Settings > Connections > Wireless manager.
If Finale has crashed or if some other software running on the scanner has crashed, you can do a warm reboot on the scanner by pressing and holding the red on/off button for 10 seconds. The button is in the upper right of Motorola MC70 scanners. A warm reboot will recover from any crashed applications and will not erase your hard drive or lose any data.
There is other scenarios to what you are experiencing
A. Scenario #1
The DataWedge may have become corrupted and needs to be reinstalled. The dataWedge is an application that allows to send scanned data from the barcode scanner to the any Finale application you have running on the scanner.
Download datawedge.CAB (you will need to have a Zebra free account)
You must have, or, order your Docking Station Kit (Chargers/Cradles/Docks in the Enterprise Scanning industry are SKU's sold separately, by factory protocol). Plug it into the wall, and, into your Windows 7(preferable) PC USB Port with mini USB-to-USB Communication Cable.
With your MCxx powered on and PC on the internet, dock your MCxx into the cradle and allow the USB drivers to sync with the computer for approximately 10 minutes - this allows your PC's "Windows Mobile Device Center" sync program to auto-install on your PC. This program allows you to view and transfer programs, files, and updates from your Computer to your handheld.
With your MCxx connected to Windows Mobile Device Center, hold you mouse over File Management and then click "Browse the contents of your device". Once your device window is open, drag-and-drop or copy-and-paste the DataWedge.CAB file into the window, to paste onto the unit.
Once DataWedge.CAB file is pasted onto the unit, the revert over to the MC70 touch-screen. From the docked MCxx, click the Windows Start Icon, then click programs, then click File Explorer. Within Windows File Explorer click the top-left dropdown arrow in the grey takbar to select My Device. There you will find the DataWedge.CAB file that you pasted. Click that file to run the installer. A Selection Screen pops up of where to install, and you must Select "Application" to install Data Wedge onto the MC70, click install. Once installation is finished, allow program a minute to initialize then Start Scanning.
B. Scenario #2 - The default baud rate for the scanner needs to be increased.
Open Data Wedge (by clicking icon in toolbar tray on bottom-right of device homescreen > Advanced Configuration > Profiles > Profile0 > Input > Serial > COM 1 > Port Settings > Baud Rate > 115200 > Back
You will want to change the Baud Rates on ports : COM 1 / COM 3 / COM 7 / COM 8.
Once Complete, Keep Clicking Back until datawedge reports that all changes are saved.
Finlay, if none of the above works it might be very helpful to have another Windows mobile that actually works
you can launch the command "System Info" on the command prompt of both of your Windows mobile terminals (the one that work and the one that doesn't) then compare the diferences on the settings
I'm happily using x2go to connect to a remote Ubuntu Server 16.04 with XFCE installed from my local pc with a local resolution of 1920x1080 on a HiDPI screen (13''). If I run the x2go client from a virtualized Linux (Linux Mint 18.03 with XFCE), everything works well and I can see a really sharp image of the remote desktop. Problem is, when I try to connect directly from Windows 10 the image is blurred and the resolution is wrong. I tried to play around with the x2go client settings but no way, the image is always terrible. I also tried to use PyHoca and different X-servers but the result is the same.
Is it a well-known problem? Any suggestion on how to fix it?
Thanks in advance.
I had a very similar problem: A Dell laptop with an Nvidia graphics card, having a resolution of the built-in flat panel of 1280x800. I connected this to an external screen with HDMI with a resolution of 1920x1080. However, X2Go seemed to pick up the resolution of the built-in screen instead of the actual screen, making everything seem blurry (interpolating 1280x800 to 1920x1080).
This is what fixed it for me: Navigate to the C:\Program Files (x86)\X2GoClient\VcXSrv\ directory in Explorer. Select the vcxsrv.exe file and right-click it, choosing Properties from the popup menu. Go to the Compatibility tab, and in the Settings section there, select the option "Override high DPI scaling behavior. Scaling performed by:" and then select "Application" in the combo-box below.
Restart the X2Go Client to have its X server start with this new setting.
This fix also solved X2Go Windows Client crashes in my setup.
I have basically the same scenario: connecting from a high DPI Windows laptop to KDE on Debian, in my case for Desktop Sharing. The client would connect okay, but display only a portion of the remote host's screen.
Keyboard shortcuts would not scroll the client window.
Any attempt to show more (maximize, go full screen, click-and-drag client window border) would seem to work for a second, then crash.
The Compatibility scaling change fixed the instability - no more crashes, yay! - but did lead to slow repaints as noted by Algeboy.
Upgrading to a newer version of VcXsrv also did not resolve the crashes - Compatibility change still required, but screen repaints are quicker.
To upgrade, download and install the latest VcXsrv in its own directory. Using Explorer or whathaveyou, apply the HiDPI setting to vcxsrv,exe.
Start x2go client but don't start a session. Click Options, Settings, then X.Org Server settings tab. Select "use custom x server". Point to the newly installed vcxsrv.exe and click okay. Restart the x2go client.
This apparently takes the version from 1.20.6.0 supplied by x2go to 1.20.14.0 (2022-04).
Screen refreshes are quicker if I minimize all applications on the host, allowing it to repaint the desktop, then restore whatever I want to work on.
How can I see the window of an app that shows on the second screen of my multi-monitor set-up when I remote in from another computer?
For example:
...on my laptop:
cmd: mstsc /span
rdc display configuration: Full Screen + Use all of my monitors for the remote session
...on the remote computer:
Open GitGUI or FileZilla for example.
Task bar shows application open.
The hover preview shows the app is open.
I can't see the app window on my screen (can't interact with it).
Nothing I do brings the app to a window I can use.
Anyone else come across this problem?
Thanks
Figured it out. Using the Windows key plus the right/left arrows, I can move windows from desktop to desktop.
I am trying to use a FireFox OS device that runs OS 1.3 on my app dev. I have went through the instructions and still there is no device name that i can test an app with. Are there windows drivers that have to be installed. It seems like everything was installed but there is no device name. I am not sure if I gave my phone an actual name on the setup menu but I would think there would be a default menu. The only thing is that I have not installed a simCard because I do not need the phone I just want to test my apps before they go up on the Firefox OS marketplace.
Note 1: When I plug in the phone it causes firefox OS to flip back and forth between the browser and the develop manager that opens when the web tools kit is opened.
Instructions that I found for the phone that I have ZTE OPEN FireFox OS
Power off your phone, remove the battery to access the microSD card and extract the card from its holder.
Connect the microSD card to your desktop machine.
Move US_DEV_FFOS_V1.1.0B04_UNFUS_SD.zip or EU_DEV_FFOS_V1.1.0B04_UNFUS_SD.zip (depending on the version you downloaded) to the root directory of your microSD card. Do NOT unzip the file.
Disconnect the microSD card from your desktop computer and return it to your phone.
Hold the volume up button and power key down simultaneously. Volume up is activated by pressing the upper part of the long key on the left side of the phone. If you did it properly, you’ll enter the Firefox OS recovery mode. (Note: the Firefox OS logo may display briefly before you enter the recovery mode; sometimes this can take a little while.)
Use the volume up/down key to move from one item to the other in the menu, and choose “apply update from external storage.”
Press the power key to confirm the selection. You’ll see a new screen listing the files you have on the microSD card.
Again use volume up/down key to select the firmware: either US_DEV_FFOS_V1.1.0B04_UNFUS_SD.zip or EU_DEV_FFOS_V1.1.0B04_UNFUS_SD.zip (depending on the version you downloaded), and press the power key to confirm.
If everything went well, you’ll see a sequence of status messages, culminating with one that says, “Install from sdcard complete.”. You’ll need to select “reboot system now” after the installation has completed. Your phone will then reboot, and you’ll see the configuration screen you saw the first time you powered on the phone.
I'm building my own Windows CE 6.0 image (NK.bin) and after Windows has been loaded is the screen just black. When i attach a USB to the USB slave port on the device the window saying "USB client Status" shows up and the mouse is visible and i can control it together with the keyboard.
However, I'm stuck at this. I been reading a similar post to remove all settings in project properties according to stackoverflow-post, without any result. I can't connect to the screen with "Windows CE Remote Zoom-in", but can connect with Remote Register and Remote Process.
Any clue?
I added explorer.exe to HKLM/init but the problem was that explorer was not included in the build. I had to choose the "standard" shell to include explorer, when i actually wanted the "thin client shell". This is still an issue to get some features from them both but at least this problem is solved and I can move on to next ;) Thanks again.