SCSI interface.

I am trying to find information on using lab view to communicate with an
interface connected to a SCSI card. Has anyone solved this problem? If
any help can be given I would greatly appreciate it.
Charles Fay
Physics Lab Facilities Manager
Western Kentucky University

Thanks for the reply, Harold.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>haroldkarl wrote on Sat, 25 February 2006 16:11</b></td></tr><tr><td class="quote">
it is
a 501-4266
</td></tr></table>
Ah, yes. A clumsy typo.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
according to http://sunsolve.sun.com/handbook_pub/Systems/E4500/spec.html it is
One 20-MB/sec, 68-pin, fast/wide SCSI-2 (synchronous) per I/O board
</td></tr></table>
Yes, but I have E4000 and E6000 and so I am not sure that the E4500 spec applies (though it probably does in this instance). I think that the E4500 had a later I/O board (the 501-4883).
Do Sun not make data sheets available for each product so that we could know for sure (especially as I have several other similar questions)? I'm trying to learn where to fish rather than asking for someone to throw me a snack ;-)

Similar Messages

Solaris 10, ISALogic SCSI interface and ARCVault tape library

I put an ISALogic SCSI interface card into a SunBlade 2000, installed
Solaris 10_u4 on it and attached an ARCVault tape library. The system
see the tape but fails to see the library and the robot. The robot and the
tape are on the same scsi bus.
I followed the instructions on how to do a scsi passthrough and did a probe-scsi-all
at the ok prompt of the system.
The probe on the ISAlogic interface card sent the system into a bus error.
Any idea how I could make the robot visible on the same bus?
Lydia

A firmware update on the Blade solve the problem.

USB Firewire and SCSI interface...

was looking at polaroid scanners, 35plus and CS4000 that have SCSI connection port only, and checked the Polaroid website which said you could interface the two connection types with a modification. they said it would not work well with an adapter, though. is there a recommended way to accomplish this, or would it be custom?
G5 2.0 512 160GB Mac OS X (10.1.x) I have one firewire port

Yes, the recommended way is to buy a scanner with usb2.0 or firewire built in. I don't know anything about Polaroid film scanners, but Nikon do a number of scanners that are compatible with OSX.

How can I connect a DLT-IV Tape drive with SCSI interface to Quad G5?

I have had no problems with my "Quantum equivalent La Cie DLT-IV Tape drive" on OSX connected to the G4 Quicksilver using an Adaptec 2930CU PCI card - but I can't move that to the G5 as it has to be PCI-Express cards as far as I can tell.
Adaptec pre-sales support inform me that Adaptec have no Mac support in their current product range.
Has anyone found a solution to this connection requirement that will work with Retrospect and DVD StudioPro?
If there is a workable solution which is no longer available to buy - I would still be interested in knowing so I could scour ebay for it.
TIA,
Richard

Hi Richard;
If you go to ATTO, they are offering a ExpressPCI PSC which include a SCSI bus on sale for $24.11.
Allan

Can I connect an external DLT Tape drive to the SCSI connector on an E450

Hi... totally new to SPARC. I have inherited an E450. It appears to have the 8 bay option. I have 6 scsi disk drives installed in slots 0 through 5. Internally, there is one ultra scsi controller in slot 2 and two internal cables running from the top of the card, one for each channel. I do have an extra ultra pci scsi card, but when I plugged it into a pci slot, the system would not boot. Bottom line, can I connect an external DLT drive to either Channel A or Channel B at the rear of the Unit and not intefere with other SCSI devices (i.e. the disk drives). Currently, the DLT is set to SCSI ID 8. If this isn't recommended, how do I install the secondary ultra scsi card and have the system recognize it ? Note that the Hard drives have been wiped and I WILL be loading Solaris 10, but have not yet. I wanted to make sure all of the hardware worked first. The second PCI Scsi controller I have is an Adaptec 39160, and I'm assumming it will work IF needed. I'd prefer not to use it if necessary.... ANY HELP is sincerely appreciated ! Thanks, Randy

