Search results

Not hard, impossible. Building SCSI2SD V3/4/5 is impossible. CY8C5267's and ALL other parts in the family are unobtanium, thanks to the global component shortages.

Yes, you can do this via Basilisk on Windows as well. There are plenty of videos and tutorials online, if you Google it, but someone here may be able to provide a recommended link/guide.

It doesn't, it can't tell the difference. That's the whole point/goal. There won't be a "SCSI 1 icon" per se, the Macintosh will simply see a volume, and, assuming it's formatted and partitioned correctly, Finder will show the name of the volume on the desktop. Yes, but you have to know what...

It's not that it doesn't provide "enough" power. This is not an accurate representation of the situation. The Mac Plus simply does not provide any SCSI termination power, unless you add a diode to the location on the Mac Plus logic board where Apple chose to omit it, presumably out of an...

Ah ok, understood. Yep, that's the whole point of this endeavour....connectivity to the outside world without the need for external bridges.

The RP2040-based Pi Picos are not "Raspberry Pi" SBCs; They're $4 Cortex M0+ based microcontrollers. It's the Raspberry Pi's first microcontroller design. Pico = RP2040, which is a ~$1 microcontroller.

Ten megabits of through is likely not achievable, given the limitations of the serial hardware on the Mac side. I believe the faster serial is good for TWO megabits per second, if externally clocked. This was a "geoport" feature, so these speeds would likely be limited to Macs that shipped with...

These "universal" serial-only CommSlot PCBs just showed up today, and so far, we've only confirmed that they physically fit in both CommSlot I and CommSlot II sockets, which is a relief. It has footprints for an ESP8266-based Adafruit ESP-12F ($6.95), Raspberry Pi Pico or Pico W stamp...

Thanks, that's the assumption I was operating under, but it's nice to have it confirmed.

Good to know, thanks, @David Cook . Can you share any information on voltage levels/logic types for the serial pins? TTL? CMOS?

Thanks. Since this is the first report we've had of any firmware issues with 1.0.7, unless we can get a debug log from you, it's going to be exceedingly difficult to understand the root cause of this problem. We don't have a IIci to test with.

Thank you for the feedback. We appreciate it. I wish it hadn't taken as long as it did to resolve, but we found a few other small issues along the way, and ended up with better debug output as a result, so it wasn't all bad in the end. Thanks again!

Yes, on the Mac Plus, you must have the following two settings present in a zuluscsi.ini file: To quote Michael McMaster (Creator of SCSI2SD), "The Mac Plus is troublesome as it's bootrom code doesn't follow the SCSI standards. The SCSI standards recommend a SCSI selection abort timeout of...

@macuserman, We've just released firmware version 1.0.6 on GitHub, which should fully resolve the stability issues you've been seeing with your Quadra 700. Please upgrade at your convenience, and let us know here, if you continue to have any problems.

@Jockelill Please try the attached development firmware, and let us know if it results in any change of behavior for you with your Mac Plus. The diode mod won't fix your issue, but it's always preferable, for the sake of convenience, if nothing else, to be able to power it from termination power.

What's the size of the SD card you're using? Can you send me a photo of the front and back of the card?

Not sure where you got that (incorrect) memory address from.. The correct syntax/address is: dfu-util -a 0 --dfuse-address 0x08000000 -D firmware.bin

Today, we released ZuluSCSI firmware version 1.0.4, which adds the ability to disable the prefetch buffer at runtime, by setting PrefetchBytes=0 in the [SCSI] section of the zuluscsi.ini file. In our testing, we've found that disabling the prefetch buffer on Macs which support synchronous SCSI...

Please engage with us via e-mail, and _fully_ describe the problem, including which SD card you're using, etc. If you aren't seeing a log, it's because the ZuluSCSI isn't writing one, which almost certainly means it can't find an SD card. Please ensure you're using an SD card that's an...

It's one of the few viable options