My synergy version is 1.4.10 in both server and client.
Server is Windows 10 and client is ubuntu 18.04
Capitalization using caps lock is working and keyboard shortcuts using shift key is working as well.
However when I capitalize using shift key, it doesn't work.
What's the problem??
I just solved this problem by upgrading synergy version.
It seems like a bug of version 1.4.10.
Related
I am an absolute beginner to Ros and i have a very simple Question. Curiously i coudn´t find an answer yet:
I want to use ROS for Windows 10 (with Visual Studio). Windows Version 19.04. The commands out of the Tutorial (http://wiki.ros.org/ROS/Tutorials/InstallingandConfiguringROSEnvironment) do not work within the x64-Terminal or the selfcreated ROS-Terminal of Course. Is there a way to use them in Windows or another tutorial for Windows?
Thanks for your help and sorry for the simple question!
I think this documents are helpful for biginner to ROS on Windows.Please note that there are many big differents between ROS 1 and ROS 2 on Windows.
Bringing the intelligent edge to robots with ROS on Windows 10 and Azure.
ROS for Windows
Installing ROS 2 on Windows
I am having a probably trivial issue with the Cloudera Quickstart virtual machine. I tried many things out, but I don't manage to make it work. So, first, I installed the Virtualbox image on a Windows workstation which has a German standard (qwertz) keyboard.
In the virtual machine, which runs a Linux Centos, I set the German keyboard and everything works fine. Now, as the workstation is in my office, I installed TeamViewer, in order to connect from my MacBook from home. And here it comes the issue that struggles me.
The MacBook has a German keyboard and all the keys, which do not require the alt combination works fine. If I need, for example # (alt+L) or \ (alt+shift+7), or anything that requires the alt combination, nothing appears on the Centos (in the Windows workstation it would correctly appear!). Could you imagine to code without \ ~ # ??
I tried also to install a German(Mac) keyboard and also a screen keyboard (florence) in the Centos and they also do not work properly. Is it a TeamViewer issue or a VirtualBox issue? How can I solve it?
Any help is appreciated!
I figure out that is a Virtualbox issue, that takes the keyboard configuration of the host in which is installed, in this case Windows 10. I could not find a simple way changing the keyboard setting in the Centos machine run via the Mac Os in TeamViewer to make it work. So, as workaround, I opted for using Docker Cloudera Quickstart rather than the VM. And everything works fine and can happily type all the #~|\ that I need.
I'm having a problem with installscript, and I'm trying to get the OS Version and detect if it's windows 10.
The Key that I'm trying to get is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\[CurrentVersion]
Using regedit, Windows 10 has the value 6.3 there. The same has Windows 8.1 and Windows 2012.
But, if I use WINVER on commandline, I get 10.0. How can this be?
Instead of reading the value CurrentVersion, read the new values CurrentMajorVersionNumber (which is 10) and CurrentMinorVersionNumber (which is currently 0) under Windows 10. Those 2 keys are new in Windows 10 to detect Windows Version from Registry.
At runtime, you need to have your application manifested correctly in order to get the right value from the version checking APIs; see this MSDN topic on how to set it up, and then you can use the Version Helper APIs to get the right value. I don't know how much of that you can do within your installer project though.
we have a setup developed in installshield vr 6.3. it is a self extractable single setup. it work fine in most on most of the Windows version but on Windows server 2003 64bit in Execution mode when doing RD it return user windows directory against WINDIR i.e. c:\documents & settings\fcuser\windows instead of C:\Windows. According to http://support.microsoft.com/?kbid=186499 it should work fine when i change the compatibility bit of Setup but it didn't. i tried changing compatibility bit of these key too (INSTRUN, SETUP and SETUP1 ) but it didn't work either. but when i when i run the setup within the self extractable by extracting it work fine.
InstallShield 6.3 is 10 years old, released when Windows 2000 had just come out. There were no 64-bit Windows OSes at that time. I'm not surprised you're having trouble. You really should think about using a modern version of InstallShield, or migrate to something like Wix/NSIS if upgrading is not financially possible.
As I work-around to using WINDIR, you could try getting this Registry value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRoot
Or try to get the value of this environment variable:
%SYSTEMROOT%
I am using Ubuntu 10.04 and Firfox 3.6.3. The tab key, arrow keys and page up / down keys have suddenly stopped working when on Firefox. They work fine on any other application (like Google chrome). I am not sure what is happening and how they got disabled, only for firefox.
tools|Options|Advanced|General tab - uncheck the first option for cursor key
The problem was resolved by removing Delicious Firefox plugin. It was not compatible with the firefox version I was using.