From owner-chemistry@ccl.net Mon Mar 12 14:03:00 2007 From: "Mark Fleharty mark.fleharty%gmail.com" To: CCL Subject: CCL: Force Field Explorer difficulty with display Message-Id: <-33783-070312140130-27034-brVKYB9LK4i9T6Vu71IvQQ#%#server.ccl.net> X-Original-From: "Mark Fleharty" Content-Type: multipart/alternative; boundary="----=_Part_8733_17898950.1173722473465" Date: Mon, 12 Mar 2007 12:01:13 -0600 MIME-Version: 1.0 Sent to CCL by: "Mark Fleharty" [mark.fleharty|-|gmail.com] ------=_Part_8733_17898950.1173722473465 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Dr. Hultin, I have found out a few things. The problem I was having was due to my ATI video card not being compatable with the version of Java3D shiped with FFE. One way around this is to install a newer version of Java3D, and then double click on FFE's .jar file. The points you made are all good ones. I have found a few issues related to using a windows based text editor, and unix based editor on a .xyz file can cause some files not to work properly with TINKER even though they look perfectly good. The problem appears (to me anyway) to be related to Windows use of a carriage return and new line, rather than just a new line that unix uses. I used the cygwin utility dos2unix on all the .xyz files, and viola, they all worked. Thanks, Mark > > ------=_Part_8733_17898950.1173722473465 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dr. Hultin,

I have found out a few things.  The problem I was having was due to my ATI video card not being compatable with the version of Java3D shiped with FFE.  One way around this is to install a newer version of Java3D, and then double click on FFE's .jar file.

The points you made are all good ones.  I have found a few issues related to using a windows based text editor, and unix based editor on a .xyz file can cause some files not to work properly with TINKER even though they look perfectly good.  The problem appears (to me anyway) to be related to Windows use of a carriage return and new line, rather than just a new line that unix uses.  I used the cygwin utility dos2unix on all the .xyz files, and viola, they all worked.

Thanks,

Mark

 


------=_Part_8733_17898950.1173722473465--