The default value is the Cygwin Setup folder you started with and that should be the correct place. Just click on the Next button to proceed. You will see the Select Packages screen that you have seen before , except that it's displaying the Categories already.
At this point, you need to, again, select openssh and X11 to be installed. So, you should do exactly what you did before. Scroll down to find the "Net" category. Scrool further down to find openssh inside the "Net" category and make sure that it's selected for installation i.
Scrool further down to find nano inside the "Editors" category and make sure that it's selected for installation i. Then scroll all the way down to look for the X11 category. It's probably showing "Default" just like before. Click on the icon to the left of "Default" once and "Default" should change to "Install" like before. Now you are ready to install. Click on the Next button to install Cygwin.
This can take a long time since it's copying and setting up a lot of stuff. When installation is about to finish, you may get a popup window saying that you have "Postinstall script errors". Please read what's in the window. If it says that these do not necessarily mean that it will cause packages to fail, then it's okay to proceed.
If there are more serious errors, you may have to reinstall everything since some important packages may be broken. When installation is done, you will see the following screen: You should check both checkboxes and then click on the Finish button to close Cygwin Setup. Desktop Setup. After installation has completed, you should have a new icon, labeled "Cygwin64 Terminal", on your desktop.
If you double-click on it, the Cygwin Terminal program will run and you will see something like the following your user namd and directory name will most likely be different : You also need to start the X11 server if you need to ssh to another machine and be able to run programs that have a graphical user interface. All you need to do is to click on your Windows' Start Menu, scroll down to the C section and look for Cygwin-X folder, click on it, and look for the "XWin Server" icon.
It may look something like the following: Drag the "XWin Server" icon onto your desktop and you are all set! To start the X11 server, just click on the "XWin Server" icon on your desktop. If you are running Windows 10 Professional, you should right-click on the "XWin Server" icon and select "Run As Administrator", if you know the admin password. You should do it this way every time you want to start the X11 server. If you click on the "X Applications Menu" and click on the "System Tools" submenu, you can see that there are a bunch of terminals available to you.
Go to your desktop, right click, go to new and new shortcut. Right click on the new. Insert these 2 lines if they are not already.
Save the changes and then try it out. Double click on the startxwin. If you use SSH Secure Shell Client, you may wish to not to have that xterm pop up and to instead just use it to start your xwindows session.
When you double click on startxwin. If you see it, you are all good. If not, you screwed something up and you should re-read this document thoroughly and make sure you installed everything you need from step 1.
Otherwise if you are using openssh from your xterm window that opens after you execute startxwin. Go back in and make sure the settings saved when you checked the X11 port forwarding box. Step 4: Installing mentor fonts. For most applications, we would now be ready to go. Keyboard layouts that are not automatically detected can be added to the list of automatically supported layouts easily upon request.
Command line configuration support is also provided to allow manually specifying a keyboard layout. Tray Icon - A tray icon is provided to indicate that the server is running, to allow easy access to the Exit command, and to toggle visibility of the root window in Multiwindow mode. Configurable Tray Icon Menu - Menu entries can be added to the configurable tray icon menu via a. XWinrc file in the user's home directory, or via a system.
The people answering questions are usually the same people that wrote the software, so they can often fix a problem if one is discovered. In practice, it is untested with versions prior to Windows XP and possibly broken.
0コメント