Jay wrote: Does that software do some magic that can't be done with cat, cp, or dd? On the PDP-1 project, we're using a DSI Reader/Punch on loan from Al Kossow. I think it's an NC2400, but I'm not sure. Anyhow, to read a tape, I use a script that does an stty on the serial port to put it in raw mode, RTS/CTS flow control, and 2400 bps, then just does a "cat /dev/ttyS0 >somefile.bin". I start the tape, then hit control-C when it's done reading. To write a tape back out, I use another script that does the same stty but at 300 bps, then does a "cat somefile.bin >/dev/ttyS0". If I want extra leader or trailer, a "dd if=/dev/zero of=/dev/ttyS0 bs=1 count=120" or the like can be put in the script. I had to use 300 bps for punching because it appears that the Linux serial driver doesn't respond quickly enough to CTS to avoid dropped bytes :-( It works fine at 300 bps, though. [*] I'm sure this is nowhere near as fancy as whatever wncedit does, but it seems to work for me. Is the Facit N4000 so "smart" that it needs more hand-holding or something? Eric [*] Back when I worked at Telebit, we made sure that our products dropped RTS or CTS (depending on which side we were on) well before we ran out of buffer room, because there are *MANY* devices and computers out there that can't quickly respond to RTS or CTS being dropped, and will still send a bunch more bytes. And we also made sure that our own products *would* respond to RTS or CTS being dropped within two character times. But the NC-2400 apparently is not willing to buffer a few extra bytes that dribble in after it drops CTS. :-(