The presumably most important differences between SCSI2Pi and PiSCSI 24.04.01 are listed below.
| Feature | SCSI2Pi | PiSCSI | Remark |
|---|---|---|---|
| Installation/Update with apt package manager | ✅ | ❌ | Installation/Update without compiling in a matter of seconds, the optimized binaries are considerably smaller compared to PiSCSI |
| Binary development snapshots | ✅ | ❌ | For development versions binaries are provided regularly |
| scsiloop tool | ❌ | ✅ | Replaced by the considerably more powerful s2ptool |
| scsimon tool | ❌ | ✅ | Removed because a lot of data are lost (a Pi's GPIO port is too slow) |
| Up to 25% higher transfer rates | ✅ | ❌ | Measured with a Pi Zero WH (25%) and a Pi 4 (5%) |
| SASI hard drive support | ✅ | ❌ | SASI hard drive emulation, including backup/restore |
| Tape drive (streamer) support | ✅ | ❌ | Streamer emulation, with tar files as image files (SIMH files are work in progress) |
| SCSI-to-USB bridge support | ✅ | ❌ | Since SCSI2Pi 5.0 |
| Improved DaynaPort emulation, improved DaynaPort bridge |
✅ | ❌ | About 16 MB less memory consumption (important for small Pis), support for several DaynaPort emulations in the same network, creating the DaynaPort bridge can be switched off |
| Linked SCSI command support | ✅ | ❌ | Affects s2p and s2pexec |
| Flexible block sizes (in multiples of 4) | ✅ | ❌ | For exotic platforms |
| Properties and property files | ✅ | ❌ | Comfortable configuring of all settings without a command line |
| BlueSCSI compatiblity mode | ✅ | ❌ | Support of the BlueSCSI filename conventions for images |
| Configurable caching modes | ✅ | ❌ | A write-through cache, for instance, ensures always consistent image files |
| Configurable and additional mode pages | ✅ | ❌ | User-definable mode pages for optimal driver/platform compatibility |
| Improved initiator mode | ✅ | ❌ | Higher compatibility with the SCSI standard, new and improved tools |
| Scripting support | ✅ | ❌ | s2pctl and s2pexec can execute command scripts |
| API for management with SCSI commands | ✅ | ❌ | The connected computer can control SCSI2Pi with SCSI commands |
| Improved and extended logging | ✅ | ❌ | Improved error analysis capabilities |
| Optional compilation of device types | ✅ | ❌ | Faster compilation and even smaller binaries, if not all device types are needed |
| Since SCSI2Pi 5.0: Tool for formatting USB drives | ✅ | ❌ | E.g. for USB floppy disk drives, runs on any Linux system |
| Since SCSI2Pi 5.0: Tool for analyzing and creating tape images | ✅ | ❌ | Supports SIMH-compatible tape image files, runs on any Linux system |
| Tool for sending SCSI or SASI commands | ✅ | ❌ | Sends any command to a device, the results are displayed or saved |
| Tools for advanced testing | ✅ | ❌ | SCSI commands can be tested without Pi hardware on a Linux/BSD-PC or Mac |
| Programs can be launched without sudo | ✅ | ❌ | When installing the binary packages or after sudo make install |
| Additional functions for the SCSI Control App | ✅ | ❌ | SCSI Control since version 5.1 offers additional features |
The SCSI2Pi news provide information on more new features.
Several PiSCSI tickets existing for a long time (bugs and requests for enhancement) have been addressed by SCSI2Pi.
| PiSCSI Ticket | Remark |
|---|---|
| 335 | Improved caching, optional write-through cache |
| 479 | Improved support of the SCSI commands READ/WRITE LONG |
| 480 | Tape drive (streamer) support |
| 497 | SCSI-to-USB bridge |
| 598 | Dynamic MAC address for the DaynaPort, for more than one DaynaPort in the same network |
| 740 | Installation packages with binaries, installation without compiling |
| 809 | Support for SASI hard drives |
| 1098 | Evaluation of Daynaport support for NetBSD |
| 1260 | Consistent code formatting and conventions |
| 1331 | DaynaPort bridge for Bookworm |
| 1402, 1410, 1412 | DEC Alpha compatibility, abandoned in PiSCSI |