Because these are file formats where 3D coordinates are mandatory, and you don't have a Corina license. The editor only creates 2D coordinates while you draw. It makes an attempt to compute 3D coordinates if it is instructed to save the structure, but the save is aborted when the editor, according to its computing instructions for the 3D coordinate property in the internal property configuration database, tries to load Corina as a dynamic module and does not find it. It is however possible to import a structure with 3D coordinates, for example as XYZ file, and write it out in PDB, as long as the structure is not edited. Editing a structure with 3D coordinates results in loss of 3D information.
Because Corina is not part of CACTVS. I was not involved in its development. I just wrote the interface code in order to demonstrate that it is possible without much effort to integrate programs which were not developed within the CACTVS framework as dynamically loaded modules, external programs or remote servers into the system. Corina can be obtained by educational institutions for free if you, for example, agree on some kind of joint project, and it can be bought for a reasonable price by commercial companies. Contact this adress for details.
Because it is buggy and completely outdated. Please refer to the manual, or volunteer to bring it up to date.
Because the help texts have not yet been written. Volunteers are of course welcome. Adding empty menus helps to avoid too frequent updates of screen shots in manuals and WWW pages. Hopefully, someday all functionality will be implemented, and the menus filled.
Hmmm. Can I refuse to answer this question ? The answer is closely related to the 'Help' menu problem.
Because the status of the copyright is not yet decided upon, and because there are still changes in the core data manager library. Additionally, part of the library code was developed while being paid by a company. Their stance toward the free circulation of source code is yet open, and the source is currently not cleanly separated into copyright domains. However, the tool collection definitely will always remain free, and it will continue to be updated. If you want some special routine, such as the Tk structure drawing commands, or the include files for the datastructures, you are welcome to ask for them by email.
CIF is the Chiron Interchange Format, not the Crystallographic Information File. The former is the file format of the Chiron stereochemistry evaluation program from Prof. Hanessian, Montreal. It (and the file format name) existed long before the Crystallographic Information File format was defined.
Probably you are in the U.S.A, and you don't have much experience with long distance ftp transfers. Our local network connections are quite good, and 800 bytes/sec across the atlantic at daytime is not bad at all. Be patient. The same arguments hold true for the speed of the http WWW transfers of these pages.
It is not yet released officially. Sometimes there may be distributions in the ftp area, but they are undocumented and unsupported. If you grab one of those, you are on your own.
Because there are font resolution problems on this system. I tried to add explicit font names on every button and menu. However, the font selection in the IRIX Xview port is buggy. Sometimes the correct font is selected, and sometimes something large and ugly. I guess this is some uninitialized variable problem in the Xview library. The very same window sometimes pops up with completely correct fonts, and sometimes not. This is not predictable, and I am certain my code always passes in the correct font handle.
You may be running SVR4 networking. CACTVS needs the BSD-style portmapper in order to negotiate RPC channels, and there must be transient ports available for non-superusers. I think there is not much need to run rpcbind instead of portmap, so you might be able to reconfigure your system without any loss of functionality.
Because I am slowly moving the whole interface toward Tk. It is possible (a minor hack) to run Tk and Xview concurrently in the same program, and so stepwise migration is easy. No new Xview-based windows will be implemented, and old Xview windows will be gradually replaced by Tk counterparts. The generic data manager programs in the tool distribution don't contain any longer any Xview code.
Back to the CACTVS home page