anderson@macc.wisc.edu (Jess Anderson) (06/07/91)
The problem, as stated: >One of our users wants to move quite a few files (~400 MB) >from a DOS machine (AT compatible) to his NeXT (he has, get >this, *two* 1.2GB disks on the NeXT!). What he's thinking >of doing is connecting the two machines together with a >proper NeXT modem cable to a null modem to the DOS machine's >serial port. >He's prepared for it to take a while, I guess. >I would think borrowing an ethernet card for the DOS side >would be much better, but let's assume he can't swing that. >Is the serial-to-serial thing likely to work? The responses, summarized (and much edited), with our thanks. --- From: jland@casbah.acns.nwu.edu It is very easy to connect an IBM to a NeXT using serial cables (IF YOU HAVE THE PROPER WIRING DIAGRAM). I am able to transfer files back and forth using zmodem at 19,200 baud What I use: Telix 3.12 for the IBM configured at 19200, E71, the cable, and the public domain zmodem program on the NeXT. Basically, I turn on my IBM and get the localhost login prompt on the screen, enter the username, password, and get a shell. Then I use rz and sz from the zmodem program to send files back and forth. This method is cheap! I spent $30 only because I got connectors that use modular cable between the ends. Let me know if you need the pin-outs. --- From: Jerry Whelan <guru@buhub.bradley.edu> Make sure he uses something smart like zmodem which can transfer whole directory trees. --- From: rao@ece.UCSD.edu I went through a similar process at home recently - no ethernet there. I got a null-modem cable. It is easier to obtain this than a modem cable that supports hardware flow control. Anyways, I fired up kermit on my PC, logged on, fired up kermit on the NeXT and moved all my files. --- From: lee@cs.wisc.edu Did you say ~400MB? I'd rather not do it! I'd prefer to use 1.44MB HDs. IBM DOS allows upto 9600 baud rate on serial ports, COM1 and COM2 physically (of course you may use extra COM3 and COM4 with 3rd party HW). Now, using 9600 baud setup, you can send 9600/(10 or 11) = ~900 byte/sec. Then think about total time to transfer files, 400,000,000/900 = ~500,000 sec = ~15Hrs! [oops! more like 124 hrs or 5.1 days]] Of course if you use Kermit, it will take more than 15Hrs! --- From: gchunt%chinle@cs.utah.edu Its not going to work in this lifetime. He would be ahead just to buy a cheap ethernet card for $200 and using FTP to move everything. 10mbs is a lot better than 9600baud. --- From: nigelm@ohm.york.ac.UK I see no problem here at all - I've done a very similar thing moving stuff from a very old unix system to some apollos _via_ a PC!!! Get MS-Kermit latest version (3.1) - from the columbia archives. With that is a utilitiy program called something like XSEND (stored in the archives as MSIXSE.*) which sends complete directory trees across. You also need the C-Kermit running on a NeXT that has been mentioned many times on this group. Unless all the files are text do all transfers in binary mode - you may need to take the additional carriage returns out of the files later, but you are stuck with this unless you want to individually tag all text & inary files! Make sure both kermits are running with long packets and full checksumming - the .kermrc file for the NeXT should include something like this:- set block 3 set send packet-length 500 set receive packet-length 500 MS-Kermit should have similar protocols set up. (I always use 500 byte packets, although they can be longer, cos it seems like the best compromise between throughput and retransmission overhead). If the NeXT kermit has a windowing protocol enable that on both ends (haven't used that version, so not sure about this). Set the baud rate pretty high - 19200 should be OK. Get kermit running on the NeXT in server mode in the top directory of the area you want the data to end up in. Get MS-Kermit fired up and use XSEND to produce the script to send all the files in the directory tree. Run that script through kermit. Go away (well watch for the first 10 minutes - if its OK leave it). Come back after the weekend!!!! (I reckon 60 hours for 19200 baud). If you wanted to be flash you could try using zoo to compress directories before transferring them..... --- From: bill@pslu1.psl.wisc.edu It is likely to work. It will be easiest if the PC does hardware flow and can run at 19200. I would recommend getting a copy of teh type of xmodem where you can set the block size to larger than 1K, because a short serial cable is usualy reliable. --- From: eps@toaster.SFSU.EDU (Eric P. Scott) Approximately 32 hours assuming that you can actually sustain 38.4Kb and absolutely nothing goes wrong. (What are the chances of THAT?) With Ethernet, the limiting factor will be the PC's performance; even an '030 cube is way faster than what an AT-bus (ISA) machine can push at it. -- Jess Anderson <> Madison Academic Computing Center <> University of Wisconsin Internet: anderson@macc.wisc.edu <-best, UUCP:{}!uwvax!macc.wisc.edu!anderson NeXTmail w/attachments: anderson@yak.macc.wisc.edu Bitnet: anderson@wiscmacc Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888