ImageJ-Win64 won’t start

Upon freshly downloading and extracting FIJI for Windows 7 64-bit, I found that typing at the Command Prompt:

ImageJ-Win64.exe

would do nothing.

I found that typing (once)
ImageJ-Win64 –cp jars/javac.jar

fixed the problem–thereafter, I could just click on ImageJ-Win64 to start.

Reference:

https://groups.google.com/forum/?fromgroups=#!topic/fiji-users/1yNPbNM13l4

workarounds for rare case where cloud server is messed up and you need your sshfs mount!

I sometimes access an enterprise Windows system that always makes its network “cloud” files accessible via sshfs.

I don’t know the details of this server system, and one day I was in the field and needed my networked files in the cloud badly, but couldn’t SSHFS mount via the head end server from any computer via VPN, or even back in the office (LAN).

I also couldn’t ssh into the main head end server, but I could ssh into the individual cluster units. I could not sshfs mount from those cluster units, but I COULD see my files via ssh.

I found two ways of copying my files to my local PC:
(1) using a Windows guest virtual machine, I was able to mount the windows side of the network share (that I can typically always mount via sshfs)
(2) I could sftp and scp from one of the cluster nodes (not the head end node, since I couldn’t get in via ssh).

Probably a weird, incorrect workaround–but it got me my badly needed files in a pinch.

sshfs: Input/Output Error

On some servers, when using SSHFS, the drive will appear to mount, but when trying to access the drive in Terminal you get
Input/Output Error

The “fix” for this at least in some cases appears to be appending a trailing slash to the remote directory. Here’s an example:

SCRIPT THAT GIVES “INPUT/OUTPUT ERROR”
sshfs -o workaround=rename joe@server:/opt/netfiles ~/Z

CODE THAT WORKS
sshfs -o workaround=rename joe@server:/opt/netfiles/ ~/Z