We expect compatibility to be universal.
As you test, please add any machines missing here.
See the speed of your Macintosh’s bus here
[!NOTE]
Assume all work! This is not an exhaustive list.
Plus*, Portable*, SE, SE/30, LC, LC II, LC III, LC 475, Classic, Classic II, Color Classic, IIci, IIsi*, IIcx, IIfx, Quadra 605, Quadra 610, Quadra 650, Quadra 660av, Quadra 700, Quadra 950, Performa 575, Performa 600, Performa 630
Power Macintosh 4400, 6100, 6300/160, 6500/300, 7300, 7600, 8100, 8500, 8600, 9600, G3, TAM, ANS*
PowerBook 140/170, 180, 520/540, Wallstreet
- Requires some special configuration. Go to <https://ini.bluescsi.com> and click `Mac Plus` to download a special `.ini` configuration file, place it in the root of your SD card.
- The Plus does not have an internal 50 pin SCSI bus. DB25 only. There is a mod called the [Clipper Plus](https://jcm-1.com/product/clipper-plus/) which can add an internal 50 pin connector.
- The Mac Plus does not provide term power. You will have to provide power via USB or do the [diode mod](https://tinkerdifferent.com/resources/mac-plus-scsi-term-power-mod.123/).
- SCSI upgrade cards for the Macintosh 128K and 512K, like the Dove MacSnap, use Macintosh Plus ROMs and will work with the appropriate Mac Plus `.ini` configuration file
- Debug is currently not supported when using `System=MacPlus`
- Requires configuration file. Go to <https://ini.bluescsi.com> and click `Mac Plus` to download an `.ini` configuration file, place it in the root of your SD card.
- Requires a 34 pin adapter.
The IIsi does not provide TERM POWER. It must be powered via the Berg connector or USB.
From the IIsi service manual:
"The 85C80 [SCSI controller] does not provide the internal SCSI disk drive with termination power; the drive provides the termination power.”
Install CD must be on the internal bus on ID0 and disconnect the original CD drive.
The internal bus does not provide TERM POWER, though the external DB25 bus does.
These macs have a Fast SCSI 10MB/sec bus and can take full advantage of BlueSCSI v2’s speed:
Among the Power Macintosh series, the 7300, 7500, 7600, 8500, 8600, 9500, and 9600, Beige G3 all have 5 MBps narrow SCSI-2 on their external bus and a second internal bus (with no external connector) that runs Fast SCSI at 10 MBps
[SCSI]
System="Generic"
HP / Agilent 16702B
HP Apollo 9000/735 PA-RISC Workstation
HP 715 Series
HP 9000 Series 362/382 Controller - tested dumping and using HDD images from original drive and usage of 3rd party images. Both HP Basic and HP-UX booting and working fine.
Example of bluescsi.ini file for 362/382:
[SCSI]
System="Generic"
[SCSI6]
Vendor="HP"
Product="Blue"
SectorsPerTrack=123
HeadsPerCylinder=4
Name of the file with image - HD60_C2203.hpi .
Use 512K sectors. Example for DEC-like CD-ROM emulation, which may be necessary on VAXen:
[SCSI6]
Type=2 # CD
Vendor="DIGITAL"
Product="RRD42 (C) DEC 4.5d"
BlockSize=512
SunOS/Solaris are picky about drive geometry - file system creation may fail using default settings. Use the HeadsPerCylinder and SectorsPerTrack settings to change them to a value more in line with what is expected. When in doubt, it’s been reported that HeadsPerCylinder = 16 and SectorsPerTrack = 128 work as good general values.
You can also use the values in the Sun installation media’s format.dat to set up drives matching pre-defined configurations. This is especially helpful for SunOS 4.x which does not have any autodetection of drive parameters. The following example is the line for the “SUN2.1G” preset:
disk_type = "SUN2.1G" \
: ctlr = SCSI : fmt_time = 4 \
: ncyl = 2733 : acyl = 2 : pcyl = 3500 : nhead = 19 : nsect = 80 \
: rpm = 5400 : bpt = 44823
Using the data from that entry, create a disk image of size (ncyl + acyl) * (nhead * nsect * 512) bytes. Then, in bluescsi.ini, set HeadsPerCylinder to the value of nhead and SectorsPerTrack to the value of nsect.
Example bluescsi.ini entry for a drive matching the above SUN2.1G specification:
[SCSI3]
Vendor = "SEAGATE"
Product = "ST32550N"
Version = "1.0"
Serial = "T3751351"
HeadsPerCylinder = 19
SectorsPerTrack = 80
The following table has the values for all the standard Sun disk configurations provided in SunOS 4.1.4:
| Drive definition | ncyl | acyl | nhead | nsect | # of 512-byte sectors | Disk image size (bytes) |
|---|---|---|---|---|---|---|
| SUN0104 | 974 | 2 | 6 | 35 | 204,960 | 104,939,520 |
| SUN0121 | 1520 | 2 | 4 | 39 | 237,432 | 121,565,184 |
| SUN0207 | 1254 | 2 | 9 | 36 | 406,944 | 208,355,328 |
| SUN0327 | 1545 | 2 | 9 | 46 | 640,458 | 327,914,496 |
| SUN0424 | 1151 | 2 | 9 | 80 | 830,160 | 425,041,920 |
| SUN0535 | 1866 | 2 | 7 | 80 | 1,046,080 | 535,592,960 |
| SUN0669 | 1614 | 2 | 15 | 54 | 1,308,960 | 670,187,520 |
| SUN1.0G | 1703 | 2 | 15 | 80 | 2,046,000 | 1,047,552,000 |
| SUN1.05 | 2036 | 2 | 14 | 72 | 2,054,304 | 1,051,803,648 |
| SUN1.3G | 1965 | 2 | 17 | 80 | 2,675,120 | 1,369,661,440 |
| SUN2.1G | 2733 | 2 | 19 | 80 | 4,157,200 | 2,128,486,400 |
512 byte sectors need to be used, otherwise you may encounter data transfer overrun errors. Both the OpenBoot prompt (device cdrom) and Solaris expect the drive at SCSI ID 6 per default. Example config for Sun-like CD-ROM emulation, not necessary but fun:
[SCSI6]
Type=2 # CD
Vendor="TOSHIBA"
Product="XM-4101TASUNSLCD"
BlockSize=512
Atari TT via SCSI
[!NOTE]
Special care has to be taken with termination. If you have internal and external devices, testing shows that the internal device’s termination has to be OFF for the chain to work, since the DB25 has an always-on termination and the TT considers both on the same chain.
Atari MegaSTE via internal SCSI/ASCI adapter
[!NOTE]
With the MegaSTEs internal host adapter you cannot use the the DaynaPort emulation together with a bootable hard drive. The DaynaPort drivers for STiNG and MiNT require LUN 0, just like the bootable hard drive. This means that you cannot have both. Whether the authors of these drivers (both still active developers for the Atari) are going to improve this is not clear. Both are aware of this problem. Other software like ExtenDOS 4 might also be affected.
There is a potential makeshift, though.
Amiga 3000 - Motherboard SCSI
1. Set EnableSCSI2=0 in bluescsi.ini
2. If BlueSCSI is not your lowest ID drive, boot from another disk to HDToolBox and save config. After that the Amiga will find it on boot.
3. Download SCSI-Prefs and enable Synchronous Transfer. You need a clock battery to save settings.
Amiga A3000/A4000 CyberStorm Mk2 with SCSI module
1. Use RDBFlags on Aminet to set synchronous mode for a speed boost. Do not use the P5 tools as they do not understand large disks.
Example: RDBFlags Device cybscsi.device UNIT 1 SYNC
2. Set your Mask in HDToolBox to 0xFFFFFFFE. This is not the default setting.
Amiga 4000 TF4060 with A4091 or Fastlane Z3
1. The mask value in the partition configuration has to be changed to 0x0FFFFFFF. This is to limit DMA to the first 128 MB of RAM. DMA over this address range results in a crash.
Commodore CDTV (Original or Matze clone SCSI card) - Same as 1&2 for Amiga 3000.
Amiga A2091
Amiga Supradrive 500XP
Amiga 500 GVP HD8
Amiga 500 A590 Rom V.7 Kickstart 1.3 & 3.2
[SCSI]
System="Generic"
EnableSCSI2=0 ; Off
PrefetchBytes=0
[SCSI0]
SectorsPerTrack=32
HeadsPerCylinder=1
[SCSI]
System="Generic"
EnableSCSI2=0 ; Off
PrefetchBytes=0
[SCSI0]
SectorsPerTrack=32
HeadsPerCylinder=1
CMD HD SCSI controller/drive for the C64/C128 works fine with a suitably-named disk image. A dump of a previously-configured HDD is a good place to start since it’ll have the controller’s DOS and partition table ready-to-go.
Termination must be enabled on the BlueSCSI. The CMD controller can address multiple “drives”, but the first/main disk image must appear as SCSI ID 0, LUN 0, and thus be named HD00 xxxxx.hda (xxxxx being optional of course, but something descriptive such as “CMD-HD” is a good idea).
It is unknown whether the CMD controller can provide termination power, so it is recommended that you construct a cable to get power from the controller’s header to the BlueSCSI via its Berg connector. This header has the standard 5v/GND/GND/12v pinout, with 5v being on the pin next to resistor R2, and a Berg connector with its middle latch bump shaved off fits it, so this cable can be easily made from salvaged wiring (say from a defunct ATX power supply).
[SCSI]
System="NeXT"
Ensure SCSIFSBuffers is configured to 0 for Morley cards, or they throw all sorts of errors (not BlueSCSI specific).
Akai samplers often (always?) use SCSI ID 6 to identify the sampler itself, so avoid using images that use ID 6, or assign another ID to the sampler.
[!NOTE]
The SCSI cable may need to be plugged in backwards(!) See this Discussion for details.
Pay attention to what is explained in the AW4416 manual, supplement (v1.2 1.3) and supplement (v2) documents in regards to formatting. ‘Original’ is used for backing up and restoring songs while ‘FAT16’ is used for exporting and importing wav files. Disk Jockey v2 may not be the best solution to create images because of multiple partitions and size limitations. Check Custom Disk Images (Advanced) under BlueSCSI Images in the wiki on how to create hda image files for the BlueSCSI v2 connected to the internal SCSI port of the AW4416. The difference between the AW4416 and the AW4416A is that the latter has an ATAPI IDE CD recorder/player, not a SCSI one. In that case an IDE to SD is a the way to go. Avoid images using ID-6 since it is reserved for the AW4416 itself. If you use the external SCSI connector at the back of the AW4416, be aware an occupant CD recorder/player has ID-3 by default (jumper defined).
Used Initiator mode to dump a very loud Quantum Fireball ST and then target mode in place of the hard drive.
IBM PS/2 Model 56SX type 8556. Internal SCSI on the motherboard, supplies term/bus power.
[!NOTE]
The boot drive must be set up from scratch - Reference disk, FDISK, Format, and always set to ID 6. The System Partition on the boot drive appears to have some kind of check that makes the drive setup hardware specific. Hence, you don’t seem to be able to use an image (with System Partition) from a real harddrive and put it on the BlueSCSI and expect to boot from it. Also, never ever open a bootable image on a modern computer (use .hda in the image file name instead of .img which a modern OS might scan or preview)
Intel LP486E has SCSI controller on motherboard and secondary (?) built-in BIOS supports booting from single internal SCSI drive out of the box.
1 Install Zip Tools software in DOS and Windows to install all SCSI drivers, then use a utility such as Trantor SCSIWorks to add HDD and CD ROM capability. Ensure drive images are filled with 0s. Fdisk refused to format, used TFormat utility on SCSIWorks to format disk.
This 8-bit ISA adapter may not work out of the box and needs a newer BIOS (3.2 or 3.3) that can be obtained from minuszerodegrees.net and burned to an EPROM/EEPROM. Use the following bluescsi.ini settings to be able to boot from a disk image:
[SCSI]
EnableSCSI2=0 ; Off
[SCSI0]
HeadsPerCylinder=4 ; Any small value should work such as 4, 6, 8
For X68000 with SCSI interface
bluescsi.ini file settings[SCSI]
System="X68000-SCSI"
For X68000 with SASI interface (original/ACE/PRO (centronics 50 pin connector marked as “HARD DISK”))
bluescsi.ini file settings[SCSI]
System="X68000-SASI"
[!NOTE]
You may need to mount the drive on ID 3.
CPS3
There were several 1st party and 3rd parties’ SCSI interfaces for PC-9801 series, and the following setting was confirmed with IF-92B. But these specific requirements seem to be very common for the series as these values come from the fact SCSI BIOS requires geometry information obtained via non-standard SCSI commands, and most interfaces assume these values for 3rd party devices. Official boards may need Vendor=NEC in addition to the setting below. Note that each interface would have another size limit, e.g. IF-92B v1.10 firmware recognize only <1GB disk, and can use 512MB of it.
[SCSI]
System="Generic"
SectorsPerTrack=8
HeadsPerCylinder=32
Generated 2025-05-07