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.

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.

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.

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.

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.

Briefly, FreeBSD is a UNIX® like operating system for the i386™, IA-64, PC-98, Alpha/AXP, and UltraSPARC® platforms based on U.C. Berkeley's ''4.4BSD-Lite'' release, with some ''4.4BSD-Lite2'' enhancements. It is also based indirectly on William Jolitz's port of U.C. Berkeley's ''Net/2'' to the i386, known as ''386BSD'', though very little of the 386BSD code remains. A fuller description of what FreeBSD is and how it can work for you may be found on the FreeBSD home page.

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.

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...

For optimal results, you need to speak normally. It will work best if you speak clearly at a regular pace. Do not try to slow down. Mobile411™ isolates your voice and should not pick up background noises. If you are in a really loud environment, you may need to type your entry or bring your cellphone closer to your mouth.

FreeBSD supports APM on certain machines. Please look in the LINT kernel config file, searching for the APM keyword. Further information can be found in apm(4).

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..

The Open Group has released the source code to Motif 2.1.30. You can install the open-motif package, or compile it from ports. Refer to the ports section of the Handbook for more information on how to do this. Note: The Open Motif distribution only allows redistribution if it is running on an open source operating system. In addition, there are commercial distributions of the Motif software available.

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.

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.