[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

628.0. "TK50 via SCSI no longer working on 7.1" by UTRTSC::DORLAND (The Wizard of Odz2) Thu May 22 1997 10:57

    
    	Hello,
    
    	I have a Alpha station 200 4/100 which has an external
    	SCSI port. On this port a TK50 is connected.
    	After upgrading to VMS 7.1, the drive is no longer
    	accessible. When trying to INIT a tape, the drive starts 
    	moving, than hangs. Usually your process hangs or you'll
    	get a SYSTEM-F_MEDOFL error. 
    
    	Just for a proof, I rebooted the system with the 7.0 and 7.1
    	distribution CD; on VMS 7.0 INIT and MOUNT work, on 7.1 not.
    
    	However I cannot find any restrictionmentioned in the release
    	notes. There is only one remark bearing to EXABYTE tapes on VAX
    	7.1. The only other pointer I have found is an IPMT case 
    	with a TLZ04 showing more or less the same problem.
    
    	My guess is that this is a bug or restriction somewhere in the
    	MK or PK driver.
    
    	Can anyone confirm this ?
    
    	Thanks in advance,
    
    	Ton Dorland
T.RTitleUserPersonal
Name
DateLines
628.1UTRTSC::jgoras-197-2-3.jgo.dec.com::JurVanDerBurgChange mode to Panic!Thu May 22 1997 11:038
Ton,

The TK50 has never been supported on Alpha. If it worked, fine.

Having said that, we may check out what's really wrong if i find some time.

Jur.

628.2LEFTY::CWILLIAMSCD or not CD, that's the questionThu May 22 1997 12:2811
    THe TK50Z was -barely- SCSI-1 functionality. It was cleaned up a little
    when it started shipping on VS3100's, but it is unlikely that it can
    handle a lot of the newer protocol being used, as it did not exist when
    the drive was designed.
    
    We don't have the code, and can't fix the drive, regardless...
    
    Time for a supported drive, I'm afraid.
    
    Chris