• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Announcing scsi2sd_to_hda, a quick and dirty script I wrote to convert SCSI2SD images to .hda files compatible with RASCSI/BlueSCSI

dburr

Member
Recently I finally finished restoring my beloved SE/30. I'm a major Unix geek, and I have dreamed of being able to run A/UX on one of my machines. Unfortunately, during its heyday, it was way beyond my starving-student budget. Recently I found the A/UX SCSI2SD easy install and wanted to give it a try... but I didn't have a SCSI2SD. So I dug into it and figured out that the XML file contains offsets to the various SCSI "devices" in the SD card image file. And I hacked together a script that parses the XML and splits out the various SCSI devices into their own .hda files that I could use with my RASCSI and/or BlueSCSI. ;-)

Get it here!
 

chillin

Well-known member
If that's what you call "quick and dirty," I'd like to see your idea of leisurely and clean. It's a neat script. Unless I missed something, it's coded entirely with bash builtins. Though I don't think echo is builtin to Bourne, I bet it'd even work on A/UX sh without modification, though the conversion would be very slow across the SE/30 SCSI bus.

bah, I missed cut and dd. And I was looking for dd. Still neat, and I still think it'll run on A/UX, not that anyone would want to
 
Last edited:

dburr

Member
If that's what you call "quick and dirty," I'd like to see your idea of leisurely and clean. It's a neat script. Unless I missed something, it's coded entirely with bash builtins. Though I don't think echo is builtin to Bourne, I bet it'd even work on A/UX sh without modification, though the conversion would be very slow across the SE/30 SCSI bus.

bah, I missed cut and dd. And I was looking for dd. Still neat, and I still think it'll run on A/UX, not that anyone would want to
Thanks :) I was trying to find a way of doing this with the minimal amount of external tools (there are a few xml parsers I could have used) and I was able to come up with a kinda hacky (but it works ;-) ) way of doing it completely within bash.
 

shirsch

Member
I'm able to mount the larger extracted image (HD1..) from my A/UX boot drive but fsck reports it as badly damaged. Anyone else see this issue? It does mount without complaint and I'm able to see the contents. Is it possibly too large for the OEM fsck tool to handle properly?
 
Top