News

SCSI2Pi is the most versatile SCSI/SASI emulation for the PiSCSI board, with a SCSI-to-USB bridge and numerous tools. SCSI2Pi profits from running on a full-fledged Linux. Specially configured SD cards or filesystems are not required. Images are simply copied to the Pi via the network. You control SCSI2Pi with the SCSI Control App, a web interface, or on the command line. Atari computers are especially well supported with the SCSI2Pi Client Tools.

The main changes in this version

• HDDRUTIL: A potential bug in HDDRUTIL 13.00 when copying a large number of sectors in one go (via the device window) has been fixed.
• HDDRUTIL: The integrated test suite has been extended.

The upgrade to HDDRIVER 13 is free for anyone who has purchased HDDRIVER 12 (full version or upgrade) since April.

Thank you to all the beta testers who invested a lot of time. HDDRIVER 13 has also been tested on not officially supported hardware, especially CT*, DFB1 and Raven. On these platforms, HDDRIVER sets benchmarks for transfer rates, so that you get even more enjoyment out of your fast processor and fast RAM.
Thanks to ETOS_FIX, many new (and old) features, including the ramdisk and fast data transfers, can also be used with EmuTOS.

The main changes in this version

• HDDRIVER: A next-generation ramdisk has been integrated. This ramdisk is a fully functional SCSI drive and supports the XHDI and SCSI Driver standards that are essential for the Atari. It can be up to 255 MiB in size, and is configurable in 1 MiB increments.
• HDDRIVER: Support of 32 bit DMA for faster SCSI transfers with the Suska-IV board with SCSI/DMA core. The availability of 32 bit DMA is detected automatically.
• HDDRIVER: Accelerated ACSI/SCSI transfers if data because of hardware limitations cannot be transferred directly to/from a memory address (STs and Falcons with Alternate-RAM, TTs with Alternate-RAM and ACSI devices), but must be copied via a buffer (_FRB).
• HDDRIVER: Further improved automatic IDE port detection, especially on not officially supported hardware.
• HDDRIVER: Improvements to the SCSI Driver, e.g. regarding the SCSI emulation for IDE drives.
• HDDRIVER: The module interface has proven its worth, so modules are now always executed, and not just optionally.
• HDDRIVER/HDDRUTIL: Extensive code review with numerous optimizations. HDDRIVER 13 is the most compact HDDRIVER in over 25 years: 25% smaller than HDDRIVER 7.93 despite a significantly larger feature set and additional hardware support.
• HDDRUTIL: Initializing partitions has been improved further. Just as when partitioning, the TOS compatiblity can now be set. Furthermore, entering the number of sectors per cluster and bytes per sector is now optional, which simplifies usage.
• HDDRUTIL: When splitting a medium into partitions, you can enter a maximum partition size. The default value is just below the maximum partition size of the current operating system, which simplifies creating partitions with maximum size.
• HDDRUTIL: When partitioning with a GPT scheme, the partitions are automatically aligned to 8 sector boundaries. This provides optimal performance, especially with memory cards, SSDs and modern hard drives.
• HDDRUTIL: The GPT partition editor provides for editing the GPT attributes as well as the start start sector and the sector count. 64 bit sector numbers are supported, so that partition tables for other platforms and large media can also be edited.
• HDDRUTIL: GPT partition entries can be added, removed, moved or sorted by their start sectors. This makes it possible to subsequently modify a partition layout without data loss on the unaffected partitions. The manual provides further information.
• HDDRUTIL: The GPT partition editor detects duplicate partition names and duplicate partition GUIDs.
• HDDRUTIL: When partitioning with a GPT, partitions for different platforms, such as TOS, Windows, macOS or Linux, can be created on the same medium. As before, HDDRUTIL automatically creates FAT16/FAT32 file systems for TOS and Windows partitions.
• HDDRUTIL: Improved support for gaps (placeholders) in a GPT.
• HDDRUTIL: The partition table can be exported to a text file instead of the clipboard, and additional data are exported
• HDDRUTIL: In the preferences, you can specify whether MBR or GPT is the default for the compatibility settings during partitioning.
• HDDRUTIL: With "Test Device/Driver" you can test devices and drivers for compatibility with important Atari standards without having to download the test suite separately. The tests are identical to those in the test suite and are open source.
• HDDRUTIL: "Unlock after Reset" and "Unpark after Reset" haben been combined into a single option.
• HDDRUTIL: Numerous improvements to support for media > 2 TiB.
• HDDRUTIL: Numerous user interface improvements.

The updated manual (PDF in the download archive of the full version) covers all changes. There is also a new demo version.

There is a new version of the free mass storage tool DISKUS. DISKUS is the Swiss Army knife for working with floppy disks, hard drives, and memory cards. Thanks to SCSI Driver support, it can access any mass storage device (ACSI, SCSI, IDE/SATA/ATAPI, USB, ...). With the SCSI Driver for Hatari and ARAnyM, you can even directly access mass storage devices connected to a Linux PC. The manual contains many tips for recovering lost data.

HDDRIVER is the ideal driver also for MiNT and therefore serves once again as the basis for the updated FreeMiNT OS Distro 26.2. This distribution is a drive image with an extensive software collection, which boots a snapshot of MiNT with the HDDRIVER demo version. For a full-fledged MiNT environment, simply replace the demo version with the full version.

ETOS_FIX replaces the EmuTOS hard drive support with a full-fledged driver of your choice, e.g. HDDRIVER, CBHD, HuSHI, ICD or AHDI. Furthermore, ETOS_FIX resolves several long known EmuTOS bugs that are not present in the listed drivers. With ETOS_FIX and HDDRIVER you can enjoy many HDDRIVER features, high speed and a wide range of supported devices also with EmuTOS.
My suggestion from some time ago that EmuTOS should allow TOS-compliant booting of external drivers did not meet with approval. Maybe the EmuTOS developers will reconsider this and will give the user a free choice. Ideally, ETOS_FIX will become obsolete sooner or later.