root@krishna.info-gw.mese.com (Sarat Vemuri) writes:The two major ones I know about are: 1. Connect to and use the floppy disk controller. This usually does more than just use it as a data path, it actually makes use of the controller functionality to run the tape drive. I believe the standard for this is QIC-02 (I can't find my copy at the moment) and there are rumored to be a few that do not follow this standard. I personally would not try to use this means of connection. Your mileage may vary. 2. Connect to the parallel port. This is difficult because the parallel port was intended for printing and is not a truly bidirectional interface and is reported to be unreliable in certain cases as well. In order to accomplish bidirectionality and improved reliability, some sneaky designs have come up. These may be using tricks like toggling available status lines and such to achieve a data flow. The problem is that all this does take some level of work to develop and test, and the companies do not want to let their competitors see what they have done. However with half a dozen such companies on the market, it seems moot to me, even if all the designs are different. I'd prefer some kind of connection that at least CAN be external, and the parallel port would be nice since it is about all you have besides the serial port for laptops. My tendency, given this situation, is to go with SCSI. You can get more variety in backup software even for DOS this way. QIC-40 and QIC-80 are formats that define the range from low level block definitions, to upper level file system representation. QIC-150 and QIC-525 define low level block definitions. I didn't see and high level for QIC-525 but someone did tell me it had it (maybe we just didn't have a common understanding of what was low level and what was high level). QIC-02 is the interface via a floppy controller. It would tell you what floppy disk operations to perform to do things on the tape. QIC-40/80 define a lot of things, from how many tracks on tape, which ones are data or sync, data transition timings required, syncronization and lead in patterns for blocks, the order of tracks on the tape (odd tracks forward, even tracks backward, for instance). These things could or should be done by the tape control firmware. This is not always the case. It also defines how to lay out the filesystem on tape, such as where the file name goes, where the date and size of the file goes, how to write the data from the file, etc. This is almost always done by the software. QIC-150 and QIC-525 define the low level stuff only. On UNIX you should end up with a stream device in /dev to which you can output directly with your own programs. You can use tar or cpio or make up whatever you want as a format. You can compress the data before being written, too. There is NO non-SCSI solution that is ideal. You will have to detail your particular needs. Well even SCSI is not ideal (until they make a SCSI interface standard on all laptops). I cannot currently recommend parallel port drives, and I would not recommend floppy disk controller drives. I've heard there are tape drives for Ethernet, but this is likely to be at least as costly as SCSI. I'd recommend getting SCSI and a QIC-150 (using DC6250 tapes you get 250 megabytes of basic capacity (500 megabytes if you data can be compressed to the 2:1 level)). In the longer run this might be a better choice than QIC-40/80. But if exchanging data with DOS machines is more important to you than exchanging with UNIX machines, then maybe some QIC-80 drive would be preferred (please disregard QIC-40). -- | Phil Howard, pdh@netcom.com, KA9WGN Spell protection? "1(911)A1" | | Right wing conservative capitalists are out to separate you from your MONEY | | Left wing liberal do gooders are out to separate you from EVERYTHING ELSE!! | +-----------------------------------------------------------------------------+
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Jeff Garzik | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Chodorenko Michail | PROBLEM: Celeron Core |
git: | |
| Linus Torvalds | People unaware of the importance of "git gc"? |
| Johannes Schindelin | Re: Empty directories... |
| Jakub Narebski | Re: VCS comparison table |
| Sam Song | Re: Fwd: [OT] Re: Git via a proxy server? |
| J.W. Zondag | Dell PE1950 III - Perc 6i |
| Richard Stallman | Real men don't attack straw men |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Anselm R. Garbe | OpenBSD 4.0 / Xorg -> vesa 1920x1200 widescreen resolution |
| Jim Winstead Jr. | Re: Root Disk/Book Disk Compatibility |
| Anselm Lingnau | File creation date in UNIX (was: Re: VMS) |
| Rafal Kustra (summer student) | mount |
| Nicholas Yue | Re: more on 486/33 weirdness |
