Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter - SUN

This is a discussion on Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter - SUN ; Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older Sparc 10 machine. I bought one of these on Ebay and I seem be be having a difficult time ...

+ Reply to Thread
Results 1 to 14 of 14

Thread: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

  1. Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    a difficult time getting it to work.

  2. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak wrote:
    > Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    > (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    > Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    > a difficult time getting it to work.


    I don't know that I've seen sbus incompatibilies between hardware. More
    common is that there's no driver in the OS for the card.

    What OS are you running on the machine? If Solaris, what do you see in
    'prtdiag' output?

    --
    Darren Dunham ddunham@taos.com
    Senior Technical Consultant TAOS http://www.taos.com/
    Got some Dr Pepper? San Francisco, CA bay area
    < This line left intentionally blank to confuse you. >

  3. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Darren Dunham wrote:

    > Kurt Nowak wrote:
    > > Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    > > (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    > > Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    > > a difficult time getting it to work.

    >
    > I don't know that I've seen sbus incompatibilies between hardware. More
    > common is that there's no driver in the OS for the card.
    >
    > What OS are you running on the machine? If Solaris, what do you see in
    > 'prtdiag' output?
    >
    > --
    > Darren Dunham ddunham@taos.com
    > Senior Technical Consultant TAOS http://www.taos.com/
    > Got some Dr Pepper? San Francisco, CA bay area
    > < This line left intentionally blank to confuse you. >


    Im running Solaris 8. I think you mean prtconf? Here is the verbose output
    of prtconf and also cfgadm after that. c4 is the controller in question.

    stanford% prtconf -v
    System Configuration: Sun Microsystems sun4m
    Memory size: 224 Megabytes
    System Peripherals (Software Nodes):

    SUNW,SPARCstation-10
    System properties:
    name length <4>
    value <0x00000003>.
    name length <4>
    value <0x00000001>.
    name length <4>
    value <0x00000fff>.
    name length <4>
    value <0x00001000>.
    name length <4>
    value <0x00001000>.
    packages (driver not attached)
    disk-label (driver not attached)
    deblocker (driver not attached)
    obp-tftp (driver not attached)
    options, instance #0
    System properties:
    name length <36>
    value
    <0x0000250200001805000000bd00008a3b031c7f1504000000 11131a19120f171600000000>.

    name length <5>
    value 'root'
    aliases (driver not attached)
    openprom (driver not attached)
    iommu, instance #0
    Driver properties:
    name length <18>
    value 'no-suspend-resume'
    Register Specifications:
    Bus Type=0xf, Address=0xe0000000, Size=0x300
    sbus, instance #0
    Register Specifications:
    Bus Type=0xf, Address=0xe0001000, Size=0x20
    Range Specifications:
    Ch: 00,00000000 Pa: 0e,00000000, Sz: 10000000
    Ch: 01,00000000 Pa: 0e,10000000, Sz: 10000000
    Ch: 02,00000000 Pa: 0e,20000000, Sz: 10000000
    Ch: 03,00000000 Pa: 0e,30000000, Sz: 10000000
    Ch: 0f,00000000 Pa: 0e,f0000000, Sz: 10000000
    espdma, instance #0
    Register Specifications:
    Bus Type=0xf, Address=0x400000, Size=0x10
    esp, instance #0
    Driver properties:
    name length <4>
    value <0x0000115d>.
    name length <4>
    value <0x00002710>.
    name length <4>
    value <0x00002710>.
    name length <4>
    value <0x00002710>.
    name length <4>
    value <0x00002710>.
    name length <0> -- .
    name length <0> -- .
    name length <0> -- .
    name length <0> -- .
    name length <4>
    value <0x000000fa>.
    name length <4>
    value <0x00001ff8>.
    name length <4>
    value <0x0000000a>.
    name length <4>
    value <0x00000002>.
    name length <4>
    value <0x00000bb8>.
    Register Specifications:
    Bus Type=0xf, Address=0x800000, Size=0x40
    Interrupt Specifications:
    Interrupt Priority=0x24 (ipl 4)
    sd (driver not attached)
    st (driver not attached)
    sd, instance #0
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000000>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    Driver properties:
    name length <5>
    value '3636'
    name length <8>
    value 'DFHSS4F'
    name length <8>
    value 'IBM OEM'
    name length <21>
    value 'needs-suspend-resume'
    name length <0> -- value>.
    sd, instance #1
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000001>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    Driver properties:
    name length <5>
    value '3636'
    name length <8>
    value 'DFHSS4F'
    name length <8>
    value 'IBM OEM'
    name length <21>
    value 'needs-suspend-resume'
    name length <0> -- value>.
    sd, instance #2
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000002>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    Driver properties:
    name length <5>
    value '3636'
    name length <8>
    value 'DFHSS4F'
    name length <8>
    value 'IBM OEM'
    name length <21>
    value 'needs-suspend-resume'
    name length <0> -- value>.
    sd, instance #3
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000003>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    Driver properties:
    name length <5>
    value '0F0C'
    name length <16>
    value 'FIREBALL ST4.3S'
    name length <8>
    value 'QUANTUM'
    name length <21>
    value 'needs-suspend-resume'
    name length <0> -- value>.
    sd, instance #4 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000004>.
    name length <5>
    value 'scsi'
    sd, instance #5 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000005>.
    name length <5>
    value 'scsi'
    sd, instance #6
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000006>.
    name length <5>
    value 'scsi'
    Driver properties:
    name length <5>
    value '0494'
    name length <17>
    value 'XM-4101TASUNSLCD'
    name length <8>
    value 'TOSHIBA'
    name length <0> -- .

    name length <30>
    value 'NAME=spindle-motor' + '0=off' +
    '1=on'
    name length <21>
    value 'needs-suspend-resume'
    name length <0> -- value>.
    ledma, instance #0
    Driver properties:
    name length <4>
    value <0xf5d52a80>.
    Register Specifications:
    Bus Type=0xf, Address=0x400010, Size=0x20
    le, instance #0
    Register Specifications:
    Bus Type=0xf, Address=0xc00000, Size=0x4
    Interrupt Specifications:
    Interrupt Priority=0x26 (ipl 6)
    SUNW,bpp, instance #0 (driver not attached)
    SUNW,DBRIe, instance #0 (driver not attached)
    mmcodec (driver not attached)
    cgsix, instance #1
    Register Specifications:
    Bus Type=0x0, Address=0x0, Size=0x1000000
    Interrupt Specifications:
    Interrupt Priority=0x39 (ipl 9)
    QLGC,isp, instance #1
    Driver properties:
    name length <4>
    value <0x000000fa>.
    name length <4>
    value <0x00001ff8>.
    name length <4>
    value <0x0000000a>.
    name length <4>
    value <0x00000002>.
    name length <4>
    value <0x00000bb8>.
    Register Specifications:
    Bus Type=0x1, Address=0x10000, Size=0x450
    Interrupt Specifications:
    Interrupt Priority=0x35 (ipl 5)
    sd (driver not attached)
    st (driver not attached)
    sd, instance #36 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000000>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #37 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000001>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #38 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000002>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #39 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000003>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #40 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000004>.
    name length <5>
    value 'scsi'
    sd, instance #41 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000005>.
    name length <5>
    value 'scsi'
    sd, instance #42 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000006>.
    name length <5>
    value 'scsi'
    sd, instance #43 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000008>.
    name length <5>
    value 'scsi'
    sd, instance #44 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000009>.
    name length <5>
    value 'scsi'
    sd, instance #45 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000a>.
    name length <5>
    value 'scsi'
    sd, instance #46 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000b>.
    name length <5>
    value 'scsi'
    sd, instance #47 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000c>.
    name length <5>
    value 'scsi'
    sd, instance #48 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000d>.
    name length <5>
    value 'scsi'
    sd, instance #49 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000e>.
    name length <5>
    value 'scsi'
    sd, instance #50 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x0000000f>.
    name length <5>
    value 'scsi'
    dma, instance #1
    Register Specifications:
    Bus Type=0x2, Address=0x100000, Size=0x10
    esp, instance #1
    Driver properties:
    name length <4>
    value <0x000000fa>.
    name length <4>
    value <0x00001ff8>.
    name length <4>
    value <0x0000000a>.
    name length <4>
    value <0x00000002>.
    name length <4>
    value <0x00000bb8>.
    Register Specifications:
    Bus Type=0x2, Address=0x200000, Size=0x40
    Interrupt Specifications:
    Interrupt Priority=0x35 (ipl 5)
    sd (driver not attached)
    st (driver not attached)
    sd, instance #7 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000000>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #8 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000001>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #9 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000002>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #10 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000003>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #11 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000004>.
    name length <5>
    value 'scsi'
    sd, instance #12 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000005>.
    name length <5>
    value 'scsi'
    sd, instance #13 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000006>.
    name length <5>
    value 'scsi'
    dma, instance #2
    Register Specifications:
    Bus Type=0x3, Address=0x81000, Size=0x10
    esp, instance #2
    Driver properties:
    name length <4>
    value <0x000000fa>.
    name length <4>
    value <0x00001ff8>.
    name length <4>
    value <0x0000000a>.
    name length <4>
    value <0x00000002>.
    name length <4>
    value <0x00000bb8>.
    Register Specifications:
    Bus Type=0x3, Address=0x80000, Size=0x40
    Interrupt Specifications:
    Interrupt Priority=0x35 (ipl 5)
    sd (driver not attached)
    st (driver not attached)
    sd, instance #14 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000000>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #15 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000001>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #16 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000002>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #17 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000003>.
    name length <6>
    value 'atapi'
    name length <5>
    value 'scsi'
    sd, instance #18 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000004>.
    name length <5>
    value 'scsi'
    sd, instance #19 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000005>.
    name length <5>
    value 'scsi'
    sd, instance #20 (driver not attached)
    System properties:
    name length <4>
    value <0x00000000>.
    name length <4>
    value <0x00000006>.
    name length <5>
    value 'scsi'
    lebuffer, instance #0
    Driver properties:
    name length <4>
    value <0xf5d52a60>.
    Register Specifications:
    Bus Type=0x3, Address=0x40000, Size=0x20000
    le, instance #1
    Register Specifications:
    Bus Type=0x3, Address=0x60000, Size=0x4
    Interrupt Specifications:
    Interrupt Priority=0x37 (ipl 7)
    obio, instance #0
    Range Specifications:
    Ch: 00,00000000 Pa: 0f,f1000000, Sz: 1000000
    Ch: 01,00000000 Pa: 00,90000000, Sz: 4000000
    Ch: 02,00000000 Pa: 00,94000000, Sz: 4000000
    Ch: 03,00000000 Pa: 00,f0000000, Sz: 4000000
    Ch: 04,00000000 Pa: 00,f4000000, Sz: 4000000
    zs, instance #0
    Register Specifications:
    Bus Type=0x0, Address=0x100000, Size=0x8
    Interrupt Specifications:
    Interrupt Priority=0x2c (ipl 12)
    zs, instance #1
    Register Specifications:
    Bus Type=0x0, Address=0x0, Size=0x8
    Interrupt Specifications:
    Interrupt Priority=0x2c (ipl 12)
    eeprom (driver not attached)
    counter (driver not attached)
    interrupt (driver not attached)
    SUNW,fdtwo, instance #0
    Driver properties:
    name length <0> -- .
    name length <30>
    value 'NAME=spindle-motor' + '0=off' + '1=on'
    Register Specifications:
    Bus Type=0x0, Address=0x700000, Size=0x8
    Interrupt Specifications:
    Interrupt Priority=0x2b (ipl 11)
    auxio (driver not attached)
    power (driver not attached)
    memory (driver not attached)
    virtual-memory (driver not attached)
    eccmemctl (driver not attached)
    TI,TMS390Z55 (driver not attached)
    TI,TMS390Z55 (driver not attached)
    pseudo, instance #0
    System properties:
    name length <5>
    value 'root'
    stanford%

    stanford% cfgadm -al
    Ap_Id Type Receptacle Occupant
    Condition
    c0 scsi-bus connected configured
    unknown
    c0::dsk/c0t0d0 disk connected configured
    unknown
    c0::dsk/c0t1d0 disk connected configured
    unknown
    c0::dsk/c0t2d0 disk connected configured
    unknown
    c0::dsk/c0t3d0 disk connected configured
    unknown
    c0::dsk/c0t6d0 CD-ROM connected configured
    unknown
    c1 scsi-bus connected unconfigured
    unknown
    c2 scsi-bus connected unconfigured
    unknown
    c4 scsi-bus connected unconfigured
    unknown
    stanford%


  4. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    According to Kurt Nowak :
    > Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    > (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    > Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    > a difficult time getting it to work.


    What are you trying to talk to with it? The SBus differential
    cards are HVD (High Voltage Differential), not the more recent LVD (Low
    Voltage Differential) which will also talk to single-ended SCSI.

    Things like the A1000 and D1000 want HVD to talk to them. Many
    other things want LVD, and unfortunately, there does not seem to be a
    LVD card for the SBus. (This is what moved me from an Ultra-2 to an
    Ultra-60 -- to be able to use PCI cards so I could get a LVD card to
    talk to an Exabyte EXB-430 tape library.

    This difference could be the source of your difficulties.

    Good Luck,
    DoN.
    --
    Email: | Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

  5. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    DoN. Nichols wrote:
    > According to Kurt Nowak :
    >> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >> a difficult time getting it to work.

    >
    > What are you trying to talk to with it? The SBus differential
    > cards are HVD (High Voltage Differential), not the more recent LVD (Low
    > Voltage Differential) which will also talk to single-ended SCSI.
    >
    > Things like the A1000 and D1000 want HVD to talk to them. Many
    > other things want LVD, and unfortunately, there does not seem to be a
    > LVD card for the SBus. (This is what moved me from an Ultra-2 to an
    > Ultra-60 -- to be able to use PCI cards so I could get a LVD card to
    > talk to an Exabyte EXB-430 tape library.
    >
    > This difference could be the source of your difficulties.
    >
    > Good Luck,
    > DoN.


    I am trying to talk to a DDS-4 tape drive.

  6. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak wrote:
    > DoN. Nichols wrote:
    >> According to Kurt Nowak :
    >>> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >>> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >>> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >>> a difficult time getting it to work.

    >>
    >> What are you trying to talk to with it? The SBus differential
    >> cards are HVD (High Voltage Differential), not the more recent LVD (Low
    >> Voltage Differential) which will also talk to single-ended SCSI.
    >>
    >> Things like the A1000 and D1000 want HVD to talk to them. Many
    >> other things want LVD, and unfortunately, there does not seem to be a
    >> LVD card for the SBus. (This is what moved me from an Ultra-2 to an
    >> Ultra-60 -- to be able to use PCI cards so I could get a LVD card to
    >> talk to an Exabyte EXB-430 tape library.
    >>
    >> This difference could be the source of your difficulties.
    >>
    >> Good Luck,
    >> DoN.

    >
    > I am trying to talk to a DDS-4 tape drive.


    The SCSI card you have is a High Voltage Differential (HVD) card - *not*
    to be confused with LVD, which is what most DDS-4 tape drives are. I've
    never seen a DDS-4 tape drive that can use HVD, so it is not surprising
    they are not working.

    Also be aware that there is a risk of damage when connecting HVD to LVD
    or single ended.

    A SPARC 10 may not be able to send data to a DDS-4 tape drive at
    sufficient rate to keep the drive writing all the time (steaming). That
    would cause the drive to stop/start repeatedly and wear it out.




  7. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Darren Dunham wrote:
    >
    > I don't know that I've seen sbus incompatibilies between hardware. More
    > common is that there's no driver in the OS for the card.


    Actually, there may be incompatibilies between sun4c and newer
    machines, but the SS10 is sun4m and counts as "new".

    Dennis

    --
    Don't suffer from insanity...
    Enjoy every minute of it.

  8. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak writes:
    >DoN. Nichols wrote:
    >> According to Kurt Nowak :
    >>> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >>> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >>> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >>> a difficult time getting it to work.

    >>
    >> What are you trying to talk to with it? The SBus differential
    >> cards are HVD (High Voltage Differential), not the more recent LVD (Low
    >> Voltage Differential) which will also talk to single-ended SCSI.
    >>
    >> Things like the A1000 and D1000 want HVD to talk to them. Many
    >> other things want LVD, and unfortunately, there does not seem to be a
    >> LVD card for the SBus. (This is what moved me from an Ultra-2 to an
    >> Ultra-60 -- to be able to use PCI cards so I could get a LVD card to
    >> talk to an Exabyte EXB-430 tape library.
    >>
    >> This difference could be the source of your difficulties.


    >I am trying to talk to a DDS-4 tape drive.



    Which most likely is a SE SCSI device, and an HDV card may fry its
    interface chips..

    You probably wanted to get a Sun SWIFT SBUS card instead.
    X1018A, 501-2739


  9. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak wrote:
    > Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    > (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    > Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    > a difficult time getting it to work.


    Thanks everyone for replying. I had no idea about the HVD vs the LVD.
    Fortunately I didn't fry anything in the process. To Doug's point, yes,
    I should have gotten the Sun SWIFT X1018A card instead. Currently I am
    using a HD68 to HD50 cable and connecting the DDS-4 to my second narrow
    scsi sbus card on the SS10. Everything Works like a charm now.

  10. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak wrote:
    > Kurt Nowak wrote:
    >> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >> a difficult time getting it to work.

    >
    > Thanks everyone for replying. I had no idea about the HVD vs the LVD.
    > Fortunately I didn't fry anything in the process. To Doug's point, yes,
    > I should have gotten the Sun SWIFT X1018A card instead. Currently I am
    > using a HD68 to HD50 cable and connecting the DDS-4 to my second narrow
    > scsi sbus card on the SS10. Everything Works like a charm now.



    Since you are using a narrow SCSI controller, you will have to be
    especially aware that the drive is 'streaming'. If the data does not
    reach the drive fast enough, it will have to stop/start all the time,
    which will wear the drive out.

  11. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Dave wrote:
    > Kurt Nowak wrote:
    >> Kurt Nowak wrote:
    >>> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >>> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >>> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >>> a difficult time getting it to work.

    >>
    >> Thanks everyone for replying. I had no idea about the HVD vs the LVD.
    >> Fortunately I didn't fry anything in the process. To Doug's point,
    >> yes, I should have gotten the Sun SWIFT X1018A card instead. Currently
    >> I am using a HD68 to HD50 cable and connecting the DDS-4 to my second
    >> narrow scsi sbus card on the SS10. Everything Works like a charm now.

    >
    >
    > Since you are using a narrow SCSI controller, you will have to be
    > especially aware that the drive is 'streaming'. If the data does not
    > reach the drive fast enough, it will have to stop/start all the time,
    > which will wear the drive out.


    Do recommend that I use an SE wide adapter instead? Like an X1063A
    (370-1703)? Or something else?

  12. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    Kurt Nowak wrote:
    > Dave wrote:
    >> Kurt Nowak wrote:
    >>> Kurt Nowak wrote:
    >>>> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >>>> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >>>> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >>>> a difficult time getting it to work.
    >>>
    >>> Thanks everyone for replying. I had no idea about the HVD vs the LVD.
    >>> Fortunately I didn't fry anything in the process. To Doug's point,
    >>> yes, I should have gotten the Sun SWIFT X1018A card instead.
    >>> Currently I am using a HD68 to HD50 cable and connecting the DDS-4 to
    >>> my second narrow scsi sbus card on the SS10. Everything Works like a
    >>> charm now.

    >>
    >>
    >> Since you are using a narrow SCSI controller, you will have to be
    >> especially aware that the drive is 'streaming'. If the data does not
    >> reach the drive fast enough, it will have to stop/start all the time,
    >> which will wear the drive out.

    >
    > Do recommend that I use an SE wide adapter instead? Like an X1063A
    > (370-1703)? Or something else?


    I guess it does stream OK, then there would be nothing to be gained by
    changing. But generally I suspect it might be more reliable.

  13. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    According to Kurt Nowak :
    > DoN. Nichols wrote:
    > > According to Kurt Nowak :
    > >> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    > >> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    > >> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    > >> a difficult time getting it to work.

    > >
    > > What are you trying to talk to with it? The SBus differential
    > > cards are HVD (High Voltage Differential), not the more recent LVD (Low
    > > Voltage Differential) which will also talk to single-ended SCSI.


    [ ... ]

    > I am trying to talk to a DDS-4 tape drive.


    I consider this to be unlikely to be HVD. LVD or SE are more
    likely.

    Is there a symbol on the drive's label showing what kind of SCSI
    it is? They are all things like diamonds with various alternative
    lines.

    SE (single-ended) looks sort of like this:

    /\
    < ---
    \/

    (where the '<' indicates a closed corner.)

    HVD (High Voltage Differential) sort of like this:

    //\
    << ----
    \\/

    (The extra "<" is outside the primary diamond.)

    and LVD (Low Voltage Differential) is sort of like this:
    /\
    // \
    << -----
    \\ /
    \/

    (the extra "<" is *inside* the primary diamond, which I had to draw
    larger here to make room.)

    If you are lucky, the DDS-4 will also have the letters "LVD" or
    "SE" near the symbol.

    In eBay auction 160171723507 there is an HP SureStore DDS4 tape
    drive which includes a photo of the back. This photo (the third)
    includes the symbol for LVD and the letters "SCSI LVD/SE" bracketing the
    symbol.

    eBay auction 160171963245 explicitly states that their
    IBM 09N0980 Seagate STD2401LW drive is LVD/SE.

    220163374958 says only LVD, for what that may be worth.

    230184620557 says LVD/SE

    So -- based on this you *don't* want to use a HVD SCSI interface
    (which is what you have), though you *might) be able to use a SE 68-pin
    interface as long as your drive is a model which explicitly states that
    it can handle SE as well as LVD.

    The 370-1703 SBus card states that it can be used in the
    following machines:

    SS4
    SS5
    SS10 <****<<<
    SS20
    SS600
    SS1000
    SS2000
    (machines which match A11, A12, and A14 which I won't bother
    dereferencing, since you have an SS10.)
    and E3000 through E6500 and E10000.

    so -- *if* your drive admits to accepting SE as well as LVD, you can use
    this card -- though as one of the other followups suggested, you may not
    be able to keep up with the data rate that the drive wants.

    Note that you may have already damaged either your HVD interface
    or your drive. Try connecting through a 50-pin to 68-pin cable to see
    whether you can talk to the drive with the 50-pin SCSI built into the
    system. If so, then go for the SE card above -- it may take some time
    to find one on eBay.

    *Or* -- look for an Ultra-60 on eBay -- and for a LVD PCI card
    to go with it. it will be significantly faster (probably dual 450 MHz
    CPUs), and you can find the LVD cards in PCI format, even though you
    can't find them in sBus.

    But *stop* trying to connect the HVD interface to the drive. I
    don't know which you are more likely to damage -- the interface, or the
    drive, but it is bad news to mix them.

    Good Luck,
    DoN.
    --
    Email: | Voice (all times): (703) 938-4564
    (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
    --- Black Holes are where God is dividing by zero ---

  14. Re: Compatibly help: Sparc 10 and Ultra Wide Sbus SCSI adapter

    DoN. Nichols wrote:
    > According to Kurt Nowak :
    >> DoN. Nichols wrote:
    >>> According to Kurt Nowak :
    >>>> Does anyone know if the Sun Microsystems Differential Ultra/Wide SCSI
    >>>> (UDWIS/S) SBUS card P/N 370-2443 (X1065A) is compatible with an older
    >>>> Sparc 10 machine. I bought one of these on Ebay and I seem be be having
    >>>> a difficult time getting it to work.
    >>> What are you trying to talk to with it? The SBus differential
    >>> cards are HVD (High Voltage Differential), not the more recent LVD (Low
    >>> Voltage Differential) which will also talk to single-ended SCSI.

    >
    > [ ... ]
    >
    >> I am trying to talk to a DDS-4 tape drive.

    >
    > I consider this to be unlikely to be HVD. LVD or SE are more
    > likely.
    >
    > Is there a symbol on the drive's label showing what kind of SCSI
    > it is? They are all things like diamonds with various alternative
    > lines.
    >
    > SE (single-ended) looks sort of like this:
    >
    > /\
    > < ---
    > \/
    >
    > (where the '<' indicates a closed corner.)
    >
    > HVD (High Voltage Differential) sort of like this:
    >
    > //\
    > << ----
    > \\/
    >
    > (The extra "<" is outside the primary diamond.)
    >
    > and LVD (Low Voltage Differential) is sort of like this:
    > /\
    > // \
    > << -----
    > \\ /
    > \/
    >
    > (the extra "<" is *inside* the primary diamond, which I had to draw
    > larger here to make room.)
    >
    > If you are lucky, the DDS-4 will also have the letters "LVD" or
    > "SE" near the symbol.
    >
    > In eBay auction 160171723507 there is an HP SureStore DDS4 tape
    > drive which includes a photo of the back. This photo (the third)
    > includes the symbol for LVD and the letters "SCSI LVD/SE" bracketing the
    > symbol.
    >
    > eBay auction 160171963245 explicitly states that their
    > IBM 09N0980 Seagate STD2401LW drive is LVD/SE.
    >
    > 220163374958 says only LVD, for what that may be worth.
    >
    > 230184620557 says LVD/SE
    >
    > So -- based on this you *don't* want to use a HVD SCSI interface
    > (which is what you have), though you *might) be able to use a SE 68-pin
    > interface as long as your drive is a model which explicitly states that
    > it can handle SE as well as LVD.
    >
    > The 370-1703 SBus card states that it can be used in the
    > following machines:
    >
    > SS4
    > SS5
    > SS10 <****<<<
    > SS20
    > SS600
    > SS1000
    > SS2000
    > (machines which match A11, A12, and A14 which I won't bother
    > dereferencing, since you have an SS10.)
    > and E3000 through E6500 and E10000.
    >
    > so -- *if* your drive admits to accepting SE as well as LVD, you can use
    > this card -- though as one of the other followups suggested, you may not
    > be able to keep up with the data rate that the drive wants.
    >
    > Note that you may have already damaged either your HVD interface
    > or your drive. Try connecting through a 50-pin to 68-pin cable to see
    > whether you can talk to the drive with the 50-pin SCSI built into the
    > system. If so, then go for the SE card above -- it may take some time
    > to find one on eBay.
    >
    > *Or* -- look for an Ultra-60 on eBay -- and for a LVD PCI card
    > to go with it. it will be significantly faster (probably dual 450 MHz
    > CPUs), and you can find the LVD cards in PCI format, even though you
    > can't find them in sBus.
    >
    > But *stop* trying to connect the HVD interface to the drive. I
    > don't know which you are more likely to damage -- the interface, or the
    > drive, but it is bad news to mix them.
    >
    > Good Luck,
    > DoN.


    Don,

    I have stopped attempting to fiddle with the HVD card since you all made
    it very clear that it was not compatible and may cause damage. I now use
    a 50-pin to 68-pin sun cable and connect it to my second 50-pin narrow
    scsi card. Everything seems to work fine and it seems to stream well
    too. Fortunately I didnt fry anything.
    Thanks for all the detailed scsi explanation. I learned a lot.
    /Kurt

+ Reply to Thread