🚀 go-pugleaf

In article <1992Oct29.020138.15875@gagetalker.com> scotty@gagetalker.com  
(Scott Turner) writes:
=>In article <1992Oct26.175847.19255@news.csuohio.edu> tgr@trans.csuohio.edu  
=>(Wayne Hogue) writes:
=>|> I have a NeXTstation Turbo and need help getting this drive to work.
=>|> 
=>|> 1.  What drive number do I need to set the tape drive to?
=>|> 2.  Is there a device I need set up?  Do I need to run mknod? and how?
=>|> 3.  How do I access the drive from Unix?
=>|> 4.  What software is out there to access the drive from NeXTstep?
=>|> 
=>|> Thanks and any info will be very helpful!
=>I would suggest _not_ attaching this drive to your NeXT. The Archive DATs
=>can cause your NeXT to panic (crash,stop suddenly,cease to process.) A bug
=>report has been filed, and for those monitoring the $225 debacle it was done
=>through my dealer, and as yet there is no word from NeXT on a fix etc...
=>

What version is the model number of that DAT drive.  We have an Archive Python  
1G DAT drive which works fine.  It could be that your drive has a bug in the  
firmware or there could be conflicts on the SCSI buss (see below)...

=>The drive will work for small amounts of data, say 200 to 300 megs. But if  
you
=>push too far, your system crashes.
=>

I don't think that such a generalized statement is safe to make.  We  
consistantly run two tapes a night backing up 3 partitions (1.7G total).  One  
partition alone is 994570K and it is usually around 98% full.  We have not had  
any problem with panics when backing up a Gig of data.

=>The above doesn't apply if you're using it under 2.1 (which implies you are
=>using non-turbo hardware.) The behaviour exists on 2.2, 2.2A 3.0pr2 and  
3.0pr3
=>(otherwise known as the "release" version of 3.0.)
=>

We are running 3.0-Gold (NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992;  
root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K) and never had had a problem.  We  
also were running the same setup on NS2.1 and NS2.2 without any problems.

We did encounter a problem once with a conflict between our Gig drive and the  
DAT.  Sometimes during a dump we would get media errors which resulted from  
timming problems.  It turns out that the drives have SCSI problems and the DAT  
is fine (we also tested an Exabyte with identical results)...

=>Anyway, I use   ID 6. It shows up as /dev/nrst0 and /dev/rst0 (assuming you
=>have no other SCSI tape drives) and you can use tar and dump to put data
=>on the tape (see man pages for more details.) For NeXTSTEP there are things
=>like EnTAR available.
=>
=>Scotty

My DAT resides on SCSI address 3.  It seems very content with that ID...

--
Paul S. Sears                *  sears@uh.edu (NeXT Mail OK)
The University of Houston    *  suggestions@tree.egr.uh.edu (NeXT
Engineering Computing Center *  comments, complaints, questions)
NeXT System Administration   *  DoD#1967 '83 NightHawk 650SC 
          >>> SSI Diving Certification #755020059 <<<
"Programming is like sex: One mistake and you support it a lifetime."