I suggest you leave the current internal connections just as they are.
You never know when you'll need to add more disks.
That Adaptec card is for PC's.
It won't work in a Sun SPARC-based system.
What sort of SCSI interface is required for that tape device?
Single-Ended? High Voltage Differential? Low Voltage Differential?
You need a card that matches that interface type if you hope it to "drive" the tape.
One quick way to tell, is to examine the chassis of the tape peripheral
and find the small icon that should be at the port for the SCSI cable.
For example, Sun's 375-0005 card is Single-ended and is what you already have inside your E450.
Sun's 375-0006 is a HVD card and would be correct for A1000 and D1000 arrays or L7 or L25 tape libraries.
Sun's 375-3057 card is LVD and would be appropriate for Sun's D2 array.
The manual for that 375-3057 card happens to have pictures of the SCSI icons I just mentioned.
See page 35 in that manual.
http://192.18.109.11/816-2156-11/816-2156-11.pdf
Once you confirm what's needed by the tape peripheral, we may be able to suggest how to connect it properly.

Will OSX support Adaptec PCI Express scsi cards in an early 2008 Mac Pro?

I need to move my scsi interface scanner from a G4 machine and the old PCI Adaptec AHA 2930 CU card won't fit. I was using Snow Leopard on the G4 unit - it still supported the Adaptec card and all was good. My 23" Cinema display then bit the dust and I replaced it with with a 24" Cinema display with the mini display port connector. I purchased an adapter from Kanex to make it compatible, but the adapter was defective - so I returned it. Their reviews aren't very good - seem to have a lot of D.O.A. adapters - not sure I want to deal with the frustration, but it would be the least expensive option.
I do have, however, an early 2008 Mac Pro that I can use, provided that it supports the newer PCI Express scsi cards that Adaptec makes. I'm not sure which one to get yet, either. I'd rather not buy one and find out it won't work. I can make a partition on the boot drive for Snow Leopard in case scsi isn't supported in later versions of OSX. In case you're wondering, I did use a scsi to firewire adapter to run the scanner on my laptop for a while - but it stopped working and I can't locate any replacements (or the company - 2nd Wave Technologies - for that matter). I haven't tried locating a scsi to usb adapter, but from what I can see, they are getting pretty scarce. I'd replace the scanner, but it is fairly pricey and the newest model retails at the price of a small car - so that really isn't an option at this point.
Thanks in advance for any info.
Message was edited by: Jakob Richardt
Changed name of display adapter manufacturer.

Thanks for the response - I guess the question I should have asked is "Will OSX support scsi cards in an early 2008 Mac Pro and if so, which ones?" I didn't realize Apple and Adaptec weren't working together - my G4 tower arrived with an Adaptec card in it when I bought it in 2000 (from a third party vendor, not directly from Apple). It came with either OS 8.* or OS 9. When I updated to OSX, everything continued working, so I didn't think much about it until I pondered using the Mac Pro for the scanner - at some point the G4 is going to stop working - need to have a solution before that happens. The manuals I've been reading refer to the slots in the G4 machines as PCI. The manual for the Mac Pro refers to the slots as PCI e. These slots have fewer connectors, so I thought that the "Express" part of the name referred to this particular card configuration when compared to the longer card connectors in the G4 type of machines.
Can you tell me what scsi card brands will work in the Mac Pro? I'd still like to pursue this option. As I mentioned in my original post, buying a new scanner isn't in the cards right now - it costs more than the computer, so, although pricey, the card option is still less expensive.
Thanks!

How to Run a SCSI Scanner with Firewire In OS X?

Does anyone know how to run a SCSI scanner with Firewire in Mavericks?
I have unsuccessfully tried the RATOC FR1SX SCSI-to-Firewire converter. The Ratoc is recognized as a Firewire device in the System Profiler (see pic below). However, the VueScan scanning software does not recognize the scanner. I know the scanner works because I have been using it in an old HP PC. As such I installled Windows 7 64 bit via Boot Camp to see if I could use the scanner, but had no luck.
I have an iMac 21.5-inch, Mid 2010.
ANY HELP?

The Mac scanner driver is not seeing it as a native SCSI device assuming VueScan supports the model of scanner you have. (You did not list the scanner model.)
Other than getting a modern non-SCSI scanner, a possible option would be to get a Thunderbolt PCI expansion chassis and a 'real' SCSI interface card. There is no guarantee this will work though as SCSI has been discontinued in the Mac world for years and years. If you then want to look at a SCSI card for use with the expansion chassis then look at the following.
Hmm, just looked the AttoTech SCSI cards have been discontinued as well, as I said SCSI is ancient history in the Mac world.

USB to SCSI Adapter - Anyone have one?

