English fork of the Japanese RaSCSI project. RaSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices.
Go to file
2022-08-05 13:46:52 -05:00
.github Disable the rpi build for develop and master (#330) 2021-10-14 13:20:57 -07:00
doc Fixed missing media change handling (#690) 2022-02-21 21:01:17 +01:00
docs Merge Hw 2p4 to develop (#109) 2021-06-08 19:06:29 -05:00
hw Added Schematic PDF file and Step 3D model (#726) 2022-03-13 20:32:28 -05:00
python Fixes to README and easyinstall text (#787) 2022-08-05 09:30:20 -05:00
src #782 compiler interprets 08 as octal, which is invalid (#784) 2022-08-02 16:31:15 +02:00
test/robot Create new test cases for checking that the user can specify the TCP Port number (#154) 2021-07-27 18:40:00 -05:00
_config.yml Set theme jekyll-theme-midnight 2020-07-04 20:39:04 -05:00
.gitignore Added Schematic PDF file and Step 3D model (#726) 2022-03-13 20:32:28 -05:00
easyinstall.sh Fixes to README and easyinstall text (#787) 2022-08-05 09:30:20 -05:00
LICENSE Updated copyrights and versions 2021-10-29 21:55:24 -05:00
lido-driver.img improved HD creator with partioning and formatting Drive with HFS. (#51) 2020-11-07 18:10:09 -06:00
README.md Fix typo in README (#788) 2022-08-05 13:46:52 -05:00

What is RaSCSI Reloaded?

RaSCSI Reloaded is a virtual SCSI device emulator that runs on a Raspberry Pi. It runs in userspace, and can emulate several SCSI devices at one time. There is a control interface to attach / detach drives during runtime, as well as insert and eject removable media. This project is aimed at users of vintage Macintosh and Atari computers and more (see compatibility list) from the 1980's and 1990's.

Please check out the full story with much more detail on the wiki!

How do I contribute?

RaSCSI Reloaded is using the Gitflow Workflow. A quick overview:

  • The master branch should always reflect the contents of the last stable release
  • The develop branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
  • The rest of the feature branches are for developing new features
  • A tag will be created for each "release". The releases will be named .. where the release number is incremented for each subsequent release tagged in the same calendar month. The first release of the month of January 2021 is called "21.01.01", the second one in the same month "21.01.02" and so on.

Typically, releases will only be planned every few months.

I sell on Tindie

Github Sponsors

Thank you to all of the Github sponsors who support the development community!

Special thank you to the Gold level sponsors!

Special thank you to the Silver level sponsors!