Recent content by saybur

This is really cool work, thank you for taking the time to document this so well!

Short answer: no. You'd just be reinventing PiSCSI. The current crop of SD based devices are excellent, bus-saturating fast and full of bells and whistles.

Bluetooth support should now be (somewhat) ready for general use. Still quite experimental so let me know if you try it out. Release is here: https://github.com/saybur/hootswitch/releases/tag/v20260417

Just stop it. I would like to chat about this unimportant little project in peace, not watch a pointless mud-slinging contest that saps the little patience I have with the (lack of) forum moderation. Let's stay on topic. Please.

Agree with the sentiment from @Fizzbinn. For clarity, I have no problem with WOOTswitch; as others mentioned I don't sell hardware myself and having an option for those not able to DIY their own boards is, IMHO, a good thing. In technical news, I'm slowly adding Bluetooth peripheral support...

If you would like a visual guide the 65scribe video about the IIsi includes him disassembling the system. Starts at 12:16. Good for a laugh too.

It's an impressive list of accomplishments, congrats to y'all for getting that much work done! I know I'm not speaking for just myself: your contributions are really appreciated. I was wondering if the SQLite backend was considered ready for general use? I'm still on Berkeley but was figuring...

The Debian script it looks like it merges all .isos into a single readable image, complete with combined package lists and the like.

Should run in 6.0.4(ish) and up but it's untested on anything other than 7.5.5 Well it shouldn't but this is hot code so I'm not comfortable saying it definitely will not. It seems unlikely unless the OS maps IDE devices onto SCSI IDs or something like that. Would be prudent to have anything...

Here's the prototype. This can either read SCSI devices into images (File:Read Disk) or write images to SCSI devices (File:Write Disk). Pick a SCSI ID and then a file to write/read. This is very much an alpha and it may eat all your data, please use with great caution. There are many, many...

Makes sense. I've been spoiled by modern Linux distros being able to `dd` an image and having it "just work" most of the time. What I've got so far is just a scuzEMU derivative. The low-level SCSI commands in/out of files was already halfway to what was needed. It's inheriting the THINK C...

I drafted a small demo program yesterday in response to your first post to do what you're describing: single function, just write a file as a disk image to an arbitrary SCSI ID. Based on testing disk images worked fine. However, the limited number of small CD images I tried did not work, but I'm...

Even the desktop systems require fussing to keep running: basically every system Apple made in the period being discussed will need capacitor work of some kind. The LC boxes in particular are notorious for issues with their power supplies and audio circuits. If you're not wanting to deal with...

Version 0.6 is available here. Main changes: Support for the new multi-block transfers introduced into the toolbox API starting with BlueSCSI v2026.02.08-RC1. .dsk release, to simplify loading into MAME. Bugfixes, mainly to file naming/path issues. The new transfers are much faster, assuming...

Yeah there isn't a way to update the INI from a utility. This would be a very nice feature, there are many systems beyond laptops that would benefit from better device control (he says, glaring at a Quadra 800) Edit: to add, this is not a ZuluSCSI specific thing: the API used doesn't support...