diff --git a/AFP-File-Sharing.mediawiki b/AFP-File-Sharing.mediawiki index ecdf157..40e5dcd 100644 --- a/AFP-File-Sharing.mediawiki +++ b/AFP-File-Sharing.mediawiki @@ -1,6 +1,6 @@ = Overview = -AFP is Apple's legacy file sharing protocol, originally standing for AppleTalk Filing Protocol. This is what classic Mac OS as well as earlier versions of Mac OS X (until 10.8) uses for file sharing. On this page, we will be using an open source implementation of an AFP server called [http://netatalk.sourceforge.net/ Netatalk] to set up a file sharing server running in parallel with RaSCSI on a Raspberry Pi. +AFP is Apple's legacy file sharing protocol, originally standing for AppleTalk Filing Protocol. This is what classic Mac OS as well as earlier versions of Mac OS X (until 10.8) uses for file sharing. On this page, we will be using an open source implementation of an AFP server called [http://netatalk.sourceforge.net/ Netatalk] to set up a file sharing server running in parallel with PiSCSI on a Raspberry Pi. As of RaSCSI 21.11.1, the RaSCSI Web Interface has integration with Netatalk built into the UI, allowing you to easily see the status of the AFP service running on your Pi, as well as downloading files directly onto the shared directory to make them instantly accessible to Macs that have mounted the AppleShare file system. @@ -12,7 +12,7 @@ As of RaSCSI 21.11.1, the RaSCSI Web Interface has integration with Netatalk bui '''Note:''' The following process has been automated through the ''easyinstall.sh'' script. If you don't want to use the script, follow the manual steps below. -This section assumes that you have already installed RaSCSI and therefore have the dependent libraries on your Pi. We will need a few more libraries installed. +This section assumes that you have already installed PiSCSI and therefore have the dependent libraries on your Pi. We will need a few more libraries installed. ``` $ sudo apt install libssl-dev libdb-dev libcups2-dev libavahi-client-dev libgcrypt20-dev autotools-dev automake libtool diff --git a/Benchmarks.md b/Benchmarks.md index 5d092e3..17fcbef 100644 --- a/Benchmarks.md +++ b/Benchmarks.md @@ -1,5 +1,5 @@ # Overview -Below are some benchmarks comparing the RaSCSI running on different variants of Raspberry Pi's, along with the SCSI2SD version 5 and an original Apple hard drive as a comparison. +Below are some benchmarks comparing the PiSCSI running on different variants of Raspberry Pi's, along with the SCSI2SD version 5 and an original Apple hard drive as a comparison. # Test results ## Overall Disk scores @@ -7,7 +7,7 @@ Below are some benchmarks comparing the RaSCSI running on different variants of _Some notes on this:_ * _There are multiple SCSI2SD scores. I ran the test on two different volumes on the SCSI2SD and got slightly different scores._ -* _I suspect that the Pi 0 got higher scores because the RaSCSI software only uses one core. This gives the Pi 0 a slight clock speed advantage_ +* _I suspect that the Pi 0 got higher scores because the PiSCSI software only uses one core. This gives the Pi 0 a slight clock speed advantage_ ## Disk Read Scores [[images/benchmark_read.png|Disk Read Benchmark]] @@ -25,26 +25,26 @@ Macintosh Quadra 840av * Drive cache configured at 128KB * Norton System Info 3.5 [Part of Norton Utilities](http://macintoshgarden.org/apps/norton-utilities-353) -## RaSCSI - Raspberry Pi 4 +## PiSCSI - Raspberry Pi 4 * 1.5GHz ARM Cortex-A72 - Quad core * 4GB RAM * Samsung 32GB EVO Plus SD Card * Raspberry Pi OS - 2020-05-27-raspios-buster-full-armhf -* RaSCSI - akuker version 1.5 - [[https://github.com/akuker/RASCSI-68kmlaver/tree/dual_connector]] +* PiSCSI - piscsi version 1.5 - [[https://github.com/akuker/RASCSI-68kmlaver/tree/dual_connector]] -## RaSCSI - Raspbery Pi 2 +## PiSCSI - Raspbery Pi 2 * 900MHz ARM Cortex 7 - Quad core * 1GB RAM * Samsung 32GB EVO Plus SD Card * Raspberry Pi OS - 2020-05-27-raspios-buster-full-armhf -* RaSCSI - akuker version 1.5 - [[https://github.com/akuker/RASCSI-68kmlaver/tree/dual_connector]] +* PiSCSI - piscsi version 1.5 - [[https://github.com/piscsi/RASCSI-68kmlaver/tree/dual_connector]] -## RaSCSI - Raspberry Pi Zero +## PiSCSI - Raspberry Pi Zero * 1GHz ARM11 - Single core * 512MB RAM * Samsung 32GB EVO Plus SD Card * Raspberry Pi OS - 2020-05-27-raspios-buster-full-armhf -* RaSCSI - akuker version 1.5 - [[https://github.com/akuker/RASCSI-68kmlaver/tree/dual_connector]] +* PiSCSI - piscsi version 1.5 - [[https://github.com/piscsi/RASCSI-68kmlaver/tree/dual_connector]] ## SCSI2SD * Version v5.0a - [[http://inertial.biz/index.php?title=SCSI2SD]] diff --git a/Compatibility.mediawiki b/Compatibility.mediawiki index ab80e69..25c9001 100644 --- a/Compatibility.mediawiki +++ b/Compatibility.mediawiki @@ -1,11 +1,11 @@ -= RaSCSI Reloaded Compatibility details = += PiSCSI Reloaded Compatibility details = -Below you will find information around the various compatibility aspects of the RaSCSI hardware and software. As the project is under active development, this page will get frequent updates. As much as the page lists systems that work with RaSCSI, configurations listed do not indicate an guarantee on the setup, just that someone just like you has tested and verified it works for them. +Below you will find information around the various compatibility aspects of the PiSCSI hardware and software. As the project is under active development, this page will get frequent updates. As much as the page lists systems that work with PiSCSI, configurations listed do not indicate an guarantee on the setup, just that someone just like you has tested and verified it works for them. __TOC__ = Raspberry Pi compatibility = -RaSCSI has been tested with several Raspberry Pi models. +PiSCSI has been tested with several Raspberry Pi models. {| class="wikitable" ! scope="col"| Raspberry Pi model @@ -38,17 +38,17 @@ RaSCSI has been tested with several Raspberry Pi models. Any Raspberry Pi with a 40-pin connector should work fine. For the best performance, use a Raspberry Pi 4 with a fast SD card. Please be mindful of cooling your RPi, as the CPU clock may fluctuate due to the influence of heat, leading to unreliable operation. It is also recommended to run your RPi system without a desktop environment, e.g. the ''Lite'' version of Raspberry Pi OS. -The RaSCSI software does not have any special software requirements beyond a Linux OS with root access. It should run on most standard Linux distributions, but testing is performed against [https://www.raspberrypi.org/downloads/raspberry-pi-os/ Raspberry Pi OS] (formerly called Raspbian). +The PiSCSI software does not have any special software requirements beyond a Linux OS with root access. It should run on most standard Linux distributions, but testing is performed against [https://www.raspberrypi.org/downloads/raspberry-pi-os/ Raspberry Pi OS] (formerly called Raspbian). -'''Note:''' RaSCSI is primarily used on 32-bit operating systems, but it has been proven to work with 64-bit too. +'''Note:''' PiSCSI is primarily used on 32-bit operating systems, but it has been proven to work with 64-bit too. = System compatibility = -This table contains the various systems RaSCSI has been tested with, and the test results. It also includes if the system was bootable from the RaSCSI presented SCSI disk. +This table contains the various systems PiSCSI has been tested with, and the test results. It also includes if the system was bootable from the PiSCSI presented SCSI disk. {| class="wikitable" ! scope="col"| System ! scope="col"| Tested and working? -! scope="col"| Bootable from RaSCSI? +! scope="col"| Bootable from PiSCSI? ! scope="col"| Software version |- |Acorn RISC PC w/ Eesox Fast SCSI II (RISC OS 3.70/4.39) @@ -77,7 +77,7 @@ This table contains the various systems RaSCSI has been tested with, and the tes |22.05.01 |- |Apple Macintosh Plus -|✅ (Use [https://github.com/akuker/RASCSI/wiki/Drive-Setup#Initializing_a_new_disk_on_Classic_Mac_OS Silverlining drivers]) +|✅ (Use [https://github.com/piscsi/PiSCSI/wiki/Drive-Setup#Initializing_a_new_disk_on_Classic_Mac_OS Silverlining drivers]) |✅ |22.07.02 |- @@ -278,7 +278,7 @@ This table contains the various systems RaSCSI has been tested with, and the tes |- |Sun SPARCstation IPC & IPX |✅ -|✅ ([https://github.com/akuker/RASCSI/issues/618#issuecomment-1017618751 workaround] for CD-ROMs) +|✅ ([https://github.com/piscsi/PiSCSI/issues/618#issuecomment-1017618751 workaround] for CD-ROMs) |21.12.1 |- |Sun SPARCStation 5/10 @@ -312,30 +312,30 @@ This table contains the various systems RaSCSI has been tested with, and the tes If you're looking to add a new system to the System compatibility list, please perform the following tests. The following items are considered the bare minimum of functionality, and should work on other systems with your same configuration. -'''Note:''' If you are testing RaSCSI on a digital sampler, please update the [[RaSCSI for Hardware Samplers#compatibility|Sampler Compatibility]] section instead. +'''Note:''' If you are testing PiSCSI on a digital sampler, please update the [[PiSCSI for Hardware Samplers#compatibility|Sampler Compatibility]] section instead. == Tested and Working == To be considered '''Tested and working''', please test and confirm the following functions work, and are working consistently. -The following steps require attaching a Hard Drive image with RaSCSI and presenting it on a SCSI ID. +The following steps require attaching a Hard Drive image with PiSCSI and presenting it on a SCSI ID. -'''1.''' With a Hard Drive image mounted in RaSCSI, can your system (computer, sampler, etc) see the SCSI ID presented from RaSCSI? +'''1.''' With a Hard Drive image mounted in PiSCSI, can your system (computer, sampler, etc) see the SCSI ID presented from PiSCSI? -'''2.''' Are you able to mount the RaSCSI presented SCSI disk in the operating system on your system? +'''2.''' Are you able to mount the PiSCSI presented SCSI disk in the operating system on your system? -'''3.''' Are you able to format the RaSCSI presented SCSI disk? +'''3.''' Are you able to format the PiSCSI presented SCSI disk? -'''4.''' Are you able to successfully read files from the RaSCSI presented SCSI disk? +'''4.''' Are you able to successfully read files from the PiSCSI presented SCSI disk? -'''5.''' Are you able to successfully write files from the RaSCSI presented SCSI disk? +'''5.''' Are you able to successfully write files from the PiSCSI presented SCSI disk? -== Bootable from RaSCSI == +== Bootable from PiSCSI == -To be considered '''Bootable from RaSCSI''', please test and confirm the following functions work, and are working consistently. +To be considered '''Bootable from PiSCSI''', please test and confirm the following functions work, and are working consistently. -'''1.''' If possible, confirm that your system will boot its main operating system from the RaSCSI. This may not be possible as not all configurations have the ability to boot from a SCSI device. +'''1.''' If possible, confirm that your system will boot its main operating system from the PiSCSI. This may not be possible as not all configurations have the ability to boot from a SCSI device. = See Also = -* [[RaSCSI for Hardware Samplers#compatibility|Sampler Compatibility]] +* [[PiSCSI for Hardware Samplers#compatibility|Sampler Compatibility]] * [https://github.com/rdmark/RASCSI-X68k/wiki#Compatibility Japanese Home Computer Compatibility] (RaSCSI-X68k) \ No newline at end of file diff --git a/Connecting-the-RaSCSI.mediawiki b/Connecting-the-RaSCSI.mediawiki index 9c2a2d8..0ddaf42 100644 --- a/Connecting-the-RaSCSI.mediawiki +++ b/Connecting-the-RaSCSI.mediawiki @@ -1,59 +1,59 @@ -= Connecting your RaSCSI board to a computer = += Connecting your PiSCSI board to a computer = -This document discusses status indicators, termination, and connecting the RaSCSI board to a computer. The following examples will focus on older Macintosh computers, but the RaSCSI is not Mac specific. At it's heart, the RaSCSI software can talk with SCSI controllers on any SCSI bus. You could connect it to Sun workstations, Amiga computers, audio samplers, keyboards, servers, or any number of other devices. We can't test and document every system, but don't let that stop you from experimenting on your own. +This document discusses status indicators, termination, and connecting the PiSCSI board to a computer. The following examples will focus on older Macintosh computers, but the PiSCSI is not Mac specific. At it's heart, the PiSCSI software can talk with SCSI controllers on any SCSI bus. You could connect it to Sun workstations, Amiga computers, audio samplers, keyboards, servers, or any number of other devices. We can't test and document every system, but don't let that stop you from experimenting on your own. __TOC__ = What are all these green lights? = -The RaSCSI is outfitted with four green LEDs. They are used as diagnostic tools, with one doubling as an activity indicator. +The PiSCSI is outfitted with four green LEDs. They are used as diagnostic tools, with one doubling as an activity indicator. Depending which model of board, the status LEDs will be in different locations. Regardless of their location, they are used to monitor the following. * 3.3 volt power * 5 volt power -* ENB/DBG - monitoring if the RaSCSI software is running. On version 2.1 and newer boards are labelled ENB, and older boards label this as DBG. -* ACT - flashes when images presented via RaSCSI are being accessed on the SCSI bus +* ENB/DBG - monitoring if the PiSCSI software is running. On version 2.1 and newer boards are labelled ENB, and older boards label this as DBG. +* ACT - flashes when images presented via PiSCSI are being accessed on the SCSI bus -The '''3v''' and '''5v''' LEDs should be lit at all times when the RaSCSI is connected to the Raspberry Pi, and the Pi powered up, +The '''3v''' and '''5v''' LEDs should be lit at all times when the PiSCSI is connected to the Raspberry Pi, and the Pi powered up, -The '''ENB/DNG''' LED will only illuminate when the RaSCSI daemon is running. During the initial setup, this LED will not illuminate until the RaSCSI software is installed and running. +The '''ENB/DNG''' LED will only illuminate when the PiSCSI daemon is running. During the initial setup, this LED will not illuminate until the PiSCSI software is installed and running. -The '''ACT''' LED flashes only when images presented via RaSCSI are being accessed, and will otherwise stay dark. +The '''ACT''' LED flashes only when images presented via PiSCSI are being accessed, and will otherwise stay dark. = Understanding the SCSI bus = No need to re-write what many other sites have already covered. [https://computer.howstuffworks.com/scsi.htm This howstuffworks article] gives a good breakdown of the SCSI bus, controllers, connectors and other useful information. -The RaSCSI software and hardware work together to emulate one or more SCSI devices and present them to the SCSI bus. The upside to using software for this emulation is the ability to present multiple devices on the SCSI bus from a single piece of hardware. Where SCSI devices typically present a single SCSI ID, RaSCSI can present multiple. Examples of this are covered under [[Drive Setup]]. +The PiSCSI software and hardware work together to emulate one or more SCSI devices and present them to the SCSI bus. The upside to using software for this emulation is the ability to present multiple devices on the SCSI bus from a single piece of hardware. Where SCSI devices typically present a single SCSI ID, PiSCSI can present multiple. Examples of this are covered under [[Drive Setup]]. = Termination = If you haven't already, take a quick read through the [https://computer.howstuffworks.com/scsi.htm This howstuffworks] article, making sure to cover the section on [https://computer.howstuffworks.com/scsi.htm#pt4 Termination]. -The SCSI terminators on the RaSCSI board can be turned on or off. Depending on the version of your RaSCSI board, this is handled by jumpers or switches. +The SCSI terminators on the PiSCSI board can be turned on or off. Depending on the version of your PiSCSI board, this is handled by jumpers or switches. On a version 2.1 or newer boards, you enable termination by moving '''both''' switches 1 and 2 the two ON position. To disable termination, move '''both''' switches 1 and 2 away from the ON position. The switch is also labelled '''Term Enable''' on the silkscreen. On a version 1.6 or older boards, you enable termination by putting jumpers on '''JP1''' and '''JP2'''. To disable termination, remove jumpers from '''both''' '''JP1''' and '''JP2'''. They are also marked with '''Terminator Enable''' on the silkscreen. -If your RaSCSI board is the final device on the SCSI chain, you enable termination. If your RaSCSI board is plugged into the middle of a SCSI chain, disable termination. +If your PiSCSI board is the final device on the SCSI chain, you enable termination. If your PiSCSI board is plugged into the middle of a SCSI chain, disable termination. = Using different connectors = -These RaSCSI boards provide both a DB-25 interface for external SCSI connections, and a 50 pin interface for internal SCSI connections. You could easily mount the RaSCSI attached to your Raspberry Pi inside the computer, and connect the 50 pin SCSI interface to the internal cabling on your computer. +These PiSCSI boards provide both a DB-25 interface for external SCSI connections, and a 50 pin interface for internal SCSI connections. You could easily mount the PiSCSI attached to your Raspberry Pi inside the computer, and connect the 50 pin SCSI interface to the internal cabling on your computer. -As this project was aimed at older Apple Macintosh computers, and those computers use a DB-25 interface for SCSI connections, the PCB design uses a DB-25 connector. However, not all systems use DB-25 connectors for their SCSI interface. Apple PowerBook laptops of the same era use an HDI-30 connector for which there are adapters available online. You could also purchase adapters to use the RaSCSI with Centronics 50pin or 68 pin SCSI connectors. Using adapters in this manner is untested, but should work. +As this project was aimed at older Apple Macintosh computers, and those computers use a DB-25 interface for SCSI connections, the PCB design uses a DB-25 connector. However, not all systems use DB-25 connectors for their SCSI interface. Apple PowerBook laptops of the same era use an HDI-30 connector for which there are adapters available online. You could also purchase adapters to use the PiSCSI with Centronics 50pin or 68 pin SCSI connectors. Using adapters in this manner is untested, but should work. = Just plug it in? = -With the RaSCSI attached to your Raspberry Pi, and the Mac computer turned off, connect the RaSCSI board to your Mac. This may require a short cable to attach the two. Many people are using 3' (90cm) or 6' (180cm) DB-25 Male to Male cables for this connection. Visit your favourite electronics retailer for this if you don't have one already. +With the PiSCSI attached to your Raspberry Pi, and the Mac computer turned off, connect the PiSCSI board to your Mac. This may require a short cable to attach the two. Many people are using 3' (90cm) or 6' (180cm) DB-25 Male to Male cables for this connection. Visit your favourite electronics retailer for this if you don't have one already. Once connected, you can power up the Macintosh. = Accessories you can use = == External SCSI Cables == -The most common approach in connecting your RaSCSI to a Macintosh will be with a Male to Male DB25 SCSI cable. Make sure that any cable you buy is marked as SCSI (not Parallel) or IEEE-1284 compliant. These cables connect to the DB25 port on the RaSCSI board, and to the back of most Macs manufactured prior to 1998. Using these cables are ideal if you want to use the RaSCSI as an external drive. A cheap option are these [https://www.amazon.com/Monoprice-3-Feet-Molded-Cable-101582/dp/B002HWNS58/ Monoprice cables]. Again, just ensure you have the correct cable before attempting to use them. If you want to use the RaSCSI with a PowerBook that has a HDI30 port, you will need a DB25 to HDI30 adapter, [https://www.monoprice.com/product?p_id=552 like this one]. +The most common approach in connecting your PiSCSI to a Macintosh will be with a Male to Male DB25 SCSI cable. Make sure that any cable you buy is marked as SCSI (not Parallel) or IEEE-1284 compliant. These cables connect to the DB25 port on the PiSCSI board, and to the back of most Macs manufactured prior to 1998. Using these cables are ideal if you want to use the PiSCSI as an external drive. A cheap option are these [https://www.amazon.com/Monoprice-3-Feet-Molded-Cable-101582/dp/B002HWNS58/ Monoprice cables]. Again, just ensure you have the correct cable before attempting to use them. If you want to use the PiSCSI with a PowerBook that has a HDI30 port, you will need a DB25 to HDI30 adapter, [https://www.monoprice.com/product?p_id=552 like this one]. Some additional options that have been tested are: @@ -61,10 +61,10 @@ Some additional options that have been tested are: * [https://www.ebay.com/itm/292770514237 Cablesonline.net] == Internal SCSI Cables == -The internal ribbon cables required for connecting your RaSCSI to the internal connector are typically included in any Macintosh that supports this option. However, if not included you need cables [https://www.amazon.com/PC-Accessories-Connectors-Inches-Internal/dp/B01EHB2YVK/ such as these]. +The internal ribbon cables required for connecting your PiSCSI to the internal connector are typically included in any Macintosh that supports this option. However, if not included you need cables [https://www.amazon.com/PC-Accessories-Connectors-Inches-Internal/dp/B01EHB2YVK/ such as these]. -== Powering the RaSCSI Internally == -If you decide to mount your RaSCSI inside your Macintosh, you will need a way to power it. Luckily, Molex to USB cables exist and will do the trick. The cable tested for this wiki article is [https://www.amazon.com/CRJ-4-Pin-Female-Sleeved-Adapter/dp/B07FK7TJG1/ available here]. The Macintosh's power supply has enough juice to power both the Raspberry Pi and RaSCSI with just one cable. +== Powering the PiSCSI Internally == +If you decide to mount your PiSCSI inside your Macintosh, you will need a way to power it. Luckily, Molex to USB cables exist and will do the trick. The cable tested for this wiki article is [https://www.amazon.com/CRJ-4-Pin-Female-Sleeved-Adapter/dp/B07FK7TJG1/ available here]. The Macintosh's power supply has enough juice to power both the Raspberry Pi and PiSCSI with just one cable. = Everything is connected, what next? = diff --git a/Dayna-Port-Command-Set.md b/Dayna-Port-Command-Set.md index b61f52d..3554272 100644 --- a/Dayna-Port-Command-Set.md +++ b/Dayna-Port-Command-Set.md @@ -5,7 +5,7 @@ The current version is made available under [Creative Commons BY-SA](https://creativecommons.org/licenses/by-sa/4.0/legalcode). For additional information, see the end of this document. Some reference data captures are available here: -https://github.com/akuker/RASCSI/tree/daynaport/doc/data_captures/daynaport +https://github.com/piscsi/PiSCSI/tree/daynaport/doc/data_captures/daynaport # SCOPE This document applies to the following hardware devices: @@ -287,4 +287,4 @@ The original revision history of this document follows: - Version 1.10 (22/April/2005) Added description of 'Set Interface Mode/Set MAC Address' command - Version 1.20 (16/July/2005) Corrected description of 'Set Interface Mode/Set MAC Address' command -The current version history of this document is maintained in the RaSCSI Github Wiki at: https://github.com/akuker/RASCSI/wiki/Dayna-Port-Command-Set \ No newline at end of file +The current version history of this document is maintained in the PiSCSI Github Wiki at: https://github.com/piscsi/piscsi/wiki/Dayna-Port-Command-Set \ No newline at end of file diff --git a/Dayna-Port-SCSI-Link.md b/Dayna-Port-SCSI-Link.md index 8d4bed3..59caba5 100644 --- a/Dayna-Port-SCSI-Link.md +++ b/Dayna-Port-SCSI-Link.md @@ -1,5 +1,5 @@ # DaynaPort SCSI/Link Ethernet -RaSCSI has the ability to emulate a DaynaPort SCSI/Link device. This allows for a host to connect to a local area network through the Raspberry Pi's network connection (either wired or wireless) +PiSCSI has the ability to emulate a DaynaPort SCSI/Link device. This allows for a host to connect to a local area network through the Raspberry Pi's network connection (either wired or wireless)
@@ -14,7 +14,7 @@ Depending upon which use case matches your situation, the Raspberry Pi configura
## Automated Setup
-- Download and install latest version of RaSCSI by following the [[setup instructions]].
+- Download and install latest version of PiSCSI by following the [[setup instructions]].
- Run the network bridge setup script for wired or wireless:
@@ -23,7 +23,7 @@ Depending upon which use case matches your situation, the Raspberry Pi configura
./easyinstall.sh # Select option 6 to configure wired, and 7 to configure wireless bridge
```
-- Let the Pi reboot, and attach a DaynaPORT adapter to your RaSCSI as instructed in the script
+- Let the Pi reboot, and attach a DaynaPORT adapter to your PiSCSI as instructed in the script
## Manual Setup
If you're *not* using easyinstall.sh to configure the network bridge, you can follow the manual steps below.
@@ -40,7 +40,7 @@ In this section, we're going to reconfigure the network so that eth0 is just an
- Copy the bridge configuration to `/etc/network/interfaces.d/`
- ```sudo cp ~/RASCSI/src/raspberrypi/os_integration/rascsi_bridge /etc/network/interfaces.d/```
+ ```sudo cp ~/PiSCSI/src/raspberrypi/os_integration/rascsi_bridge /etc/network/interfaces.d/```
- Modify the `/etc/dhcpcd.conf` file to add the following line at the bottom
@@ -63,12 +63,12 @@ bridge name bridge id STP enabled interfaces
rascsi_bridge 8000.869bacd8de6f no eth0
```
-- After you create/attach the daynaport in Rascsi, you should be able to see a "ras0" interface attached to the bridge. Run 'brctl show' on Linux to validate this. (Note the formatting may be garbled on your terminal)
+- After you create/attach the daynaport in Rascsi, you should be able to see a "piscsi0" interface attached to the bridge. Run 'brctl show' on Linux to validate this. (Note the formatting may be garbled on your terminal)
```
pi@rascsi:~ $ brctl show
bridge name bridge id STP enabled interfaces
rascsi_bridge 8000.869bacd8de6f no eth0
- ras0
+ piscsi0
```
@@ -104,7 +104,7 @@ sudo apt-get install iptables-persistent
Reboot the Pi
-Note that unlike the wired configuration above, RaSCSI will stand up the rascsi_bridge interface automatically when you attach the DaynaPORT device, so there is no need to copy over the interface config file to interfaces.d .
+Note that unlike the wired configuration above, PiSCSI will stand up the rascsi_bridge interface automatically when you attach the DaynaPORT device, so there is no need to copy over the interface config file to interfaces.d .
On the Mac side, in the TCP/IP or MacTCP control panel choose Manual and input:
* IP address 10.10.20.2
@@ -117,35 +117,35 @@ On the Mac side, in the TCP/IP or MacTCP control panel choose Manual and input:
**Note:** AppleTalk/DDP won't work to communicate with other devices on the network with this configuration, but TCP will work fine.
-# Attach a DaynaPORT adapter to your RaSCSI configuration
+# Attach a DaynaPORT adapter to your PiSCSI configuration
There are four ways to accomplish this:
1. Launch 'rascsi' with parameters on the command line (when not running as a service)
2. Edit the rascsi.service configuration to attach devices on launch (when running as a service)
-3. Use 'rasctl' to dynamically attach the device on a running rascsi instance
+3. Use 'scsictl' to dynamically attach the device on a running rascsi instance
4. Use the [[web interface]] to attach the device
Note that by default, the DaynaPORT device will launch with parameters 'eth0,wlan0' meaning it will attempt to use eth0 first, and if unavailable then wlan0. Also, note that the default IP address / netmask is 10.10.20.1/24. So for most usecases, if you follow the automated process and use the default values, you don't have to specify any parameters when attaching the DaynaPORT device and it should work out of the box.
-Ex. with rascsi / wired / DHCP, RaSCSI *not* running as a service
+Ex. with rascsi / wired / DHCP, PiSCSI *not* running as a service
```sudo rascsi -ID 6 -t scdp eth0```
-Ex. with rasctl / wired / DHCP, RaSCSI already running
-```rasctl -i 6 -c attach -t scdp -f eth0```
+Ex. with scsictl / wired / DHCP, PiSCSI already running
+```scsictl -i 6 -c attach -t scdp -f eth0```
-Ex. with rascsi / wireless / static IP, RaSCSI *not* running as a service
+Ex. with rascsi / wireless / static IP, PiSCSI *not* running as a service
```sudo rascsi -ID 6 -t scdp wlan0:10.10.20.1/24```
-Ex. with rasctl / wireless / static IP, RaSCSI already running
-```rasctl -i 6 -c attach -t scdp -f wlan0:10.10.20.1/24```
+Ex. with scsictl / wireless / static IP, PiSCSI already running
+```scsictl -i 6 -c attach -t scdp -f wlan0:10.10.20.1/24```
-## **(Optional)** Configure RaSCSI to start up with your DaynaPORT configuration
+## **(Optional)** Configure PiSCSI to start up with your DaynaPORT configuration
-Here you have two options. Either have the RaSCSI Web UI read your *default* configuration file on startup, or hard code the launch parameters in the rascsi.service ExecStart argument. The latter is more permanent, while the former can be managed more easily through the Web UI. Also note that the Web UI configuration will override whatever is defined in rascsi.service.
+Here you have two options. Either have the PiSCSI Web UI read your *default* configuration file on startup, or hard code the launch parameters in the rascsi.service ExecStart argument. The latter is more permanent, while the former can be managed more easily through the Web UI. Also note that the Web UI configuration will override whatever is defined in rascsi.service.
- Web UI configuration option:
-Once you've attached your DaynaPORT device with just the right parameters, you can save that as a RaSCSI Web UI configuration file. If you name it *default* (~/.config/rascsi/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
+Once you've attached your DaynaPORT device with just the right parameters, you can save that as a PiSCSI Web UI configuration file. If you name it *default* (~/.config/rascsi/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
- rascsi.service ExecStart option:
Modify your service startup script to automatically add the DaynaPort at startup. To do this, open `/etc/systemd/system/rascsi.service` with a text editor. Modify the ExecStart line to add the ID and device. For example:
@@ -176,7 +176,7 @@ MacTCP is your only option if you want to get your Mac with a 68000 or 68020 CPU
- Download [MacTCP 2.0.6](https://macintoshgarden.org/apps/mactcp-206) and apply the unofficial 2.1 patch, then move it into the Extensions folder (SSW 7.0+) or in the root of the System Folder (SSW 6.0.x or earlier)
- Download and install the [DaynaPort 7.5.3 Drivers](https://macintoshgarden.org/apps/daynaport-drivers)
- Reboot your Macintosh
-- Open up the MacTCP control panel and configure it with a static IP address matching the rascsi_bridge configuration on your RaSCSI
+- Open up the MacTCP control panel and configure it with a static IP address matching the rascsi_bridge configuration on your PiSCSI
-- Example below for when rascsi_bridge is set to 10.10.20.1, and using Google Public DNS servers
- Reboot your Macintosh again
- Test your network connection with [MacTCP Ping](https://macintoshgarden.org/apps/mactcp-ping) by f.e. pinging a DNS server (8.8.8.8)
@@ -223,7 +223,7 @@ After you click Continue, it may take a few seconds for the diagnostics to run.
Another excellent troubleshooting tool it Apple's [OTTool 1.2.1](https://macintoshgarden.org/sites/macintoshgarden.org/files/apps/OTTool_1.2.1.sit). It requires Open Transport 1.3 to be installed, provides detailed information about the network interface, and has several built-in features for domain name resolution, ping, traceroute, etc.
-One way to know that your DaynaPort interface is set up correctly locally, is that OTTool shows that the interface has been assigned an IP address. That helps you eliminate other problems such as bridge or NAT configuration on the RaSCSI host.
+One way to know that your DaynaPort interface is set up correctly locally, is that OTTool shows that the interface has been assigned an IP address. That helps you eliminate other problems such as bridge or NAT configuration on the PiSCSI host.
# Atari ST/TT/Falcon Setup Instructions
diff --git a/Drive-Setup.mediawiki b/Drive-Setup.mediawiki
index c0a6179..960ff7d 100644
--- a/Drive-Setup.mediawiki
+++ b/Drive-Setup.mediawiki
@@ -1,12 +1,12 @@
= Creating and attaching disk images =
-This section digs into creating hard drive images, checking SCSI IDs, and presenting images with RaSCSI. This document assumes you have completed the [[Full Size RaSCSI Assembly|full size]] or [[RaSCSI Zero Assembly|Zero]] assembly of your RaSCSI (if needed), have the software covered in the [[Setup Instructions]] page and connected your RaSCSI as described in the [[Connecting the RaSCSI]] instructions. If you're starting here, consider checking those documents before proceeding.
+This section digs into creating hard drive images, checking SCSI IDs, and presenting images with PiSCSI. This document assumes you have completed the [[Full Size PiSCSI Assembly|full size]] or [[PiSCSI Zero Assembly|Zero]] assembly of your PiSCSI (if needed), have the software covered in the [[Setup Instructions]] page and connected your PiSCSI as described in the [[Connecting the PiSCSI]] instructions. If you're starting here, consider checking those documents before proceeding.
__TOC__
= Creating and attaching an empty SCSI hard drive image =
-Boiled down, RaSCSI simply presents one or more files on the Raspberry PI file system as SCSI Disks. So you will create or already have a file somewhere on your Raspberry Pi, use rasctl to presents it as a disk on the SCSI Bus, then your computer treats it like a hard drive, MO disk, CD Rom, etc. This document talks about creating images, presenting them with RaSCSI on the SCSI Bus, and how to use them on your target computer.
+Boiled down, PiSCSI simply presents one or more files on the Raspberry PI file system as SCSI Disks. So you will create or already have a file somewhere on your Raspberry Pi, use scsictl to presents it as a disk on the SCSI Bus, then your computer treats it like a hard drive, MO disk, CD Rom, etc. This document talks about creating images, presenting them with PiSCSI on the SCSI Bus, and how to use them on your target computer.
== Initial setup ==
@@ -61,37 +61,37 @@ The image size is specified in bytes.
== Check existing SCSI IDs ==
-Once you have the image created, we need to find an unused SCSI ID to attach the image to. Use rasctl -l to list the current SCSI IDs being used by RaSCSI.
+Once you have the image created, we need to find an unused SCSI ID to attach the image to. Use scsictl -l to list the current SCSI IDs being used by PiSCSI.
```
-rasctl -l
+scsictl -l
```
For a new installation, you should see an output similar to the following.
```
-pi@raspberrypi:~ $ rasctl -l
+pi@raspberrypi:~ $ scsictl -l
No images currently attached.
```
-From the output above, we see RaSCSI is using no SCSI IDs. We will use ID 1 to attach our newly created 400MB image.
+From the output above, we see PiSCSI is using no SCSI IDs. We will use ID 1 to attach our newly created 400MB image.
-'''Note:''' rasctl -l only shows SCSI IDs presented via RaSCSI. It does not report other devices on the SCSI bus. You will want to use a utility or tool on your target computer to find what SCSI IDs are available to use. For example, Macintosh computers reserve SCSI ID 7 the onboard SCSI controller.
+'''Note:''' scsictl -l only shows SCSI IDs presented via PiSCSI. It does not report other devices on the SCSI bus. You will want to use a utility or tool on your target computer to find what SCSI IDs are available to use. For example, Macintosh computers reserve SCSI ID 7 the onboard SCSI controller.
== Attach new image to an unused SCSI ID ==
The next two commands will attach the new_drive.hda to SCSI ID 1, then show a list of the currently attached images.
```
-rasctl -i 1 -c attach -t hd -f /home/pi/images/new_drive.hda
-rasctl -l
+scsictl -i 1 -c attach -t hd -f /home/pi/images/new_drive.hda
+scsictl -l
```
And once done, you should see something similar to ...
```
-pi@raspberrypi:~ $ rasctl -i 1 -c attach -t hd -f /home/pi/images/new_drive.hda
-pi@raspberrypi:~ $ rasctl -l
+pi@raspberrypi:~ $ scsictl -i 1 -c attach -t hd -f /home/pi/images/new_drive.hda
+pi@raspberrypi:~ $ scsictl -l
+----+-----+------+-------------------------------------
| ID | LUN | TYPE | IMAGE FILE
@@ -100,9 +100,9 @@ pi@raspberrypi:~ $ rasctl -l
+----+-----+------+-------------------------------------
```
-From the rasctl output above, we see new_drive.hda image is now attached to SCSI ID 1.
+From the scsictl output above, we see new_drive.hda image is now attached to SCSI ID 1.
-With that complete, you can boot up the target computer that has the RaSCSI attached, and initialize or format the new disk.
+With that complete, you can boot up the target computer that has the PiSCSI attached, and initialize or format the new disk.
== Initializing a new disk on Classic Mac OS ==
@@ -114,7 +114,7 @@ The following images show this process on a Macintosh running Mac OS 8 (I think)
* '''Note 1:''' Apple HD SC Setup and earlier versions of Drive Setup has fine grained whitelisting controlling what drives it will initialize, and how large partitions it will create on those drives. You can spoof the INQUIRY data to pretend to be a particular old drive, but that may give you a very small partition (e.g. 20MB).
* '''Note 2:''' If you have issues initializing the drive, you may try a [https://lowendmac.com/2007/format-any-hard-drive-for-older-macs-with-patched-apple-tools/ patched Apple Drive Setup] or [https://macintoshgarden.org/apps/apple-hd-sc-setup-753-patch HD SC Setup] to bypass hard coded limitations. Or, you may also consider trying a 3rd party tool such as [https://macintoshgarden.org/apps/lido-756 Lido], [https://macintoshgarden.org/apps/scsiprobe SCSI Probe] or [https://macintoshgarden.org/apps/lacie-silverlining-531-more Silverlining]. They can be more forgiving than Apple's Drive Setup.
-* '''Note 3:''' At the time of writing, only ''Silverlining'' drivers are confirmed working with the ''Macintosh Plus''. Lido drivers and Apple drivers are known to not be compatible with a RaSCSI emulated drive on the Plus. See [https://github.com/akuker/RASCSI/issues/656 issue#656] for more information.
+* '''Note 3:''' At the time of writing, only ''Silverlining'' drivers are confirmed working with the ''Macintosh Plus''. Lido drivers and Apple drivers are known to not be compatible with a PiSCSI emulated drive on the Plus. See [https://github.com/piscsi/PiSCSI/issues/656 issue#656] for more information.
|-
|[[images/initialize_drive2.png]]
@@ -127,19 +127,19 @@ The following images show this process on a Macintosh running Mac OS 8 (I think)
'''Note:''' This area is for Mac OS disk setup application notes.
-= Understanding and doing more things with RaSCSI =
+= Understanding and doing more things with PiSCSI =
-The instructions up to this point are great for new users of the RaSCSI software. The following sections dig deeper into things you can do with RaSCSI.
+The instructions up to this point are great for new users of the PiSCSI software. The following sections dig deeper into things you can do with PiSCSI.
== Mounting CD / DVD ISO or MO images ==
-RaSCSI can mount [https://en.wikipedia.org/wiki/ISO_image CD or DVD ISO] images and MO [https://en.wikipedia.org/wiki/Magneto-optical_drive (Magneto Optical)] images. In most cases, drivers work out of the box with RaSCSI. You may have to use INQUIRY masquerading to get certain drivers to recognize the emulated optical drive.
+PiSCSI can mount [https://en.wikipedia.org/wiki/ISO_image CD or DVD ISO] images and MO [https://en.wikipedia.org/wiki/Magneto-optical_drive (Magneto Optical)] images. In most cases, drivers work out of the box with PiSCSI. You may have to use INQUIRY masquerading to get certain drivers to recognize the emulated optical drive.
=== Mac OS Drivers ===
-'''Note:''' As of RaSCSI v22.10.01, any Apple CD-ROM and DVD driver for classic Mac OS should work as-is. In previous versions of RaSCSI, they did NOT work with RaSCSI out of the box, which is why patched versions of the Apple drivers are provided below.
+'''Note:''' As of PiSCSI v22.10.01, any Apple CD-ROM and DVD driver for classic Mac OS should work as-is. In previous versions of PiSCSI, they did NOT work with PiSCSI out of the box, which is why patched versions of the Apple drivers are provided below.
-Macintosh CD-ROM drivers that have been verified working with RaSCSI:
+Macintosh CD-ROM drivers that have been verified working with PiSCSI:
* [https://macintoshgarden.org/apps/apple-cd-rom-extension-patched Apple CD/DVD Driver 1.2.2] patched (recommended for Mac OS 8.6)
* [https://macintoshgarden.org/apps/apple-cd-rom-extension-patched Apple CD-ROM 5.4.2] patched
@@ -148,17 +148,17 @@ Macintosh CD-ROM drivers that have been verified working with RaSCSI:
* [https://macintoshgarden.org/apps/cd-sunrise-v22b CD-Sunrise 2.2c]
* [https://macintoshgarden.org/apps/rapidcd RapidCD 1.0.4] (recommended for the highest CD-ROM image compatibility, but consumes a lot of memory)
-== What else can RaSCSI do? ==
+== What else can PiSCSI do? ==
Seriously, who named this section ? :)
-As the RaSCSI software was originally written for use with the Sharp X68000 computer, it supports a few image formats. The following shows the output from rascsi --help. The list of supported image types is at the bottom.
+As the PiSCSI software was originally written for use with the Sharp X68000 computer, it supports a few image formats. The following shows the output from rascsi --help. The list of supported image types is at the bottom.
```
$ rascsi --help
-SCSI Target Emulator RaSCSI Reloaded version 22.11 --DEVELOPMENT BUILD-- (Oct 23 2022 21:39:11)
+SCSI Target Emulator PiSCSI Reloaded version 22.11 --DEVELOPMENT BUILD-- (Oct 23 2022 21:39:11)
Powered by XM6 TypeG Technology / Copyright (C) 2016-2020 GIMONS
-Copyright (C) 2020-2022 Contributors to the RaSCSI Reloaded project
+Copyright (C) 2020-2022 Contributors to the PiSCSI Reloaded project
Connect type: FULLSPEC
Usage: rascsi [-idn[:m] FILE] ...
@@ -179,14 +179,14 @@ Usage: rascsi [-idn[:m] FILE] ...
iso : SCSI CD image (ISO 9660 image)
```
-== How to detach an image with rasctl ==
+== How to detach an image with scsictl ==
-In this section we will review the images currently attached to RaSCSI, and detach one or two.
+In this section we will review the images currently attached to PiSCSI, and detach one or two.
-'''1.''' use rasctl -l to get a listing of currently attached images.
+'''1.''' use scsictl -l to get a listing of currently attached images.
```
-pi@raspberrypi:~ $ rasctl -l
+pi@raspberrypi:~ $ scsictl -l
+----+-----+------+-------------------------------------
| ID | LUN | TYPE | DEVICE STATUS
@@ -200,18 +200,18 @@ pi@raspberrypi:~ $ rasctl -l
+----+-----+------+-------------------------------------
```
-'''2.''' We want to detach /home/pi/images/small_drive.hda , which is on SCSI ID6. Use the following commands will detach new_drive.hda, then run rasctl -l again to show the still mounted images.
+'''2.''' We want to detach /home/pi/images/small_drive.hda , which is on SCSI ID6. Use the following commands will detach new_drive.hda, then run scsictl -l again to show the still mounted images.
```
-rasctl -i 6 -c detach
-rasctl -l
+scsictl -i 6 -c detach
+scsictl -l
```
And the output should look like this..
```
-pi@raspberrypi:~ $ rasctl -i 6 -c detach
-pi@raspberrypi:~ $ rasctl -l
+pi@raspberrypi:~ $ scsictl -i 6 -c detach
+pi@raspberrypi:~ $ scsictl -l
+----+----+------+-------------------------------------
| ID | UN | TYPE | DEVICE STATUS
@@ -224,15 +224,15 @@ pi@raspberrypi:~ $ rasctl -l
+----+----+------+-------------------------------------
```
-== Presenting SCSI disks when the RaSCSI service starts ==
+== Presenting SCSI disks when the PiSCSI service starts ==
-At this point we can start the RaSCSI service and attach images to it. There are two methods to have RaSCSI automatically present disks on the SCSI bus when the service starts up.
+At this point we can start the PiSCSI service and attach images to it. There are two methods to have PiSCSI automatically present disks on the SCSI bus when the service starts up.
=== Web Interface method ===
-The first approach requires the RaSCSI [[Web Interface]] to be installed. Launch the Web Interface and attach the devices that you want as your default configuration. Then click the 'Save' button under the ''Current RaSCSI Configuration'' heading. This will save a configuration file called '''default.json''' into the RaSCSI config directory (~/.config/rascsi). The next time the Web Interface starts up, it will read this configuration file and attach the devices.
+The first approach requires the PiSCSI [[Web Interface]] to be installed. Launch the Web Interface and attach the devices that you want as your default configuration. Then click the 'Save' button under the ''Current PiSCSI Configuration'' heading. This will save a configuration file called '''default.json''' into the PiSCSI config directory (~/.config/rascsi). The next time the Web Interface starts up, it will read this configuration file and attach the devices.
-=== RaSCSI Service method ===
-The second approach involves modifying the RaSCSI service configuration, and is recommended only for advanced users, or those who prefer to not run the Web Interface.
+=== PiSCSI Service method ===
+The second approach involves modifying the PiSCSI service configuration, and is recommended only for advanced users, or those who prefer to not run the Web Interface.
The configuration for the rascsi service lives in /etc/systemd/system/rascsi.service . We will edit this file and update ExecStart.
@@ -272,7 +272,7 @@ sudo vi /etc/systemd/system/rascsi.service
ExecStart=/usr/local/bin/rascsi -ID1 /home/pi/images/400MB-system-disk.hda -ID2 /home/pi/images/this-house-is-a-prison.hda -ID5 /home/pi/images/simcity.iso
```
-'''Note:''' There is a current bug when providing multiple IDs - see this issue for more info https://github.com/akuker/RASCSI/issues/101
+'''Note:''' There is a current bug when providing multiple IDs - see this issue for more info https://github.com/piscsi/PiSCSI/issues/101
'''5.''' Save the file and exit the editor.
@@ -285,7 +285,7 @@ ExecStart=/usr/local/bin/rascsi -ID1 /home/pi/images/400MB-system-disk.hda -ID2
```
sudo systemctl daemon-reload
sudo systemctl restart rascsi.service
-rasctl -l
+scsictl -l
```
If everything worked, you should see the following
@@ -293,7 +293,7 @@ If everything worked, you should see the following
```
pi@raspberrypi:~ $ sudo systemctl daemon-reload
pi@raspberrypi:~ $ sudo systemctl restart rascsi.service
-pi@raspberrypi:~ $ rasctl -l
+pi@raspberrypi:~ $ scsictl -l
+----+----+------+-------------------------------------
| ID | UN | TYPE | DEVICE STATUS
@@ -306,13 +306,13 @@ pi@raspberrypi:~ $ rasctl -l
= I have the hardware and software, what next? =
-If you've made it this far, you're awesome!! The next part is how to make mounting/unmounting images easier. A web interface for RaSCSI has been developed to help in this area. Proceed to the [[Web Interface]] page. There we will learn about setting up the RaSCSI management web page, and how to use it.
+If you've made it this far, you're awesome!! The next part is how to make mounting/unmounting images easier. A web interface for PiSCSI has been developed to help in this area. Proceed to the [[Web Interface]] page. There we will learn about setting up the PiSCSI management web page, and how to use it.
= Mounting images on your Raspberry Pi locally (advanced) =
In the following steps, we will take a hard drive image that has already been formatted by a Macintosh computer, and mount it on your Raspberry Pi. The example assumes the disk was formatted with the HFS file system on Mac OS 7 or similar.
-'''Note!''' Make sure the image you're about to mount is NOT attached with RaSCSI. You may be able to mount a currently attached disk image, but chances are high the file system will be damaged, leading to data loss. Use the rasctl commands covered earlier to confirm the image is not attached.
+'''Note!''' Make sure the image you're about to mount is NOT attached with PiSCSI. You may be able to mount a currently attached disk image, but chances are high the file system will be damaged, leading to data loss. Use the scsictl commands covered earlier to confirm the image is not attached.
'''1.''' Install the hfsprogs package on your Raspberry Pi. This package contains the modules required to mount HFS formatted disks (and images). Run the following command to install the hfsprogs package.
@@ -367,10 +367,10 @@ pi@raspberrypi:~ $ lsmod | grep hfs
hfs 65536 0
```
-'''3.''' Create a directory to mount the hard disk image to. This can be any directory. We are using /mnt/RaSCSI in this example.
+'''3.''' Create a directory to mount the hard disk image to. This can be any directory. We are using /mnt/PiSCSI in this example.
```
-sudo mkdir /mnt/RaSCSI
+sudo mkdir /mnt/PiSCSI
```
'''Note:''' sudo is being used with the above command as /mnt is not writeable by the pi user. You are welcome to create a target directory somewhere the Pi user already has permissions, and would not need to prepend sudo to mkdir
@@ -396,18 +396,18 @@ drwxr-xr-x 7 pi pi 4096 Sep 11 00:45 ..
'''5.''' Mount the image. The following command will use a loop device to mount the image. Using a loop device allows the kernel to treat the image like a typical block device (hard drive, usb storage, optical drive, etc). You can find more information on loop devices at [https://en.wikipedia.org/wiki/Loop_device this Wikipedia article].
```
-sudo mount -o loop /home/pi/images/small_drive.hda /mnt/RaSCSI
-mount | grep RaSCSI
-ls -la /mnt/RaSCSI
+sudo mount -o loop /home/pi/images/small_drive.hda /mnt/PiSCSI
+mount | grep PiSCSI
+ls -la /mnt/PiSCSI
```
If the mount was successful, you will see the mount information, and get a directory listing of the contents from your hard disk image.
```
-pi@raspberrypi:~ $ sudo mount -o loop /home/pi/images/small_drive.hda /mnt/RaSCSI
-pi@raspberrypi:~ $ mount | grep RaSCSI
-/home/pi/images/small_drive.hda on /mnt/RaSCSI type hfs (rw,relatime,uid=0,gid=0)
-pi@raspberrypi:~ $ ls -la /mnt/RaSCSI
+pi@raspberrypi:~ $ sudo mount -o loop /home/pi/images/small_drive.hda /mnt/PiSCSI
+pi@raspberrypi:~ $ mount | grep PiSCSI
+/home/pi/images/small_drive.hda on /mnt/PiSCSI type hfs (rw,relatime,uid=0,gid=0)
+pi@raspberrypi:~ $ ls -la /mnt/PiSCSI
total 130
drwxr-xr-x 1 root root 10 Sep 10 23:43 .
drwxr-xr-x 3 root root 4096 Sep 11 01:00 ..
@@ -426,15 +426,15 @@ drwxr-xr-x 1 root root 5 Jul 18 2010 'StuffIt Expander'$'\252'' 4.0.2'
'''7.''' Once you are done working on the mounted image, use the following command to unmount the hard disk image.
```
-sudo umount /mnt/RaSCSI
-mount | grep RaSCSI
+sudo umount /mnt/PiSCSI
+mount | grep PiSCSI
```
The above will umount the HFS disk image, and show the output from mount , confirming the image is no longer mounted.
```
-pi@raspberrypi:~ $ sudo umount /mnt/RaSCSI
-pi@raspberrypi:~ $ mount | grep RaSCSI
+pi@raspberrypi:~ $ sudo umount /mnt/PiSCSI
+pi@raspberrypi:~ $ mount | grep PiSCSI
```
-'''8.''' From here you could use rasctl to re-attach the image and present it on the SCSI bus.
\ No newline at end of file
+'''8.''' From here you could use scsictl to re-attach the image and present it on the SCSI bus.
\ No newline at end of file
diff --git a/FAQ.mediawiki b/FAQ.mediawiki
index 9dc7633..f4f572b 100644
--- a/FAQ.mediawiki
+++ b/FAQ.mediawiki
@@ -1,9 +1,9 @@
-Frequently Asked Questions about RaSCSI.
+Frequently Asked Questions about PiSCSI.
-= My RaSCSI is running very hot – is this normal? =
+= My PiSCSI is running very hot – is this normal? =
-The four SN74LS641-1 transceiver ICs that drive the SCSI bus on the RaSCSI are known to run hot. These chips are [rated for 70°C](https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/page-25#post-426873) so as long as they are kept below this temperature they should be fine. Some users have [attached heatsinks](https://github.com/akuker/RASCSI/issues/484#issuecomment-980522338) to their RaSCSIs as a precaution, but this is not mandatory.
+The four SN74LS641-1 transceiver ICs that drive the SCSI bus on the PiSCSI are known to run hot. These chips are [rated for 70°C](https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/page-25#post-426873) so as long as they are kept below this temperature they should be fine. Some users have [attached heatsinks](https://github.com/piscsi/PiSCSI/issues/484#issuecomment-980522338) to their PiSCSIs as a precaution, but this is not mandatory.
= What is 68kmla? =
-[https://68kmla.org/forums/ 68kmla] is the “68k Mac Liberation Army”. Its a group of vintage Mac (and Apple) enthusiasts who talk about nerdy stuff on the forum. This development started as [https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/ part of a forum thread]. This RaSCSI project has grown far beyond the original 68k MLA community though.
\ No newline at end of file
+[https://68kmla.org/forums/ 68kmla] is the “68k Mac Liberation Army”. Its a group of vintage Mac (and Apple) enthusiasts who talk about nerdy stuff on the forum. This development started as [https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/ part of a forum thread]. This PiSCSI project has grown far beyond the original 68k MLA community though.
\ No newline at end of file
diff --git a/Full-Size-RaSCSI-Assembly.mediawiki b/Full-Size-RaSCSI-Assembly.mediawiki
index 89d692b..545ec21 100644
--- a/Full-Size-RaSCSI-Assembly.mediawiki
+++ b/Full-Size-RaSCSI-Assembly.mediawiki
@@ -1,12 +1,12 @@
= Congratulations on your purchase! =
-If you are reading this page, it is most likely because you have purchased the PiSCSI kit (full sized version). Alternatively, you've ordered the PCBs and procured the parts to build the RaSCSI pHAT for your Raspberry Pi. Either way, the following instructions are provided on how to assemble your new RaSCSI Reloaded board.
+If you are reading this page, it is most likely because you have purchased the PiSCSI kit (full sized version). Alternatively, you've ordered the PCBs and procured the parts to build the PiSCSI pHAT for your Raspberry Pi. Either way, the following instructions are provided on how to assemble your new PiSCSI Reloaded board.
-Note that PiSCSI was originally called "RaSCSI Reloaded". There are no differences in the hardware between "RaSCSI Reloaded" and PiSCSI!.
+Note that PiSCSI was originally called "RaSCSI Reloaded". There are no differences in the hardware between "PiSCSI Reloaded" and PiSCSI!.
-If you have the RaSCSI Zero version, see the assembly instructions [https://github.com/akuker/RASCSI/wiki/RaSCSI-Zero-Assembly here]
+If you have the PiSCSI Zero version, see the assembly instructions [https://github.com/piscsi/PiSCSI/wiki/PiSCSI-Zero-Assembly here]
-If you have not yet purchased one, you can pick up your very own RaSCSI Reloaded board on [https://www.tindie.com/products/landogriffin/rascsi-macintosh-version/ Tindie].
+If you have not yet purchased one, you can pick up your very own PiSCSI Reloaded board on [https://www.tindie.com/products/landogriffin/rascsi-macintosh-version/ Tindie].
__TOC__
@@ -98,7 +98,7 @@ extra long pins
Mounting holes have been placed in the PiSCSI board to attach it securely to any of the supported Raspberry Pi models. M2.5 standoffs can be purchased to affix your PiSCSI to the Raspberry Pi from [https://www.amazon.com/HVAZI-320pcs-Standoffs-assortment-Male-Female/dp/B06XKWDSPT/ Amazon]
=== OLED Screen ===
-A header is included for mounting an optional OLED screen to the PiSCSI board. The recommended OLED screen is [https://github.com/akuker/RASCSI/wiki/OLED-Status-Display-(Optional)#Overview MakerFocus SSD1306]. Other models may be compatible, but this version has been tested with the python script included in the [https://github.com/akuker/RASCSI/tree/master/src/oled_monitor RaSCSI github repo].
+A header is included for mounting an optional OLED screen to the PiSCSI board. The recommended OLED screen is [https://github.com/piscsi/piscsi/wiki/OLED-Status-Display-(Optional)#Overview MakerFocus SSD1306]. Other models may be compatible, but this version has been tested with the python script included in the [https://github.com/piscsi/piscsi/tree/master/src/oled_monitor PiSCSI github repo].
= Orientation options =
@@ -138,7 +138,7 @@ board. This image shows some important connection points
on the PiSCSI board.
-|[[images/assembly/RaSCSI_Options.png]]
+|[[images/assembly/PiSCSI_Options.png]]
|}
@@ -245,7 +245,7 @@ to remove the extra solder.
|-
|}
-With the first transceiver attached, do it three more times. But please ''please'' '''''please''''' heed the notice at the [https://github.com/akuker/RASCSI/wiki/Assembly#Install_Transceivers top of this section].
+With the first transceiver attached, do it three more times. But please ''please'' '''''please''''' heed the notice at the [https://github.com/piscsi/piscsi/wiki/Assembly#Install_Transceivers top of this section].
== Install Terminator Power Switch ==
@@ -275,9 +275,9 @@ The board should look similar to this.
== Correction for issue # 672 ==
-There is a potential issue with the PiSCSI (aka RaSCSI reloaded) board versions 2.4 and 2.5 when it is assembled with the DB-25 connector. If you are installing the DB-25 connector on your board, it is highly recommended that you make a small "cut" on your board. Over time, it appears that the DB-25 shield will wear through the solder mask and may come into contact with the 5v signal right below it. This essentially shorts 5v to Ground. Making this small cut will prevent this from happening.
+There is a potential issue with the PiSCSI (aka PiSCSI reloaded) board versions 2.4 and 2.5 when it is assembled with the DB-25 connector. If you are installing the DB-25 connector on your board, it is highly recommended that you make a small "cut" on your board. Over time, it appears that the DB-25 shield will wear through the solder mask and may come into contact with the 5v signal right below it. This essentially shorts 5v to Ground. Making this small cut will prevent this from happening.
-https://github.com/akuker/RASCSI/issues/672
+https://github.com/piscsi/piscsi/issues/672
{|
diff --git a/Hardware-Versions.mediawiki b/Hardware-Versions.mediawiki
index 56ecc5c..f2c23e3 100644
--- a/Hardware-Versions.mediawiki
+++ b/Hardware-Versions.mediawiki
@@ -1,53 +1,53 @@
= Full Sized Versions =
-The table below shows the known versions of the RaSCSI hardware, and whether it has been tested with the Reloaded version of the RaSCSI software.
+The table below shows the known versions of the PiSCSI hardware, and whether it has been tested with the Reloaded version of the PiSCSI software.
[[images/assembly/IMG_9516.jpg | width=200px]]
{| class="wikitable"
-! scope="col"| RaSCSI Hw Version
+! scope="col"| PiSCSI Hw Version
! scope="col"| Connection Type
! scope="col"| Tested and working?
! scope="col"| Schematic
! scope="col"| Gerbers
! scope="col"| Comments
|-
-|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_2p1 akuker 2.2]
+|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_2p1 akuker 2.2]
|FULLSPEC(Initiator or Target) |YES -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_2p2_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p2/rascsi_2p2.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p2/gerbers/rascsi_2p2.zip Gerbers] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_2p2_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p2/rascsi_2p2.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p2/gerbers/rascsi_2p2.zip Gerbers] |No major issues 5v/3v silkscreen captions swapped |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_2p3 akuker 2.3] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_2p3 akuker 2.3] |FULLSPEC (Initiator or Target) |Yes -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_2p3_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p3/rascsi_2p3.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p3/gerbers/gerbers.zip Gerbers] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_2p3_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p3/rascsi_2p3.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p3/gerbers/gerbers.zip Gerbers] |No known issues |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_2p4 akuker 2.4] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_2p4 akuker 2.4] |FULLSPEC (Initiator or Target) |Yes -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_2p4_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p4/rascsi_2p4.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p4/gerbers/gerbers.zip Gerbers] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_2p4_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p4/rascsi_2p4.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p4/gerbers/gerbers.zip Gerbers] |Added optional high-density connector for PowerBooks and [https://en.wikipedia.org/wiki/Berg_connector Berg] power connector. |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_2p5 akuker 2.5] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_2p5 akuker 2.5] |FULLSPEC (Initiator or Target) |Yes -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_2p5_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/develop/hw/rascsi_2p5/rascsi_2p5.kicad_sch KiCad] -|[https://github.com/akuker/RASCSI/blob/develop/hw/rascsi_2p5/gerbers/rascsi_2p5b_gerbers.zip Gerbers] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_2p5_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/develop/hw/rascsi_2p5/rascsi_2p5.kicad_sch KiCad] +|[https://github.com/piscsi/piscsi/blob/develop/hw/rascsi_2p5/gerbers/rascsi_2p5b_gerbers.zip Gerbers] |Updated to make external activity LED brighter (bypassed the extra 2k resistor) |} -= RaSCSI Target Board = -The RaSCSI Target Board is a minimal spec , low component count DIY version intended for enclosed applications ( external scsi housings etc. ) -[[https://levosretrocomputerprojects.co.uk/images/RaSCSI/20220219_144152.jpg | width=300px]] += PiSCSI Target Board = +The PiSCSI Target Board is a minimal spec , low component count DIY version intended for enclosed applications ( external scsi housings etc. ) +[[https://levosretrocomputerprojects.co.uk/images/PiSCSI/20220219_144152.jpg | width=300px]] * Low component count * 50 pin ribbon connector only * No Parity @@ -55,7 +55,7 @@ The RaSCSI Target Board is a minimal spec , low component count DIY version inte * Intended for DIY {| class="wikitable" -! scope="col"| RaSCSI Hw Version +! scope="col"| PiSCSI Hw Version ! scope="col"| Connection Type ! scope="col"| Tested and working? ! scope="col"| Schematic @@ -77,8 +77,8 @@ The RaSCSI Target Board is a minimal spec , low component count DIY version inte | |} -= RaSCSI Zero = -The RaSCSI Zero is a compact version of the RaSCSI board that is intended for use with the Raspberry Pi Zero family. Differences from the Full Sized RaSCSI include: += PiSCSI Zero = +The PiSCSI Zero is a compact version of the PiSCSI board that is intended for use with the Raspberry Pi Zero family. Differences from the Full Sized PiSCSI include: * Only has DB-25 connector. No ribbon cable connector. * Termination is always enabled. * Smaller board size (same size as Raspberry Pi Zero) @@ -86,19 +86,19 @@ The RaSCSI Zero is a compact version of the RaSCSI board that is intended for us [[images/assembly_zero/IMG_0771.png | width=200px]] {| class="wikitable" -! scope="col"| RaSCSI Hw Version +! scope="col"| PiSCSI Hw Version ! scope="col"| Connection Type ! scope="col"| Tested and working? ! scope="col"| Schematic ! scope="col"| Gerbers ! scope="col"| Comments |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_zero_1p0 akuker RaSCSI Zero 1.0] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_zero_1p0 akuker PiSCSI Zero 1.0] |FULLSPEC (Initiator or Target) |YES -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_zero_1p0_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_zero_1p0/rascsi_zero.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_zero_1p0/gerbers/gerbers_rascsi_zero_1p0.zip Gerbers] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_zero_1p0_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_zero_1p0/rascsi_zero.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_zero_1p0/gerbers/gerbers_rascsi_zero_1p0.zip Gerbers] |No major issues. |- | @@ -112,7 +112,7 @@ The RaSCSI Zero is a compact version of the RaSCSI board that is intended for us = Obsolete / Deprecated Versions = {| class="wikitable" -! scope="col"| RaSCSI Hw Version +! scope="col"| PiSCSI Hw Version ! scope="col"| Connection Type ! scope="col"| Tested and working? ! scope="col"| Schematic @@ -126,27 +126,27 @@ The RaSCSI Zero is a compact version of the RaSCSI board that is intended for us |N/A |Requires re-mapping of GPIO pins - doesn't match original GIMONS design |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_1p5 akuker 1.5] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_1p5 akuker 1.5] |STANDARD (Target Only) -|[https://github.com/akuker/RASCSI/issues/10 Yes - with Fix] -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_1p5_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_1p5/rascsi_din.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_1p5/gerber/gerber.zip Gerbers] +|[https://github.com/piscsi/piscsi/issues/10 Yes - with Fix] +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_1p5_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_1p5/rascsi_din.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_1p5/gerber/gerber.zip Gerbers] |Cut/Jump required to get this board to work |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_1p6 akuker 1.6] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_1p6 akuker 1.6] |STANDARD (Target Only) |Not Tested -|[https://github.com/akuker/RASCSI/wiki/sch/rascsi_1p6_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_1p6/rascsi_din.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_1p6/gerber/gerber.zip Gerbers] -|Same as 1.5, but with fix for [https://github.com/akuker/RASCSI/issues/10 Issue 10]. *Should* work, but is currently untested. +|[https://github.com/piscsi/piscsi/wiki/sch/rascsi_1p6_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_1p6/rascsi_din.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_1p6/gerber/gerber.zip Gerbers] +|Same as 1.5, but with fix for [https://github.com/piscsi/piscsi/issues/10 Issue 10]. *Should* work, but is currently untested. |- -|[https://github.com/akuker/RASCSI/tree/master/hw/rascsi_2p1 akuker 2.1] +|[https://github.com/piscsi/piscsi/tree/master/hw/rascsi_2p1 akuker 2.1] |FULLSPEC (Initiator or Target) |NO -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p1/rascsi_2p1_sch.pdf PDF] -[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p1/rascsi_2p1.sch KiCad] -|[https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p1/gerber/gerber.zip Gerbers] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p1/rascsi_2p1_sch.pdf PDF] +[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p1/rascsi_2p1.sch KiCad] +|[https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p1/gerber/gerber.zip Gerbers] |Several issues, including the connector being flipped. Not recommended for ANYONE to use |} \ No newline at end of file diff --git a/Home.mediawiki b/Home.mediawiki index e73e131..05e955e 100644 --- a/Home.mediawiki +++ b/Home.mediawiki @@ -38,7 +38,7 @@ |- |
+|PiSCSI Zero Main Board with Resistors & LEDs pre-installed |[https://www.tindie.com/products/landogriffin/ Tindie] |- @@ -58,7 +58,7 @@ pre-installed |} = Orientation options = -Please take careful note of the orientation of the RaSCSI Zero board, as well as the orientation of the Raspberry Pi Zero. If you assemble these incorrectly, DAMAGE MAY OCCUR! +Please take careful note of the orientation of the PiSCSI Zero board, as well as the orientation of the Raspberry Pi Zero. If you assemble these incorrectly, DAMAGE MAY OCCUR! = Assembly Instructions = @@ -68,7 +68,7 @@ The following section covers installing the transceivers. {| |'''Note:''' Several people have had a common mistake while -assembling their RaSCSI the first time. Please make a special +assembling their PiSCSI the first time. Please make a special note of the orientation of IC1 and IC2 vs IC3 and IC4 (the transceivers). Don't assume that they are all oriented the same way. Check that the dot on the chip (indicating pin 1) @@ -110,10 +110,10 @@ Solder the top pins in place. == Alternate Assembly for Raspberry Pi WH == {| -|If you have a Raspberry Pi Zero WH (with headers), you will need to assemble your RaSCSI Zero differently. +|If you have a Raspberry Pi Zero WH (with headers), you will need to assemble your PiSCSI Zero differently. | [[https://user-images.githubusercontent.com/34318535/198755035-e2940ef7-5c74-4257-a4cb-d48987599139.png | width = 400px]] |- -|The most critical thing to check during assembly is that the pins are not reversed. A good way to check this is to verify Pin 1 on the RaSCSI connects to Pin 1 on the Raspberry Pi. Pin 1 has a square pad instead of circular. +|The most critical thing to check during assembly is that the pins are not reversed. A good way to check this is to verify Pin 1 on the PiSCSI connects to Pin 1 on the Raspberry Pi. Pin 1 has a square pad instead of circular. ||[[https://user-images.githubusercontent.com/34318535/198754056-da6af5d0-5a57-439b-9411-59511e5ee6c3.png | width = 400px]] [[https://user-images.githubusercontent.com/34318535/198754380-38f48c17-8770-498a-aba5-ee7c89d1ed97.png | width = 400px]] |} @@ -123,18 +123,18 @@ Solder the top pins in place. |Take the straight 40-pin breakaway header and cut it EXACTLY in half. You should end up with two headers that are 20 pins long. |[[images/assembly_zero/IMG_0753.png | width=500px]] |- -| Insert the breakaway headers into the RaSCSI Zero board as shown here. Make sure you match the orientation of the board. The pins should point AWAY from the transceivers. +| Insert the breakaway headers into the PiSCSI Zero board as shown here. Make sure you match the orientation of the board. The pins should point AWAY from the transceivers. Use the 20 pin female header as a guide to hold the male pins straight while you're soldering. | [[images/assembly_zero/IMG_0755.png | width=500px]] |- -| Flip the board and solder all of the male pins into the RaSCSI Zero board. You can remove the female header after a few pins are soldered in each row. +| Flip the board and solder all of the male pins into the PiSCSI Zero board. You can remove the female header after a few pins are soldered in each row. |[[images/assembly_zero/IMG_0757.png | width=500px]] |} == Install the DB 25 connector == {| -|Snap the DB-25 connector in the RaSCSI board. The mechanical clips should hold it in place. The DB-25 connector should be installed on the same side as the resistors. It should NOT be installed on the same side as the transceivers. +|Snap the DB-25 connector in the PiSCSI board. The mechanical clips should hold it in place. The DB-25 connector should be installed on the same side as the resistors. It should NOT be installed on the same side as the transceivers. |[[images/assembly_zero/IMG_0758.png | width=500px]] |- | Solder all of the pins of the DB-25 connector @@ -147,7 +147,7 @@ Use the 20 pin female header as a guide to hold the male pins straight while you == Install the Disk Activity LED Connector == {| -| This step is OPTIONAL. You only need to install the 2-pin LED connector if you're using the RaSCSI Zero with an external LED. +| This step is OPTIONAL. You only need to install the 2-pin LED connector if you're using the PiSCSI Zero with an external LED. Insert the 2-pin right angle header into the holes, as shown. Solder these two pins into place. Tip: you can use the table to hold the right angle header in place (as shown here). Be careful not to touch the pins while soldering. They'll get VERY hot. | [[images/assembly_zero/IMG_0763.png | width=500px]] @@ -169,18 +169,18 @@ Tip: you can use the table to hold the right angle header in place (as shown her = Final Assembly = {| -|You should now have a fully assembled RaSCSI Zero with the male pins on the same side as the resistors. Double check that your assembled pieces match this image. +|You should now have a fully assembled PiSCSI Zero with the male pins on the same side as the resistors. Double check that your assembled pieces match this image. |[[images/assembly_zero/IMG_0768.png | width=500px]] |- -|You can now install the Raspberry Pi Zero on top of the RaSCSI Zero as shown here. +|You can now install the Raspberry Pi Zero on top of the PiSCSI Zero as shown here. |[[images/assembly_zero/IMG_0773.png | width=500px]] |- -|You can now continue with setting up the SD card and configuring your RaSCSI Zero! +|You can now continue with setting up the SD card and configuring your PiSCSI Zero! |[[images/assembly_zero/IMG_0771.png | width=500px]] |} = You're done! = -If you've gotten to this point, your RaSCSI board and optional daughter board are ready to use. +If you've gotten to this point, your PiSCSI board and optional daughter board are ready to use. -Proceed to the [https://github.com/akuker/RASCSI/wiki/Setup-Instructions Setup Instructions] page. \ No newline at end of file +Proceed to the [https://github.com/piscsi/piscsi/wiki/Setup-Instructions Setup Instructions] page. \ No newline at end of file diff --git a/RaSCSI-for-Hardware-Samplers.md b/PiSCSI-for-Hardware-Samplers.md similarity index 87% rename from RaSCSI-for-Hardware-Samplers.md rename to PiSCSI-for-Hardware-Samplers.md index 661e486..c793009 100644 --- a/RaSCSI-for-Hardware-Samplers.md +++ b/PiSCSI-for-Hardware-Samplers.md @@ -1,14 +1,14 @@ -1. [FAQ](https://github.com/akuker/RaSCSI/wiki/RaSCSI-for-Hardware-Samplers#faq) -2. [Setup](https://github.com/akuker/RaSCSI/wiki/RaSCSI-for-Hardware-Samplers#setup) -3. [Troubleshooting](https://github.com/akuker/RaSCSI/wiki/RaSCSI-for-Hardware-Samplers#troubleshooting) -4. [Compatibility](https://github.com/akuker/RaSCSI/wiki/RaSCSI-for-Hardware-Samplers#compatibility) -5. [Performance Tests](https://github.com/akuker/RaSCSI/wiki/RaSCSI-for-Hardware-Samplers#performance-tests) +1. [FAQ](https://github.com/piscsi/piscsi/wiki/PiSCSI-for-Hardware-Samplers#faq) +2. [Setup](https://github.com/piscsi/piscsi/wiki/PiSCSI-for-Hardware-Samplers#setup) +3. [Troubleshooting](https://github.com/piscsi/piscsi/wiki/PiSCSI-for-Hardware-Samplers#troubleshooting) +4. [Compatibility](https://github.com/piscsi/piscsi/wiki/PiSCSI-for-Hardware-Samplers#compatibility) +5. [Performance Tests](https://github.com/piscsi/piscsi/wiki/PiSCSI-for-Hardware-Samplers#performance-tests) # Introduction -The RaSCSI is a SCSI emulator that is built on the Raspberry Pi Ultra Low Cost Computer platform. It will mount virtual CD-ROM's and Hard Drives directly into your sampler using the SCSI port on the back. +The PiSCSI is a SCSI emulator that is built on the Raspberry Pi Ultra Low Cost Computer platform. It will mount virtual CD-ROM's and Hard Drives directly into your sampler using the SCSI port on the back. -The benefits of using a RaSCSI are: +The benefits of using a PiSCSI are: * Easy to use with a web-based admin interface * Low cost ($60 for a basic setup, $150 for a high-end setup) @@ -16,7 +16,7 @@ The benefits of using a RaSCSI are: * Effectively a CD-ROM jukebox that can manage dozens of ISO images without SD card swapping * Create and mount hard drive images -If you get comfort from the clicking and clacking and whirring of old SCSI devices then the RaSCSI isn't for you. If you enjoy the thrill of wondering whether or not your Zip cartridge will save your sample editing session, we don't judge. +If you get comfort from the clicking and clacking and whirring of old SCSI devices then the PiSCSI isn't for you. If you enjoy the thrill of wondering whether or not your Zip cartridge will save your sample editing session, we don't judge. If you want to learn more about the best mass storage solution for vintage samplers then you should read on. @@ -29,7 +29,7 @@ If you want to learn more about the best mass storage solution for vintage sampl The project lead sells them on Tindie. Ignore the signs about it being a product for Macintosh, he was a little confused when he created that page and didn't realize how awesome this product would be for all of us sampler users. This is the version to get: -RaSCSI [Tindie Store](https://www.tindie.com/products/landogriffin/rascsi-english-version-assembled/) +PiSCSI [Tindie Store](https://www.tindie.com/products/landogriffin/rascsi-english-version-assembled/) |
-We are actively working to get a groovy 3d printed case designed. Sitting exposed on your desktop won't damage the RaSCSI, just don't lick it by mistake. +We are actively working to get a groovy 3d printed case designed. Sitting exposed on your desktop won't damage the PiSCSI, just don't lick it by mistake. |
-Sure you could probably figure out how to do this and you'd need to either drill holes or create a custom mount for the floppy bay. Even after all that it is better to keep it outside where the RaSCSI can stay cooler - this is healthy for both the RaSCSI and your sampler. +Sure you could probably figure out how to do this and you'd need to either drill holes or create a custom mount for the floppy bay. Even after all that it is better to keep it outside where the PiSCSI can stay cooler - this is healthy for both the PiSCSI and your sampler. |
-At the time of writing this, amazon.com is selling a 64GB Sandisk Ultra microSD card for $12, 128GB for $20, and 256GB for $35. At those prices the 64GB is a no-brainer for a well-spec'ed RaSCSI setup. +At the time of writing this, amazon.com is selling a 64GB Sandisk Ultra microSD card for $12, 128GB for $20, and 256GB for $35. At those prices the 64GB is a no-brainer for a well-spec'ed PiSCSI setup. -The OS and RaSCSI software will take a little over 8GB, leaving you the balance of the card to store disk images. +The OS and PiSCSI software will take a little over 8GB, leaving you the balance of the card to store disk images. A CD-ROM image will have a maximum size of 650MB but most are in the 200-300MB range. Roland CD-ROM's are a little different as for some strange reason they specified that all discs must fill up the empty space with zeros, so they're all 650MB no matter what. Let's also assume that the average hard drive for sampler use is 500MB - you can definitely have larger drives but most older samplers don't have folder/subfolder implementations and it's a PITA to scroll through hundreds of banks/multis/programs to find what you're looking for. @@ -106,7 +106,7 @@ Using that logic, a 64GB SD card will give you roughly 56GB of storage. Let's b If that's not enough for you, spend the extra $8 on the 128GB card and you'll have enough capacity for 20 virtual hard drives and over 400 CD-ROM images. -Also remember that RaSCSI has an awesome web admin interface that lets you transfer files directly onto the Raspberry Pi, so it's very easy to swap out CD-ROM images if you have a very large library stored on another computer somewhere. You could also hook up an external USB 3.0 hard drive if you bought the Raspberry Pi 4B and use that as your local high-speed RaSCSI image library location. +Also remember that PiSCSI has an awesome web admin interface that lets you transfer files directly onto the Raspberry Pi, so it's very easy to swap out CD-ROM images if you have a very large library stored on another computer somewhere. You could also hook up an external USB 3.0 hard drive if you bought the Raspberry Pi 4B and use that as your local high-speed PiSCSI image library location. It should also be noted that over the years of using SD cards in samplers that generic cards seem to have higher failure rates than name-brand cards, and counterfeit name-brand SD cards are more common than you might think on auction sites. Generally speaking, you get what you pay for. |
Completely 100% totally A-OK.
-If you have content from an old 1GB external hard drive that you'd like to back up, just create a virtual 1GB hard drive in the RaSCSI and mount it to a free SCSI ID. Then use your sampler to copy all of the files from the physical drive to the virtual drive. +If you have content from an old 1GB external hard drive that you'd like to back up, just create a virtual 1GB hard drive in the PiSCSI and mount it to a free SCSI ID. Then use your sampler to copy all of the files from the physical drive to the virtual drive. -You could use the same method to copy content from your favorite physical CD-ROM's or Zip Disks and consolidate them on a virtual hard drive. Then put them in a box in that dark corner of the garage no one ever looks at, give them to the local tech-friendly recycle depot, or sell them on ebay to people who have never heard of RaSCSI. +You could use the same method to copy content from your favorite physical CD-ROM's or Zip Disks and consolidate them on a virtual hard drive. Then put them in a box in that dark corner of the garage no one ever looks at, give them to the local tech-friendly recycle depot, or sell them on ebay to people who have never heard of PiSCSI. |
-These devices are directly comparable to the RaSCSI, but in the opinion of the unofficial RaSCSI Sampler Team it's the clearly superior solution and can be recommended to all sampler users who use SCSI-equipped electronic musical instruments.
+These devices are directly comparable to the PiSCSI, but in the opinion of the unofficial PiSCSI Sampler Team it's the clearly superior solution and can be recommended to all sampler users who use SCSI-equipped electronic musical instruments.
-SCSI2SD has been the leading modern mass storage solution since soon after its introduction in 2013. Relative to the more expensive SCSI2SD V6 the RaSCSI offers:
+SCSI2SD has been the leading modern mass storage solution since soon after its introduction in 2013. Relative to the more expensive SCSI2SD V6 the PiSCSI offers:
- (+) Vastly more intuitive administration/management
- (+) Wi-Fi/network connectivity
- (~) Similar performance
- (-) Can't easily be mounted internally
-Relative to the SCSI2SD V5.5 the RaSCSI scores:
+Relative to the SCSI2SD V5.5 the PiSCSI scores:
- (+) Vastly more intuitive administration/management
- (+) Wi-Fi/network connectivity
@@ -168,7 +168,7 @@ Relative to the SCSI2SD V5.5 the RaSCSI scores:
- (-) Larger physical footprint
-Blue SCSI is another new SCSI emulation device which shows a lot of promise as an inexpensive drive emulator, however the RaSCSI is a far more powerful solution for sampler users:
+Blue SCSI is another new SCSI emulation device which shows a lot of promise as an inexpensive drive emulator, however the PiSCSI is a far more powerful solution for sampler users:
- (+) Much faster performance
- (+) Mounts ISO images as virtual CD-ROM's
@@ -192,7 +192,7 @@ The vendors of these floppy drive emulators can be really deceptive with their d
A lot of people see "USB Storage" and think "Oh this is awesome because transferring files to my computer using that USB stick is so fast!" so you'd definitely not be the first person to get excited then experience the letdown of the cold, hard truth of the floppy ribbon cable of life.
-A USB floppy emulator is perfect for older samplers without SCSI, and their on-board memory capacity is usually less than the 720KB or 1.44MB floppies that they use. However, if your sampler has SCSI, you should be using a RaSCSI.
+A USB floppy emulator is perfect for older samplers without SCSI, and their on-board memory capacity is usually less than the 720KB or 1.44MB floppies that they use. However, if your sampler has SCSI, you should be using a PiSCSI.
If you are interested in a floppy emulator for an older sampler then check out [HxC](http://hxc2001.free.fr/floppy_drive_emulator/index.html#Download_HxCFirmwareForGotek) or [FlashFloppy](https://github.com/keirf/FlashFloppy/wiki) and don't pay a crazy price for an underpowered and oversold floppy emulator. $30-$60 is a fair price for a USB emulator, and in our opinion you should avoid anyone selling them for over $100.
@@ -221,7 +221,7 @@ If you are just learning how to solder, don't have quality soldering/desoldering
### Step 1 - Set up Raspberry Pi
-Connect the RaSCSI to the Raspberry Pi using the header pins (there's only one way it will fit). Connect a monitor to the HDMI port and a keyboard and mouse to the USB ports.
+Connect the PiSCSI to the Raspberry Pi using the header pins (there's only one way it will fit). Connect a monitor to the HDMI port and a keyboard and mouse to the USB ports.
### Step 2 - Install the Raspberry Pi software onto the SD card
@@ -231,7 +231,7 @@ Follow the [standard instructions](https://www.raspberrypi.org/documentation/ins
Insert the SD card into the Raspberry Pi and power it up. Follow the on-screen instructions to configure it, and connect it to your Wi-Fi network at this time if you like.
-Then follow the [RaSCSI setup procedure](https://github.com/akuker/RaSCSI/wiki/Setup-Instructions) to install that software.
+Then follow the [PiSCSI setup procedure](https://github.com/piscsi/piscsi/wiki/Setup-Instructions) to install that software.
### Step 4 - Connect to the admin web page
@@ -257,7 +257,7 @@ You will then be able to log in using the user "pi" and the password you provide
(NOTE: this section is a work in progress)
-Although you can use the web interface to manage files on the RaSCSI, it's often easier just to mount the images folder to a Windows share then you can cut/copy/paste files from your main computer.
+Although you can use the web interface to manage files on the PiSCSI, it's often easier just to mount the images folder to a Windows share then you can cut/copy/paste files from your main computer.
`sudo apt install samba -y`
@@ -269,8 +269,8 @@ Although you can use the web interface to manage files on the RaSCSI, it's often
Add this to the bottom of the file:
-> [RaSCSI Images]
-> comment = RaSCSI Images
+> [PiSCSI Images]
+> comment = PiSCSI Images
> path = /home/pi/images/
> directory mask = 0777
> create mask = 0777
@@ -294,7 +294,7 @@ Add this to the bottom of the file:
We're still in the early stages of developing this knowledge base and are only starting to collect troubleshooting information. However, the vast majority of SCSI problems that sampler users have encountered over the past 30 years come down to two things: 1) Improper SCSI termination or 2) Duplicate SCSI ID's on the same chain.
-If you've checked those things, please join us on the [RaSCSI-Samplers Discord Channel](https://discord.com/channels/749261651978748014/839337309752262696) or the [RaSCSI for Samplers Facebook Group](www.facebook.com/groups/RaSCSIforsamplers/) for more support.
+If you've checked those things, please join us on the [PiSCSI-Samplers Discord Channel](https://discord.com/channels/749261651978748014/839337309752262696) or the [PiSCSI for Samplers Facebook Group](www.facebook.com/groups/RaSCSIforsamplers/) for more support.
There are also several hardware sampler groups on Facebook providing peer support for the samplers themselves:
@@ -313,7 +313,7 @@ The tables below show the testing status for all known samplers with SCSI. It i
|