|
Site Map
|
Occasionally, difficulty in getting a clean download of a program or file occurs. There can be a myriad of causes for this, and here we don't attempt to address the causes but instead offer some possible workarounds.
We offer three methods of downloading files:
The three types of operating systems for which we distribute files - Macintosh, Unix, and Windows - each have a different method for terminating a line in a text file. The Mac uses a carriage return (\r, ASCII code 13), unix uses a line feed (\n, ASCII code 10), and the PC uses both (together). If you are viewing a text file that is just a few long lines, then this is probably the reason. Alot of text processors will recognize the different use and will translate transparently; some won't, especially the older programs. You may need to try a "soft wrap" when viewing a text file; but, unless the file is purely for "human eyes" only, it is probably best not to change it by doing a "hard wrap" as this may change the way it is read by a program.
We attempt to send you text files with the right line breaks. This is easy to do when you are choosing a particular bundled package of programs and text files. When it is just a text file that is being requested, we make an educated guess as to what platform you are accessing the site with, and send along that file. The default is unix line breaks. Of course, to be certain, if you suspect a file with the wrong line breaks, then you can retrieve the same file with your platform's breaks from the FTP site. There you will find subdirectories of text files called "Mac" or "Win" with those line breaks. The upper level files, like the default download is unix line breaks.
One more twist with Macintosh files. Pre-OS X, Macintosh files typically have both data and resource forks. This is not normally a problem for file transfer when both sides of the transfer want to transfer a file with two forks. Well, that's not always the case. You may want a Mac file, but not knowing that, we'll transfer a file with no resource fork. Sorry about that. If on your Mac the kinemage files or Mage/Prekin programs do not show the Mage icons, then you probably have files without resource forks. The same absence can cause loss of the ability to double-click a kinemage and start Mage.
For text files such as kinemages, we try to detect if you are using a Mac by the internet browser headers. If we do, then for text files we'll send a file that has Mac line breaks and a resource file as appropriate. The MIME type is application/x-stuffit which on most modern Mac browsers will invoke StuffIt Exander™ª, to translate the file correctly. Stuffit Expander is available free from Aladdin Systems in case you don't have this excellent utility program.
Don't scream. Drop me an email with as much description of the problem as you can, and I'll try to help.
|
|
Kinemages | Java Mage | Software: |
|
Validation | Rotamers | FTP | 2D Gallery | Lab Info |
|
||
| Display | Contacts | Utility | ||||||||||