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. See similar questions...

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. See similar questions...

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. See similar questions...

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. See similar questions...

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... See similar questions...

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.. See similar questions...

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. See similar questions...

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. See similar questions...

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. See similar questions...

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. See similar questions...

There is only module that can be used to expand the IBM SCSI Adapter with cache/A from 512K cache to 2MB cache is the IBM P/N 30F5360 / FRU 74X8637, which is a 1MB x 9 bit (Parity) 120ns module *with* IBM-specific presence detection. Also Kingston had their KTM-1000/M30 module which also worked, but is no longer made. The above-mentioned IBM modules can be found on the Mod. 30-286(8530-Hxx or -Bxx) with 80286-cpu - if anywhere at all. See similar questions...

This acronym is pronounced "scuzzy" and stands for Small Computer Systems Interface. There are now three types of interfaces for hard drives, CD-ROM drives, etc. One is SCSI, another is IDE (also called PATA, Paralle ATA) and the newest one which replaced IDE is called SATA (Serial ATA). IDE and SATA are much more common and less expensive. SCSI is more expensive and also more flexible and generally faster. See similar questions...

In 'Q. How does replication work intra-site in Windows 2000?' we saw how the KCC automatically creates and maintains the connection objects for intra and inter-site replication however these can be manually maintained if you wish by disabling the KCC, this is NOT recommended! Enter the DNS name of a domain controller, leave the port as 389 (LDAP) and make sure the connectionless option is clear. Click OK Some text will display in the right hand pane. Now select bind from the Connection menu. See similar questions...

Just remove the 'x' in set::modes-on-connect, then users will not be set +x automatically and thus will not be cloaked. Option 2: fully deny users to be cloaked If you don't even want users to be cloaked when they want themselves to, in other words: prevent users from setting themselves +x. See similar questions...

To disable Kaleidoscope, move the Kaleidoscope file out of the Control Panels folder, either by dragging it out manually or by disabling it with your Extensions Manager, and restart your Macintosh. If you drag Kaleidoscope to the trash, you must restart first before emptying the trash; otherwise the Finder will complain that the file is still in use. See similar questions...