Tips for Windows Users
These are some basic tips for users whose primary machines are Windows.
- 1 Logging into Proteus
- 2 Transferring Files
- 3 Text Editors
- 4 Graphical Display to Windows
- 5 Password-protected ZIP Files
- 6 Scripts Created on Windows
- 7 References
Logging into Proteus
Logins to Proteus are via commandline only, using SSH. Here are three ways to do so.
OpenSSH in Windows 10
Windows 10 provides the full OpenSSH suite as an optional feature.
Installation instructions: https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse
Once installed, run the ssh command within Windows PowerShell.
Here are a couple of tutorials on how to use this feature:
Access to Proteus is via SSH. Use the PuTTY ssh client for Windows:
If for some reason PuTTY does not work, you may use one of these alternatives:
- Use the Google Chrome browser, and install the Secure Shell Chrome App. This will run the remote terminal in a tab in your Chrome browser.
- Termius, an open source SSH terminal client (also includes PowerShell terminal)
- terminus (alpha release)
- This free SSH client from the makers of WinSCP
- Bitvise SSH client
The PuTTY project also includes an SCP and SFTP client, downloadable from the link above.
OpenSSH in Windows 10
The OpenSSH feature in Windows 10 provides all the usual OpenSSH command line tools: ssh, sftp, scp. See above for links to information on installing it.
Use PowerShell to run it -- type "yes" at the question "Are you sure you want to continue connecting?":
WinSCP supports some newer encryption standards.
Download it from: http://winscp.net/eng/index.php
Code 32 system error WinSCP may raise this error in certain circumstances. The solution is:
Options >> Preferences 1. select Storage (in left panel) and under the Configuration storage section, select ‘INI file’ AND 2. select Endurance (in left panel) and under the Enable transfer resume/transfer to temporary filename section, select ‘disable’
NOTE FileZilla has some issues with connection because it tries all available SSH keys, which may lead to multiple authentication failures before it succeeds in logging in. There seems to be no fix for this issue on Windows, at least, and possibly the other platforms.
FileZilla is a graphical file transfer program that supports SFTP and FTP: https://filezilla-project.org/
To connect to the login nodes, use one of the following as the "Host" in the quick connect bar:
Rsync provides differential updates, which makes it well-suited for keeping a directory tree synchronized between two computers.
Some Windows text editors handle multiple line-ending styles, e.g.
Graphical Display to Windows
If you want to use a GUI application on one of the login nodes (proteusi01, or proteusa01), your Windows machine must have an X11 server installed to be able to display the GUI. Either of the two below should work.
Once installed, ssh to one of the Proteus login nodes giving the "-Y" option:
ssh -Y firstname.lastname@example.org
Or use your SSH client application setup to enable "X11 Forwarding".
Then, try the command "xclock": if your setup is working, you should see a small analog clock window pop up.
NOTE: remote display in this manner is very slow, and noticeably laggy.
- MobaXterm -- NB apparently uses Cygwin/X and PuTTY under the covers.
Drexel has a license for X-Win32. Download is available at:
See documentation at: https://www.starnet.com/xwin32/
See also their documentation on how to set up PuTTY for remote display:
Password-protected ZIP Files
If you have a password-protected ZIP file created by WinZIP, it cannot be decrypted by the "unzip" program. Use "7za" instead:
[juser@proteusi01 ~]$ 7za e myfile.zip
Scripts Created on Windows
Text files on Windows have different line endings. This may cause scripts (shell scripts, Matlab .m files, makefiles, etc.) to fail when used on Linux. If "qstat -j JOBID" shows an error like:
error reason 1: 05/14/2015 11:17:46 [1002:69060]: execvp(/cm/local/apps/sge/var/spool/ic21n04/job_scripts/213677, "/cm/local/apps/sge/var/spool/ic21n04/job_scripts/213677") failed: No such file or directory
it is likely that the script has the wrong line endings.
To convert a Windows text file to a Linux text file, use the dos2unix command:
[juser@proteusa01 ~]$ dos2unix filename