Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!bsu-cs!dhesi From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi) Newsgroups: comp.sys.ibm.pc Subject: Re: ZIP file transfer util. posted to C.B.I.P / Problems Summary: Things to try Message-ID: <8134@bsu-cs.bsu.edu> Date: 7 Jul 89 17:04:10 GMT References: <14963@watdragon.waterloo.edu> Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi) Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 29 In article <14963@watdragon.waterloo.edu> mdharding@trillium.waterloo.edu (Matthew D. Harding) reports problems getting Zip, the 115 Kbps file transfer utility, to work. It works for me. Here are some possibilities and how to test for them. 1. Cable: Is your null modem cable really working? Try this: Run MS-Kermit on both machines, put one end in host mode, and see if you can do Kermit transfers. If not, you may have cable problems. 2. Interrupts: If Kermit transfers work, but Zip doesn't, it means the high data rate may be the problem. Remove ALL extraneous software, even things (like PRINT.COM, RAMdisks, keyboard enhancers, etc.) that don't seem likely to affect serial port I/O. Many of these utilities disable interrupts for too long. 3. Cable capacitance: How long is your cable? If it's more than about five feet, it is possible that shortening it will help. The longer the cable the mushier signals become as they travel along it, and at 115 Kbps that could make all the difference. If you are using a shielded cable, try using *unshielded* ribbon cable. 4. Alternative: Do you have Borland's Turbo Debugger? If so, try using the high-speed file transfer utility (TDREMOTE and TDRF) that comes with it. It can be told to use an intermediate data rate rather than 115 Kbps and might work for you. -- Rahul Dhesi UUCP: ...!{iuvax,pur-ee}!bsu-cs!dhesi