Transfer TIFF files from Macintosh IIsi to Windows PC

Jim,

That is not the web page mentioned in my message. Please see the text again.

Jan

Jim,

Very good. You may have to rebuild the Desktop on the PowerBook 180 if StuffIt Expander only appears with a generic program icon. Otherwise, you could now try to drag any previously downloaded file onto the StuffIt Expander icon (or try to open them from within the StuffIt Expander application). This should decode MacBinary (.bin) and BinHex (.hqx), and decompress StuffIt (.sit) files.

If you wish to test whether the communications portion of ClarisWorks can be made to work properly, you could try to download all the Communications Toolbox tools. After decoding and decompression, install them (the Extensions Folder of the System Folder).

http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English -North_American/Macintosh/Networking-Communications/Comm_Toolbox/

With these downloadable tools, ClarisWorks can only use the XMODEM protocol for file transfers.

ZMODEM is more advanced, probably easier to use, and offers more options. The shareware utility ZTerm would be the program to use for that protocol.

Jan

How do I rebuild the Desktop on the PowerBook 180?

Get TechTool 1.2.1. It is easy and does a complete job of desktop rebuild and will zap the Pram also without the repeated startups.

http://macintoshgarden.org/apps/techtool-121

http://macintoshgarden.org/apps/techtool

https://www.micromat.com/support-45/file-archives/62-techtool-121

Jim,

See the following article:

http://support.apple.com/kb/ht2344

Jan

I am not absolutely certain but the Mac should be able to read the PC floppy with the required control panel/extension. Or you can try the manual way for classic Mac OS.

Restart your computer while pressing the Command and Option keys. is the classic way to do the rebuild.

Jim,

Apparently, StuffIt Expander is working since the tools were successfully decoded.

Normally, a .sit compression would protect the Mac file structure (a resource fork and a data fork) as well. Something may have happened to that file during download/transfer, though. A new download/transfer could perhaps be tested. Also, some .sit files have been compressed in a format that requires a newer StuffIt Expander version.

The following archive, for example, contains many older communications programs (see the abstracts text file). Both BinHex (.hqx) and MacBinary (.bin) downloads are OK (do not attempt to carry out any decoding/decompression until on the PB 180).

http://ftp.funet.fi/pub/mac/info-mac/_Communication/_Terminal/

I do not know why ClarisWorks does not work OK. Maybe something with the basic Communications Toolbox in the system, or something with the tools versions. Have you checked whether the ClarisWorks 4 installer or the System 7.1 system installer (Custom Installation) could offer anything of interest? Otherwise, you would just have to concentrate on other terminal emulation utilities with file transfer capabilities. Unfortunately, I do not have access to ClarisWorks (1) nor to a System 7.x computer today, so I cannot help you test this right now.

Jan

Hello again,

>putting unzipped "Apple Modem Tool 1.5.3", "Serial Tool 1.0.2", and "XMODEM Tool 1.1" in the extension folder

Just to avoid any misunderstanding, I assume that the items placed in the Extensions Folder were the ones resulting from unpacking the .sea (self-expanding archive) intermediate files.

Maybe you could try putting all the remaining tools from the Comm_Toolbox download page in the Extensions Folder in order to see whether this makes a difference.

BTW, you probably noticed that the aforementioned download archive with old shareware/freeware/demo terminal emulation programs contains ZTerm 1.0.1 in a BinHex (.hqx) version (see also the abstracts file).

Jan

Hi Jim,

Basically, you would have to create a new direct/local connection using the same settings as for the PC counterpart (for instance, HyperTerminal). Select the Modem Port on the Mac and COM1 (or another appropriate port) on the PC. 8 data bits, parity none and 1 stop bit would be standard. Hardware handshake is typically the best solution. but you may want/have to test both Xon/Xoff and no flow control. You could test something like 9600 bps speed on both computers to begin with. If successful, try higher speeds. The transfer protocol ZMODEM if possible (otherwise, for example, XMODEM).

Do expect problems. Be prepared to experiment. Setting up a null-modem connection for file transfers can sometimes be very irritating, partly depending on which programs are involved. If you do not know whether the null-modem adapter/cable is OK, you may want to send text (in a terminal mode), perhaps with local echo turned on, as a cable test. Never connect any cables with the computers turned on. Carry out all connections at your own risk.

If it does not work, do try other programs. An Internet search should provide you with more information regarding settings et cetera. See also the Windows help under HyperTerminal and the ZTerm instructions.

Good luck!

Jan