Yes you can. I have successfully used the 4020i with an Adaptec 1542CF controller. The only change that I had to make was in the SCSISelect utility. Upon getting into SCSI select, you will need to select Device Configuration. Then go to the ID that the 4020i is on (default = 2). Where it says YES for FAST SCSI, change it to say NO. If you attempt to burn CDs when this is set to YES, you will run into mysterious Buffer Underrun Errors. I don't know why this causes buffer underruns, but it do...

Sure. The Iomega Buz uses the Advansys ASC3050B PCI SCSI Controller. It works just like any other SCSI card based on this chip. Several people have reported success (or even improvements) using the Advansys SCSI drivers from www.advansys.com. The latest drivers for all systems are listed here.

Yes, you can have other devices on the chain, providing you make sure that your termination is correct. I have run my 4020i off of an Adaptec 1542CF with a scanner plugged into the external SCSI port. The scanner was terminated as well as the 4020i. This setup appeared to work just fine. You must be careful when placing the CD-Writer on a SCSI bus with other devices. If there is a possibility that one of the other devices will be accessed during a write, (i.e.

I would recommend everyone use an active terminator. I could not flash a ROM upgrade, until I changed the termination per advice from an HP tech support rep. If you are using the HP supplied controller from Advansys be advised there are at least 2 revisions of the card. The one I first got was positively identified to produce random read errors when reading from the HP CD. This means that if I used the HP drive to read a CD, I occasionally had corrupted data during reading. Didn't matter if...

If you don't have any SCSI devices attached to your Buz, or you don't use them from DOS, there is no reason to put up with the long "Iomega Jet SCSI" BIOS sequence. This is where the machine probes the Buz SCSI bus for devices at boot time, before Windows starts. To disable this boot-time probe, remove the EPROM on the Buz! The 64k EPROM on the card contains the BIOS boot code for the SCSI controller. If you don't have SCSI devices, you don't need it.

The newer AIC789x series Adaptec chips are supported under the CAM SCSI framework which made it's debut in 3.0. Patches against 2.2-STABLE are in ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/. A CAM-enhanced boot floppy is available at http://people.FreeBSD.org/~abial/cam-boot/. In both cases read the README before beginning.

There are 2 general ''versions'' of the 742a card. They are hardware revisions A-G, and revisions H - onwards. The revision letter is located after the Assembly number on the edge of the card. The 742a has 2 ROM chips on it, one is the BIOS chip and the other is the Firmware chip. FreeBSD does not care what version of BIOS chip you have but it does care about what version of firmware chip. Buslogic will send upgrade ROMS out if you call their tech support dept.

This is basically a known problem. The EISA on-board SCSI controller in the HP Netserver machines occupies EISA slot number 11, so all the ''true'' EISA slots are in front of it. Alas, the address space for EISA slots >= 10 collides with the address space assigned to PCI, and FreeBSD's auto-configuration currently cannot handle this situation very well. So now, the best you can do is to pretend there is no address range clash :), by bumping the kernel option EISA_SLOTS to a value of 12.

Ships" are short for "relationships." This is commonly a fanfic term, but if you support a particular pairing of characters between Harry Potter characters Several of you have accused me of "selling out" and all this other junk. I can tell you that it's downright hurtful, but I understand your own pain. I don't like that I have to put ads up, but there is a reason I must. I cannot afford to run the site on my own accord - and my parent's.

In general; I put as many batteries in as possible. The Zilla controllers are the best dc controllers on the market and they come in 3 voltages 156v, 300v and 348v at 1000 or 2000 amps. As distance is related to weight of batteries, golf cart batteries give lots of weight at 65lbs each. You get the most for the money but it is hard to get the voltage high when you need 20 of them, just to get 120 volts.

Section 12- Kernel Programming Questions Answers to common questions about kernel programming details. See also Tigran Aivazian's page on kernel programming.

This is included here because it's a Frequently Asked Question, but... it's completely nonsensical. The Buz is a SCSI controller, not a SCSI target device (like a tape drive or hard disk). If you're asking this question, you probably have a misunderstanding of how the Buz device looks and works. And now, for the technical nit-picking..

Yes! The internal Jaz drive plugs into the internal SCSI connection, while the external Jaz (portable) comes with exactly the right cable to connect to Buz. It's a perfect match.

There are 2 genera l ''versions'' of the 742a card. They are hardware revisions A-G, and revisions H - onwards. The revision letter is located after the Assembly number on the edge of the card. The 742a has 2 ROM chips on it, one is the BIOS chip and the other is the Firmw are chip. FreeBSD does not care what version of BIOS chip you have but it does care about what version of firmware chip. Buslogic will send upgrade ROMs out if you call their tech support dept.

This is basically a known problem. The EISA on-board SCSI controller in the HP Ne tserver machines occupies EISA slot number 11, so all the ''true'' EISA slots are in front of it. Alas, the address space for EISA slots >= 10 collides with the address space assigned to PCI, and FreeBSD's auto-configuration currently cannot handle this situation very well. So now, the best you can do is to pretend there is no address range clash :), by bumping the kernel option EISA_SLOTS to a value of 12.

The problem is due to missing driver for AIC-78xx adapter, which would be naturally provided by the SUNWcadp package in Solaris. However, we realize that we cannot redistribute such a package because it is not currently part of OpenSolaris. A solution to this is currently under review.