Sponsored Content
Operating Systems SCO SCO Openserver Release 5 and HP VS160 Tape Drive Post 302189026 by jfd7000 on Thursday 24th of April 2008 07:31:03 PM
Old 04-24-2008
SCO Openserver Release 5 and HP VS160 Tape Drive

Hi,

Does anyone know if a HP VS160 Tape drive will work with SCO Openserver Release 5?

If so what driver would it use? alad, cha?

Thanks

John
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Magneto-Optical drive for SCO Openserver 5.0.5

Hi, I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160). During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
Discussion started by: yurist
2 Replies

2. UNIX for Advanced & Expert Users

Sco Unix OpenServer Release 3.0

hi everybody I have got a set of sco unix open server release 3.0 flopyy disks series N1, N2, M1, P1...P43, Release notes.. ý did a fresh installation. but ý cant install ethernet card. when ý use netconfig-ad a chain -tcpip... there is a messge : the sco contain TCP/IP driver. and ý... (2 Replies)
Discussion started by: kaygusuz
2 Replies

3. UNIX for Advanced & Expert Users

Tape Drive SCO 5.0.7

Hi guys I had a system running 5.0.6 , we upgraded it to 5.0.7 everything was fine till i try to do a test backup. The error was cannot open (cannot open /dev/xct0 no such file or directory)what i did was, removed the tape , reboot the system and the try to install it again, but its... (2 Replies)
Discussion started by: josramon
2 Replies

4. UNIX for Dummies Questions & Answers

second tape drive on SCO 505

I need to run a back up that will take more than one tape. What is the command that will continue the back up on to a second tape drive. the first is /dev/rStp0 second is /dev/rStp1. Anyone? (1 Reply)
Discussion started by: franruiz
1 Replies

5. SCO

Tape drive issues with SCO 5.0.5!!!

Hi Don't know if anyone will be able to help, but we're currently having problems with our external tape drive on our SCO server. If I try the following command for instance, "tar cvf /dev/rStp0", the tape drive jumps into action for a while, then comes back with the error "tar: cannot open:... (3 Replies)
Discussion started by: mattingg
3 Replies

6. UNIX for Dummies Questions & Answers

SCO 5.0.5 Tape Drive errors

hi guys, I.m trying to remove and add a new tape drive by using the mkdev tape command and when i try to update the Kernel this is what i'm getting, i386ld: Symbol Sdsk_no_tag in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/blad/s pace.o is multiply defined. First defined in... (0 Replies)
Discussion started by: josramon
0 Replies

7. SCO

Configuring Tape in SCO OPENSERVER 5

Hello All, I m new in SCO.Please any one help me regarding configuring HP TapeDrive in SCO OPENSERVER5. (1 Reply)
Discussion started by: ather_36
1 Replies

8. SCO

Tandberg Tape SLR70 on SCO Openserver 6.0

Hello, I've a Dell computer Poweredge 1800 with a Perc DC4 Dual channel raid controller :D . The whole computer is SCSI based . I've installed the whole system (SCO 6.0, maintenance package 2.0, and our Openbasic software and all printers). Everything works, even my remote printers. But I've... (2 Replies)
Discussion started by: frederik1
2 Replies

9. SCO

how to access data in a pen drive in sco openserver 6

Does anybody know the commands to access the data from a pen drive in a SCO Openserver 6. What are the parameters to the mount command for accessing the USB port:confused: (9 Replies)
Discussion started by: jksah
9 Replies

10. SCO

SCO 5.0.7 Tape Drive swap

Our tape drive died and I installed a newer Quantum DAT72 drive in it's place with the same SCSI ID. It still works, but with one major flaw, the system will lock up if I try to upgrade BackupEDGE or view NFS settings in scoadmin. I get a Transition to ready failure on ha=0* message when the... (4 Replies)
Discussion started by: psytropic
4 Replies
CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME
cd -- CDROM driver for the CAM SCSI subsystem DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com- mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags. QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver. The following is a list of quirks that the driver recognize. CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what size it is. This flag is currently unimplemented in the CAM cd driver. CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag. CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with multiple luns that are not a part of a changer. CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto- matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial read capacity command for LUN 0 of the changer through the changer scheduling code. CD_Q_10_BYTE_ONLY This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam- ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6 byte commands. FILES
/sys/cam/scsi/scsi_cd.c is the driver source file. SEE ALSO
cd(4), scsi(4) HISTORY
The cd manual page first appeared in FreeBSD 2.2. AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry <ken@FreeBSD.org>. BSD
September 2, 2003 BSD
All times are GMT -4. The time now is 07:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy