Winscp notes

Setting the Putty path

View->Preferences->Applications->Putty/Terminal client path

for putty in programs folder

%PROGRAMFILES%\PuTTY\putty.exe -t -m "%TEMP%\putty.txt" !`cmd.exe /c echo cd "!/" ; /bin/bash -login > "%TEMP%\putty.txt"`

for putty in quicklaunch folder with ability to change the window size on open

"%appdata%\Microsoft\Internet Explorer\Quick Launch\putty.exe - Shortcut.lnk" -t -m "%TEMP%\putty.txt" !`cmd.exe /c echo cd "!/" ; /bin/bash -login > "%TEMP%\putty.txt"`

To make putty open full screen you will need to edit the shortcut by right clicking the putty icon, selecting ‘Properties’, under ‘Shortcut’ tab change ‘Run:’ select input to ‘Maximized’.
full screen putty

ssh timeout

Working with putty and winscp these programs would timeout/freezes and have to reconnect. Here is how I fixed it.

On the server, have a look in /etc/ssh/sshd_config and see if you have these variables set. If not, add them:

TCPKeepAlive yes
ClientAliveInterval 190

Or on the client edit ~/.ssh/config and add this line

ServerAliveInterval 60

In putty setup under category Connection there is “Seconds between keepalives” option. It was “0” and I changed to 90.

The same option is also in WINSCP program.
winscp keepalive


Laravel blade not compiling or showing in browser.

I was having an issue that when I saved a file using winscp to laravel4 the view in the browser would not change. I figured out that laravel view blades caches to app/storage/view and the way it knows whether to recompile it is by the dates the view blade file was changed and the cache file was created. In winscp the cache file was off by an hour ahead.

The way I fixed this was by changing winscp login environment settings to “Preserve Remote Timestamp”

and also adjusting my server time to match the actual time on my other computer.

The server time has to be an earlier time than your computer

Also this was a fix to the issue with sublimetext sftp package sync funcitonality.