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.

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

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.

Easy CD Creator has its own image file format. CDEveryWhere creates an ISO image, a byte-for-byte file of the data that should be written to the CDR. You may need to upgrade Easy CD Creator to be able to use the ISO image. This upgrade can be downloaded from http://www.adaptec.com. After you have the newest version, select the "ISO Image Files (*.iso)" option from the "Select Image File" dialog. You also may experience problems if you create a pure Macintosh CD.

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

I had many problems when I first started with the Iomega Zip on my GS and it isn't the most reliable thing - But it works. Attach a terminator adapter to the back of the remaining port on your external HD - The Zipdrive has a weak termination and requires another terminator source. Last, if you are working on the GS for a long time and suddenly the Zipdrive Icons don't pop up when you load Finder, simply eject the zipdisk and push it back into the drive.

It does work, but likely there is still something wrong with the registry settings (installation is not the strongest point of Adaptec). You might try the fix which is available on the following site: Winamp reports the location of the first MPEG header in the MPEG stream data. If you have enabled the ID3V2 tags, it will place the ID3V2 header before the MPEG stream, the the first MPEG header will be shifted with the size of the ID3V2 header.

Adaptec has issued a lot special version for some individual inquiry strings supporting. Please use the software bundling with drive.

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.

First, refer to the xD-Picture Card? Compatibility Chart to verify that the card is supported in your model. If the card is not supported, return it to the store where you purchased it. The FE-140 may not recognize a non-Olympus brand memory card or a card that has been formatted on another device, such as a card reader or personal computer. As a general rule, xD-Picture Card media should only be formatted in the camera.

If you have an SD card which is not recognized or which results in many media errors you should format it. Although most commercial cards come pre-formatted it may be possible the formatting was not done correctly. To format, insert the SD card into your PC card reader. Open the ???My Computer' program from your desktop and right-click (or press the Applications key on your keyboard) to bring up the context menu for the SD card. Select ???Format' from this menu.