I'm trying to find one that works. I need to connect an Epson Expresson 836XL large format scanner to my iMac, and this is the only way.
I'm looking for an OS 10.5.x compatible adapter that has a 50 pin SCSI interface on one side and (USB 2 preferrably) on the other. I'm not sure of the exact SCSI type though.
George Peters found this one for me, but perhaps there are alternatives?
http://www.pcconnection.com/IPA/Shop/Product/Detail.htm?sku=6638881&srccode=cii_ 9324560&cpncode=08-48791933-2
Thanks. ~Kort

Good news everyone!
I bought it and installed it (with a 50 pin port adapter) and am pleased to say that the the Ratoc FR1SX is compatible with the Epson 836XL scanner using the latest VueScan software. And the optional power supply in not necessary. It took a few restarts and some playing with the supplied driver software supplied by Ratoc on a CD, but it does now work smoothly.
I am thrilled. It scans images beautifully, perhaps better than when attached to the old G4. And it is faster as well. For about $150 I know have a working 13x19 scanner instead of having to get a new one for $2000 or more.
So yes, there is a *SCSI to Firewire adapter* out there that works in OS 10.5.2.
Spread the good word...
~Kort

PowerBook 145B - strange hard drive interface?

I opened up a PowerBook 145B from a friend that had died (the PowerBook, not the friend) and pulled out the hard drive to recover the data. I thought I would find some type of regular SCSI interface on the hard drive, but...
I've spent some time Googling and found people who can't figure out how to get data off this drive (IBM Model WDS-2120, 120mb) and no solutions. It says 2.5" SCSI 17mm on the drive, but the interface is something I haven't seen.
Does anyone have ideas on how to get the data off this drive?
Thanks!

Hi,
I don't think a cable exists which would handle the data and power requirements of the WDS-2120 and allow connection to a more standard SCSI interface.
The adapter that I have is part of the external case mentioned above. It has made it possible to supply power to e.g. a WDS-2120 drive, and to connect that drive to the HDI-30 SCSI port of a PowerBook or the DB-25 SCSI port of a desktop Mac. However, as indicated, it may be difficult to buy something like that today.
(It looks like 8 of the pins are for power on the HD.)
If I remember correctly, the ID selector is connected to some of the pins in the separate group of eight. Since the internal hard drive always is ID 0, the selection can even be simplified (meaning that the complete interface may not be needed). So, do not be surprised if you see a connector covering merely the main portion of the interface in some computer models.
For more on pinouts, try a Google search for this or any other (maybe Quantum) 2.5" SCSI hard drive. Also, you may be able to find something of interest in the Apple hardware documentation here.
Jan

SCSI Printer adapter

I would like to purchase a new Intel laptop, but I am not yet ready to give up my HP Laser Jet 6MP printer that has a SCSI interface. Does anyone know if a USB - SCSI adapter exists and where I could find one? My printer is new and it would be a shame to give it up. Thank you in advance for your help.
Patrizia

Such animals exist, but you may have to look on eBay to find them. The ones that were developed tended to work with most printers, but not all SCSI devices. If you see something on eBay, check the support site for the company that originally built the device to see what hardware it is compatible with.

Anybody know to where to get a 2nd wave Firewire to SCSI Adapter?

Hello
I want to connect my Imacon Flextight Photo to my 20" Imac.
My friend has 2nd Wave's Firewire-to-SCSI interface adapter and it works great.
I hear all sort of weird stuff about adapting these two component.
People are slacking of Ratoc, Orange micro and other brands. Doesnt work with Panther and so on.
So I just want this item which works on his Intel duo and has worked on his Powerbook and Ibook.
Even though I have heard others complain about having problems with 2nd wave.
Anybody know where to get it? Please...
Feel free emailing me directly.
Thank you!
Regards
Reimar

And oh I have tried their homepage.
They dont have it anymore.

KT7 Master 6347-S SCSI Device Drivers?

I just purchased a MSI KT7 Master 6347 from an online dealer and when I got ready to installed the device drivers from the MSI CD found that the CD was 'Sealed[Melted?]' to the plastic storage sleeve.
I have been able to find most of the drivers for this board online [but other than the BIOS upgrade had to go off site for the drives {why is that MSI?}]..
But I am unsure of which SCSI drivers that I need for Win'98SE??
Can not tell which drivers I need for this board online?
--David

