Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!asuvax!mcdphx!phx.mcd.mot.com!teroach!dbk From: teroach!dbk@phx.mcd.mot.com (Dave Kinzer) Newsgroups: comp.sys.amiga.hardware Subject: Tape drive on 2090a, help needed. Summary: Can't mount tape device from BTN TAPE Keywords: TAPE SCSI BTN 2090A Message-ID: <15028@mcdphx.phx.mcd.mot.com> Date: 20 Jun 91 16:33:34 GMT Sender: listen@mcdphx.phx.mcd.mot.com Reply-To: teroach!dbk@phx.mcd.mot.com (Dave Kinzer) Organization: Motorola Analog Integrated Circuits Division Lines: 67 I originally posted this to comp.sys.amiga.programmer, but have not had any sucess in solving this yet. What I need is for someone who has a 2090a controller to use XOPER (or similar) and look up the device version for hddisk.device to see if a newer one has been issued. Please note that for BTN Tape on a 2090a, a unit number of 7 means scsi ID 4 (Units 1 and 2 are the ST506 Drives). Begin old message: Help!!! :^) I am trying to get BTN tape to work on my system. The system will hang (completely) when I try to mount the TAPE: device, requiring three finger salute to recover. No LED Flashing or GURU. Hardware: A2000 A2630 (enabled/disabled, no difference) 8Meg memory board, 4 meg installed A2090A (hard disk is ST506 type) Archive 2150 Viper, strapped address 4, (parity on/off no difference), 16K disconnect Software: BTN Tape 2.0 1.3 software: Kick V34.5 WB V34.28 hddisk.device V34.4 No ARP software, Mount command from 1.3.2 release. /* Tape mountlist. */ TAPE: Handler = L:tape-handler Startup = "hddisk.device/UN-7/BS-512/NB-16/C9-1" Stacksize = 4000 Priority = 5 /* use 11 for Supra 4x4 */ GlobVec = -1 Mount = 1 # Symptoms include: 1. System locks up shortly (2 sec in 68000 mode) after typing Mount TAPE:. 2. If I place a tape in the drive before typing above, tape drive resets (tape is driven to BOT) when I try to mount it, then system hangs. This indicates that the SCSI ID is correct, since it talks to the drive. 3. Does not lock up if I change unit number in mountlist to 8, but dos requester for "TAPE:" comes up. (i.e. SCSI device being addressed never comes ready.) Since there is no SCSI device at address 5, this indicates the software only locks up if it actually talks to a device. Does anyone see anything obviously wrong with the above? This seemed to be a simple excercise but it just won't go. If anyone has a 2090A working I would appreciate you checking the version number (I used xoper since it resides on rom) of the hddisk.device, I have a very early 2090A and suspect that this might be the problem. Thank you. * * * Imminent use of deathnet predicted. * * * // Dave Kinzer (602)897-3085 asuvax!mcdphx!teroach!dbk Opinions are mine. \X/