Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Reply-To: From: "Kris Thielemans" To: "Paul Stearns" Cc: "Gnuwin" Subject: RE: b20.2 Problem accessing scsi tape drive on WIndows NT SP5. Date: Mon, 7 Feb 2000 15:02:34 -0000 Message-ID: <001c01bf717c$5d965580$1d4bb392@petnt1.rpms.ac.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_001D_01BF717C.5D965580" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal In-Reply-To: <389DA184.280B628B@compuace.com> ------=_NextPart_000_001D_01BF717C.5D965580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I guess you mean B20.1. As far as I know, the distributed GNU tar does not allow access to tape drives. However, there is a port of GNU tar (called nttar) that works nicely under NT (it doesn't work under Win95, which may be why it's not included in the standard distribution, which is a pity). I can't remember the exact location, but doing an internet search on nttar should help. I did attach the README All the best, Kris > > Whomever: > > I have installed full.exe. The files in the bin directory are data\ed > 12/01/98. I have been unable to access an Archive Python 2550-XXX 4mm > DAT drive. > > Some information about my configuration; > > Windows NT v4.0 SP5 > Dual processor Pentium 200 > 128MB memory > Hard dirves are IDE > Tape controller is Buslogic > > I am a novice with the CYGWIN product. I am somewhat unix proficient. I > have read the FAQs and the online documentation. > > My end goal is to read tar tapes created on a SCO unix 3.2.4.2. > > When I first installed the CYGWIN on this machine and typed the mount > command the only device mounted was C:\ as \. So I decided I needed to > mount > the tape drive. I tried a variety of mount commands. The one I thought > most likely to work was; > > mount -b //./tape0 /dev/st0 > > bash said that /dev/st0 was not a directory. So I tried to create > /dev/st0 using the mkdir commands I was successful in creating /dev, but > it wouldn't work. > > I also tried to tar the tape with the "NT?" device name with the > following command; > > tar -tvf //./tape0 > > When doing this I got a permission denied message. > > I tried finding any problems in by searching the archives and I > downloaded mt.exe version 1.8. When I try the following; > > mt -f \\.\tape0 rewind > > mt says mt: '' is no tape device > > I have tried everything I know I was hoping someone might be able to > help. > > I have inclueded some of the stuff I've tried below. > > Paul > ------=_NextPart_000_001D_01BF717C.5D965580 Content-Type: application/octet-stream; name="readme" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="readme" GNU Tar for NT w/APSI tape extentions (see "NTRMT" below for rmt server) NTTAR =3D=3D=3D=3D=3D This is a port of the GNU-tar 1.11.8 for Windows-NT using the WIN32 tape API. Only nessesary modules are included in this package. It is based on the structure of the port of tar 1.10 with ASPI-support of "chris AT alderan DOT sdata DOT de". I made a little change in tar.c to prevent removing the "/" of the entered pathname. The modules are tested with a HP-SureStore Tape 5000 and Windows-NT 4.0. The devicename of the tape is builded by default with "0" --> "\\.\tape0". Other names can be reached through an environment variable named TAPEID. e.g. TAPEID=3D1 makes "\\.\tape1". Enter tar --help to get full syntax-description of the tar-command. The filename "/dev/ct" specifies the cartridge-tape and "/dev/nrct" specifies the no-rewind-cartridge-tape (no rewind on close). tar -c c:/some/dir - creates the tar-file "tar.out" tar -cf archive.tar c:/some/dir - creates the tar-file "archive.tar" tar -cf /dev/ct c:/some/dir - creates a tar-file on tape and rewinds the tape on close. tar -cf /dev/nrct c:/some/dir - creates a tar-file on the tape and does *not* rewind the tape on = close To append one tar-file to the end of another just use the "/dev/nrct" device. E.g: 1) tar -cf /dev/nrct c:/some/dir 2) tar -cf /dev/ct d:/some/other/dir Multi volume archives are supported by the tape-functions(). So, you may backup your whole disk in one GO to a multi volume tape archive. E.g.: tar -cvMf /dev/ct c:/ d:/ e:/ f:/ writes your c:, d:, e: and f: - drive to the tape archive. You might have noticed the use of "/" instead of "\" to separate dirnames in a pathname. So, don't use the backslash in pathnames, use the normal slash. If you have any suggestions or errors please feel free to send me an e-mail. Markus Barth - mbarth2193 AT aol DOT com barthm AT csb DOT de history: 6/2/97 - Added support of -b parameter to define blocksize So the default blocksize is 20 * 512 and not 512 bytes NTRMT =3D=3D=3D=3D=3D I added an NT service which responds to UNIX tcp rexec "rmt" commands. This allows you to run dumps from your unix (& linux) boxes to your NT tape drives. I also added an "unix like" mt command - some of just can live without "mt rew" and "mt rewoffl"... The rmt server can run as a console application but is intended to run as a service (rmt -d).=20 To install it as a service move the rmt.exe to the place you intended it to stay (c:/winnt/system32 is a fine place) and then run "rmt -i" to install and start it. You can uninstall it later with "rmt -u". The rmt service will show up in the "Services" control panel and will respond to start & stop requests. You should be able to remake from the sources using Visual C 4.2 with "nmake -f rmt.mak". (gnu make will work also). Brad Parker brad AT parker DOT boston DOT ma DOT us 8/23/97 =1A ------=_NextPart_000_001D_01BF717C.5D965580 Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com ------=_NextPart_000_001D_01BF717C.5D965580--