Quote
Originally posted by wonkanoby
what are these drivers for?
KT7 Master 6347-S SCSI Device Drivers?
This mainboard has built-in SCSI interface and while I currently do not have anything connected to it I am getting the "YELLOW" ''!'' :] in Windows which might be causing some of my other troubles that I am having??
*> Side Note I don't understand why MSI does not have all the needed device drivers for their mainboards posted and/or linked to on their web sites??

SCSI HD's

Running a Beige G3 333 MT; RevC; 512MB; ATTO PSC PCI Express; Radeon7000ME; USB/Firewire combo.
My Quantum Viking II 9G died. I began shopping Ebay.
There are descriptions like, 'hot swapable' and 'IDE/SCSI interface'.
How can a drive be both IDE and SCSI? Is this a PC thang? How can one 'hot swap' a SCSI drive? I thought one should always connect/disconnect SCSI devices with the computer turned off. Again, PC stuff?
I believe almost any IDE drive will work in a Mac, but will almost any SCSI drive work?
EG, What are the differences between the Viking and Atlas models? IBMs? Seagates?
I purposely limit expenditures on my Beige and prefer not to spend big bucks on a new, large capacity SCSI HD. (Of course I'll pay the going rate for IDE drives since they can be used in the G4 also.)
Thanks in advance for any thoughts on buying SCSI drives!

"Hot Swap" SCSI drives have a special 80-pin SCA -- Single Connector Attachment -- connector that provides both power and data in a way that allows the drives can be installed and removed with the power on. On installation, the pins for ground make first, then power, then data; on removal, the reverse. The SCSI ID and a few options are set by straps on the backplane or paddleboard, not on the drive. So that as the drive is inserted, it takes on the ID of the slot into which it is inserted.
These drives are intended to be installed in a cabinet with a backplane or with a paddleboard that offers a 68-pin connector and a 4-pin Molex power connector and the straps. They should NEVER be used with anything claiming to be an SCA cable. If you are handy, you can buy the paddleboards to convert a single drive, provided you follow the rule: "Only one cheat per drive." If that cheat is a paddleboard, do not also try to also use a 68-50 wide to narrow converter on the same drive. You used up your cheat with the paddleboard.
"Hot swap" drives of modest sizes are cheap on the used market, because the High-End users who bought them originally have gone on to bigger and better drives, and because there is a little extra complexity and another part to buy to get them to work.
Here are pictures and description from a reputable seller:
http://mcpb.com/html/sca.f80hp.68f.html
The top picture shows the 4-pin power connector, the 68-pin Wide data connector, and the straps. The bottom picture shows the other side, with the 80-pin SCA connector for the drive itself.

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

Windows xp pro stalls - blank screen- hardware or software problem?

Hi Guys,
My system is about one month old and has been awesome in performance and graphics.
Suddenly it (windows xp pro) stalls after flashing the windows loading screen and it goes blank. Looks like a software problem?
I am posting on this forum because when I check cmos, no hard drives are registered.
I can't get into safe mode, can't get past the administrator/user screen because no mouse operates here and can't select icons with the keyboard.(No admin passwords were set up anyway)
Booting from CD, repair console doesn't work because it can't find any hard drive.
Reluctant to do a complete reinstall because of precious stuff on the hard drive.
Using f8, "last known good..." just gives the same blank screen.
Using floppy boot, no other drives are recognized.
If my root directory has been wiped out by a virus or something, how come it gets past post and starts to load windows? If it's merely the graphics driver or similar not loading, how come the cmos shows no hard drive?
Is this a hardware or software problem? Any help much appreciated.

THE ANSWER !!
Hi Guys,
I finally got to talk to the guy who set up this system and he said that it is normal for RAID drives not to show on BIOS/CMOS. 'Think of it like a vrtual drive' he said. When the black and white initialization screen shows something like: 'Nividia Stripe-healthy'...then THAT is the hard-drive.
He said that as long as Windows was getting to the loading screen, that means that the computer itself was functioning okay, so don't worry about BIOS, the problem is a file corruption in windows, or virus etc.
Also he said that when trying to use recovery console or reinstall windows, because the system can only read the RAID drives through a SCSI interface, you have to load the Nvidia SCSI drivers from floppy by pressing f6 when asked to at the bottom of the pale blue screen (from Windows cd boot), before trying to do anything with windows (or windows will just tell you it can't read the drives, as it did before with me.)
So in the end, I reinstalled windows by that method and everyting seems fine so far. YAY!
Thanks you people for being kind enough to help someone out. I really appreciate it.

SCSI interface.

Similar Messages

Maybe you are looking for