My Mac SE/30 Part IX: System 7.5 Boot Floppy

In Part VIII of this series, I finished prepping a 2 GB SD card for the SCSI2SD that will serve as the primary disk for my vintage Macintosh SE/30. Now it’s time to get that disk formatted and a working system installed, but to do so I’ll need to create a boot floppy first.

As a quick recap, at this point I have a Macintosh SE/30 with a working floppy drive. I’ve installed 64 MB of RAM along with a GGLABS MACSIMM ROM replacement. I’m using the aforementioned SCSI2SD to simulate a single 1.75 GB hard drive, on which I intend to install System 7.5.5.

Formatting plan

The first thing I want to do is format that 1.75 GB drive with an HFS filesystem. The usual process is to boot from a floppy and use either the Apple HD SC Setup (for System 6) or Drive Setup (for System 7) program to format the drive. However, I’ve found that those programs don’t work well with the SCSI2SD. They don’t recognize the non-Apple drive by default, and even if you get a “patched” version which does, the resulting disk will have data corruption problems.

The solution is to use the third-party disk formatter Lido 7.5.6. It works perfectly fine with the SCSI2SD, however it doesn’t come preinstalled on a bootable floppy. So the actual first thing I need to do is to make a bootable floppy.

Creating the boot floppy

While there are many methods for doing this, I decided that since I’m planning on installing 7.5.5, that I wanted a 7.5.5 boot floppy. However by this time system CDs were becoming the norm, so the closest I could find was Apple’s System 7.5 Network Access Disk.

It’s provided as a disk image stored in a MacBinary-encoded self-extracting archive, so the first step is to download it onto a working classic mac and extract the disk image with Stuffit Expander. Then you can use the Disk Copy program to write the extracted “Network Access.image” file to a real floppy.

This is where having a bridge machine, like the Power Macintosh 8600/200 I previously restored, comes in handy. I could have easily done the whole process, from download to physical floppy, right there. But let’s assume for a moment that you don’t have a bridge machine, is it still possible to create a vintage mac boot floppy? Yes!

Note: Okay, technically, if your vintage mac only accepts 400/800k disks, then the answer is no. You’ll need a real, already working vintage mac to write one of these older floppies.

What you’ll need to do is create a bridge machine in emulation, with something like Mini vMac. To be honest, I use Mini vMac as a bridge machine way more often than I use my PowerMac. Other than the lack of networking and CDs, it covers most of my needs quite well.

Now, I’m not going to detail how to get Mini vMac set up. There are already plenty of tutorials out there for that and it’s worthwhile to get comfortable with the program before continuing. What I’ve got set up is a Macintosh II running System 7.5.5 with Stuffit Expander and Disk Copy (as above), along with the apps ImportFI and ExportFI to get files into and out of the emulator.

Creating a raw DSK image file

Without access to a real mac floppy drive, what we want is a raw DSK image of the Network Access disk. That is, we want a file with a 1-to-1 copy of the bits of that bootable floppy, without any extraneous headers or metadata. To start, we’ll need to use Mini vMac to get the Disk Copy image out of the archive:

  1. Download the Network_Access_Disk_7.5.sea.bin archive to your PC.
  2. Use ImportFI to import the archive file into Mini vMac.
  3. Use Stuffit Expander within Mini vMac to extract the archive’s contents.
  4. Use ExportFI to export the “Network Access.image” file out of Mini vMac back to your PC.

Now, the file we’ve exported is almost what we need. It’s a Disk Copy 4.2 image with all of the data we want, but it’s still wrapped up in some metadata we don’t. To strip that metadata we’re going to use a tool called Convert2Dsk.

Convert2Dsk is a small command-line tool I wrote to convert Disk Copy 4.2 images into raw DSK images on modern PCs. It works on Windows, OSX, and Linux, can even handle image files that are BinHex (.hqx) or MacBinary (.bin) encoded. Simply pass it an image file (or folder of image files) and it’ll convert them into DSK files.

On Windows, it’s as simple as dragging the “Network Access.image” file onto convert2dsk.exe, which will then create the “Network Access.image.dsk” file we want.

Writing the raw DSK image to a floppy

Now that we have a raw DSK image, it’s time to write that file to a floppy disk. Obviously that means you’ll need a floppy drive and at least one 1.4 MB floppy disk. You can get an external USB floppy drive on eBay, though a pro-tip is to avoid the new stuff from China, and instead pick up an older used drive made by one of the big PC manufacturers. They may cost a little more but they’re of higher quality and less likely to give you problems. I bought an old Dell floppy drive for $20 and it works perfectly.

Software-wise, you’re going to need a program to read and write the disk images, and I use dd (for Windows). It’s a powerful command-line utility for utility (also on OSX and Linux) for reading and writing directly to a drive by sectors. So from a command-prompt I’ll call dd.exe like so:

dd.exe if=<image file> od=<floppy drive letter> --progress

Which, with the file we created earlier, and my USB floppy registered as the A: drive, looks like:

dd.exe if="Network Access.image.dsk" od=a: --progress

Running with a floppy inserted will overwrite its entire contents with the contents of the DSK file. If you see “80+0 records in” and “80+0 records out”, then the write worked and the floppy is ready to use. Pop the disk into the SE/30, flip the switch, and… it doesn’t boot.

Fixing a 7.5 disk to boot a SE/30 with an upgraded ROM

It turns out that the combination of a SE/30 with the MACSIMM ROM replacement (which is based on the IIsi ROM) isn’t recognized by System 7.5 and above as a valid Macintosh computer. Thankfully this problem can be solved by making a minor patch to the system files, as detailed in this post: Mac SE/30 with Upgraded ROM.

However, I found that post to be a little overzealous in its instructions. Their goal is to setup a machine with each and every system version, using a tool called System Picker to let you switch between them. While it works, it’s a tedious process, and as I’ve stated, I only want System 7.5.5. So, simplifying their steps, here’s what I did in Mini vMac:

  1. Mount the raw DSK image as a floppy “Network Access.image.dsk” in Mini vMac.
  2. Use ResEdit to open the “System” file in the “System Folder” on the disk.
    1. Open the “gusd” resource.
    2. Open “ID 1”.
    3. Go to the 4th line (offset 000018) and change the end from 03 to 05. That is, the line should have changed from 0008 0003 0009 0003 to 0008 0003 0009 0005 as per below:
Modifying the System file in ResEdit
Modifying the System file in ResEdit
  1. Save and close the file.
  2. Eject the disk from Mini vMac.

Now if you write the modified disk image to a floppy using dd (as above), it should be bootable on the upgraded SE/30.

So that’s it, that’s how to create a System 7.5 boot floppy that will work on an SE/30 with an upgraded ROM. Stay tuned for Part X, where we’ll finally switch to the SE/30 and start setting up its disk drive.


Want to read from the beginning? Start at Part I.

Reviving a Sony WM-FX28 Walkman

I had been looking for a small restoration project, something with electronic and mechanical components that could be completed in less than a day, when I stumbled upon some YouTubers who still use audio cassettes.

It reminded me how much I obsessed over audio equipment as a child. Every time a family member upgraded their stereo systems I would beg for the old components, and by the time I was a teenager in the late 90’s I had built an absurdly mismatched setup in my media tower.

Part of that system included an old wood-panel tape deck complete with needle meters. I never had many commercially produced cassettes, but I had stacks I’d recorded myself. I loved recording video game music to listen to on my walkman, or dictating story ideas through the set of “professional” microphones I’d scrounged.

So, watching these YouTube videos, I started to get a better understanding how cassettes and cassette decks work. I enjoyed seeing that, if you knew what you were doing, you could actually make pretty high quality recordings on cassette.

Which, by the way, taught me that I was doing everything 100% wrong as a child. Oops.

Now, I don’t have any old cassettes to play, nor do I have a pressing need to set up a full deck for recording, but after some deliberation, I decided that I wanted to try my hand at fixing and restoring a walkman. Nothing fancy, not the golden-grail best player desired by current cassette collectors – just take a regular broken walkman and get it up and running again.

I searched eBay for options and finally settled on this Sony WM-FX28:

The listing said the radio worked but the tape didn’t, and it was only $10 before shipping. I looked around online and was able to find PDFs of both the Sony WM-FX28 User Manual and the Sony WM-FX28 Service Manual. So I went ahead and bought it.

The number one reason a cassette player stops working is that the rubber belt inside has worn out, stretched, or just straight up broken. It’s a simple repair – if you can get the right sized belt. Thankfully I was able to find a Sony WM-FX28 replacement belt online for cheap. The other thing you need to do (especially after replacing a belt) is to calibrate the speed of the motor, so I just added a speed calibration test tape to my order.

Now the site I bought these from, Fix Your Audio, is one of the few (if only) places left in the world where you can reliably get these kinds of replacement parts for cassette equipment. It’s located in Slovakia, but I was pleasantly surprised that it only took a week for the package to get to me in the USA.

The last tool I ordered was a Cassette Head Demagnetizer. As tapes play, the magnetic material in the tape can slowly magnetize the cassette head (the part which rubs against the tape to read the signal). This will affect the quality of the sound, but more importantly, a magnetized head can potentially erase a tape as it’s playing. So it’s important (especially when getting a used player) to demagnetize the head so it won’t ruin your tapes.

Speaking of, even if I got the walkman working, I didn’t have any cassettes to actually play on it. So I started hitting up eBay and Discogs looking for Hawaiian cassettes. I was able to get a (still sealed) copy of Hawaiian Slack Key Guitar Masters along with a copy of my all-time favorite album: Mākaha Bash 3: Live At The Shell.

With all my orders in place, it was time to clear some desk space for the project. The first things to arrive were the walkman itself, the replacement belt and calibration tape, and the copy of Mākaha Bash 3:

As listed, the radio functioned just fine, but nothing moved when pressing the tape controls. So, following the service manual, the first step was to pop off the back shell:

Oops! As you can see, I got the shell off, but at the expense of a few of the plastic tabs that attached it. I probably should have been a little more gentle with the old plastic, but I also think the service manual deserves some blame here. I exaggerate, but step 1 is like “insert screwdriver here to separate the shell”, step 2 is “open the tape door and release this tab” then step 3 is like “in step 1 you should have removed the shell in this exact order”.

Anyway, there’s still plenty of tabs left, so next I took a look at the mechanism itself. Looking closely at the motor on the right, you can see where the belt is tangled around the shaft, rather than looped nicely around the brass pulley:

Adding batteries and pressing play, you could see the motor trying to run but the belt was just getting caught tighter underneath. Removing the belt allowed the motor to run quite freely:

Disregarding that growing pile of broken plastic bits from my bad shell removal, you can see how much the old belt stretched by comparing it to the replacement side by side:

With the belt out I took a moment to clean things with some compressed air along with good ol’ cotton swabs and isopropyl alcohol. Then I installed the new belt:

With the new belt in, I reinserted the batteries and tried the controls. Play would run the gears but that little white arrow in the center kept snapping back and forth with an awful clicking noise. Fast-forward would only run for a second before stopping, while rewind caused the the whole thing to lock up while the motor spun away, rubbing on the belt but not getting any traction.

I couldn’t see anything that looked straight up broken: no missing teeth on the gears and no stray bits of plastic that I wasn’t responsible for. I continued my search (and cleaning) by popping out the entire board and checking everything underneath:

Finally I decided my best bet was to try lubricating all of the gears. I used the plastic on plastic grease I’d bought for when I eventually tune-up the floppy drives in the macs I’m still restoring:

I made sure to get the grease onto the shaft of every rotating part in the mechanism. After I was satisfied that I’d gotten it everywhere it needed to be, I popped in the batteries and tried the controls again:

Sony Walkman WM-FX28 with new belt and greased gears

It worked! Play, fast-forward, and rewind all ran perfectly with no clicks or hang-ups. I really wish I’d had the presence of mind to record how it ran like before the repair, but c’est la vie. With the mechanism working again, I put the whole thing back together, thankful enough plastic tabs remained for it to stay together.

The next step was to demagnetize the head. According to the instructions (and people online) you want do this far away from any kind of magnetic media, as the demagnetizing wand is basically a wall-powered electromagnet. In the age of solid state drives that might not be a risk in most modern offices, but with my other retro restorations I’ve actually amassed a small assortment of floppy disks and hard drives in my workspace. So it’s off to the dining room table:

To use the wand you have to plug it in several yards away from the target, approach it very slowly, touch the items to demagnetize for roughly five seconds each, then back away slowly and unplug it back where you started. If you go too fast, or touch the wand on the head for too long, or cut the power while you’re still too close, you risk doing the exact opposite of what you want and magnetizing the head even more.

So I propped open the cassette door and dutifully snuck up on my unsuspecting walkman like I was pranking it while it slept. Who said electronics restoration wasn’t exciting?

With that finally out of the way, the last step was to calibrate the speed of the motor. The idea is to play the calibration tape, which has a 3 kHz tone recorded onto it, and verify that the pitch isn’t too high or too low. You use a tool called a “frequency counter” to see the exact frequency being played, and adjust the speed of the player’s motor until the tone is exactly 3 kHz.

I don’t have a physical frequency counter, but thankfully there’s plenty of free smartphone apps that work just fine for the job. Also this particular walkman exposes the speed adjustment potentiometer through a tiny hole in the back of the case, making it easy to adjust the speed without having to take everything apart.

So I inserted the calibration tape, connected headphones, cranked the volume, and installed Audio Frequency Counter onto my phone. The app picked up the signal at a few hundred kHz too fast, so I adjusted it down with a tiny screwdriver until I was as close as possible to 3 kHz:

Finally, after all that work, I put in my Mākaha Bash 3 cassette, took a deep breath, and pressed play:

It worked perfectly! I listened through the whole album, both sides, without any issues. I made lunch while listening through my very anachronistic modern earbuds, since I don’t have any old over-ear style headphones.

After that first playthrough I did redo the speed calibration just in case things had loosened up, but otherwise, I think it’s safe to call this repair is complete. Despite some missing bits of plastic, I’m happy with the results.

Now the only question is: do I stop here, or do I need to take the next step and get a cassette recorder up and running? We’ll see.


My Mac SE/30 Part VIII: SCSI2SD Setup #2

In Part VII of this series, I planned out the configuration for the SCSI2SD I’ve installed in my vintage Macintosh SE/30. Now it’s time to actually set everything up.

As described in my last post, I plan to divide up a 2 GB SD card like this:

Partition NameDescriptionTypeSector OffsetSize (Sectors)Size (Bytes)
SCSI2SDBackup UtilsFAT065,53633,554,432 (32 MB)
Unallocated65,5362,0481,048,576 (1MB)
Macintosh SDSCSI 1HFS67,5843,670,0161,879,048,192 (1.75 GB)
Unallocated3,737,600184,32094,371,840 (90 MB)
Total3,921,9202,008,023,040 (1.87 GB)
My partition setup for a 2 GB SD card (1 sector = 512 KB)

Creating the FAT partition

The first step is to create the 32 MB partition at the start of the card. Usually SD cards come with an existing file system, so the first thing we need to do is remove it. On Windows 10 you can launch the Disk Management control panel by bringing up the Start menu, typing “disk management” and selecting Create and format hard disk partitions.

Disk Management - New 2GB SD Card
Disk Management – New 2 GB SD Card

On my PC, the card is mounting as the F: drive, and you can see it already has an existing FAT file system that spans the entire card. The first task is to delete that file system. This is as simple as right-clicking on that F: drive at the bottom of the window and selecting Delete Volume….

You’ll be prompted that this will delete everything – go ahead and click Yes. Afterwards it should look something like this:

Disk Management – Unallocated 2 GB SD Card

Now we want to add our new 32 MB FAT file system. Right-click on the unallocated space for F:, select New Simple Volume…, then click Next >. Here’s where you’ll set the size to 32 MB:

New Simple Volume Wizard – Specifying Volume Size

After clicking Next > again, you’ll be prompted to pick the new drive letter. It’s annoying that you can’t keep using F: here, but don’t worry, you can change it later if you really want to. On my computer it picked K:. I just took a note of the new drive letter and clicked Next > again. Here’s where you’ll be prompted to pick the type of file system and give the volume a name.

As per my table above, I’ve picked FAT and set the label to “SCSI2SD”:

New Simple Volume Wizard – Specifying File System and Label

Click Next > and then Finish to create the new partition. Afterwards, Disk Management looked like this:

Disk Management – New 32 MB FAT Partition

Perfect! I now have my 32 MB FAT partition and an approximate 1.84 GB of unallocated space for SCSI2SD to use. More importantly: I have the peace of mind that I can insert this card into any computer without risking an accidental format which corrupts my vintage mac data.

Configuring the SCSI2SD

The next step is to configure the SCSI2SD, which means we’re done with the Disk Management tool and can return the SD card to the SCSI2SD. Then we’ll need to go and download the latest scsi2sd-util6 and (if you’re out of date) the latest firmware file for your model.

There’s a quick start guide (at the link above) that details installing the PC driver, connecting your PC to the SCSI2SD via a USB cable, and flashing the latest firmware file. Once you’ve done all that, it’s time to use the scsi2sd-util6.exe tool to configure the SCSI2SD.

For my model SCSI2SD (a 2020 V6), installed in my SE/30, this is how I configure the General Settings tab:

scsi2sd-util6 – General Settings

Next it’s time to set up the virtual SCSI devices. I select the Device 1 tab and configure it accordingly:

scsi2sd-util6 – Device 1

Now, you might be asking, “Why am I setting up the 32 MB FAT partition” as a SCSI device? Will the classic mac be able to use it?

Unfortunately, no. While various vintage mac utilities will see that the device exists, they won’t be able to access any files on it. However, the SCSI2SD V6 has an interesting feature, where, when you plug it into your PC with the USB cable, it will try to expose the SCSI devices to the computer as USB drives. So by setting this virtual device up, the 32 MB FAT drive appears on my PC and files can be managed directly without having to to remove the card. It’s not strictly necessary, but it is a nice bonus perk.

Anyway, on to the Device 2 tab, where again I set the values according to the table above:

scsi2sd-util6 – Device 2

You’ll notice that I haven’t done anything to “spoof” a particular drive by modifying the values for Vendor, Product ID, etc. Other guides often recommend using particular settings here, so that you can use the official Apple tools to format the new drive. The official tools only support specific drive models, and so must be tricked into thinking that’s what’s connected.

However, after much painful experimentation, I’ve found that neither Apple HD SC Setup (for System 6) nor Drive Setup (for System 7) works properly for this, even if you trick it into running. The newly setup drive will report its capacity incorrectly and suffer from constant data corruption and loss. I tried many times and was never even able to install a fresh system onto it.

In the end, I found that the only working way to set up the mac drive was to use the 3rd-party formatting tool Lido, which has no restrictions on what drives it can format, and works flawlessly.

But I’m getting ahead of myself. After setting this all up, the next step is to save it to the device, by selecting File > Save to device. I’ve also found it prudent save a backup of this configuration to my PC by doing File > Save to file… and naming it scsi2sd.xml. After that you’re ready to (safely) eject and disconnect the USB cable. Now the SCSI2D is ready to be used on my SE/30.

Some finishing touches

But before we switch to the SE/30, I have a couple more “quality of life” tricks I’d like to share, revolving around the card’s little FAT partition. I’ve curiously described as for “Backup Utils” and that’s what I use it for: backing up copies of all PC-side files I used to set up the device.

So, reinserting the card back into my PC, my drive now looks something like this:

SCSI2SD 32 MB FAT Drive Contents

You can see copies of the scsi2sd-util6 tools, the latest firmware, the quick start guide PDF, and the configuration backup scsi2sd.xml we just created. But there’s also two other files: dd.exe and manage.cmd.

If you’re familiar with common Unix utilities, dd.exe is just dd for Windows. It’s a small but powerful utility for reading and writing directly to a drive by sectors, making it very useful tool for creating and restoring backups as disk images.

The other file, manage.cmd, is something I whipped up myself. It’s a small script which makes it easier to use dd.exe to backup and restore the SCSI2SD virtual devices as individual image files.

Launching it provides this menu:

manage.cmd Menu

This is part of the reason why I saved my SCSI2SD config as the file scsi2sd.xml. Manage.cmd reads this file to determine which sector ranges on the disk correspond to virtual devices. This is also why I explicitly added the FAT partition as a device in the SCSI2SD config – so this script would be able to see it.

Now typing “1” and pressing enter, the script will prompt me, for each virtual drive, where to save a backup disk image. Then it will invoke dd.exe with the proper arguments to save off the image files:

manage.cmd Backup

To restore those image files, it’s as simple as entering “2” at the menu, and you’ll be walked through the reverse – prompting for the image files you wish to write back to the SD card. It’s not the most sophisticated system, and still doesn’t give me direct access to files within those images, but it’s a little nicer than having to run dd.exe by hand.

Note: The manage.cmd script expects to be run from the actual SCSI2SD SD card, as it uses that location to determine which disk to read and write from. If you use it, make sure that you also keep a backup copy of your scsi2sd.xml file in a place other than the actual SD card.

Well, that’s it for this post. Stay tuned for Part IX, where we’ll get back onto the SE/30 and start setting up a working system!


Want to read from the beginning? Start at Part I.

P.S. My thoughts on how to plan, execute, and document setting up my SCSI2SD was largely influenced by these two blog posts: SCSI2SD: Using a SCSI2SD adapter to setup your 68k Macintosh and Apple IIe Card and SCSI2SD: How I have my SCSI2SD setup for my Apple IIe card in my LC 475. Enormous thanks to the folks at for all of their detailed posts on classic macs and the SCSI2SD.

My Mac SE/30 Part VII: SCSI2SD Setup #1

In Part VI of this series, I replaced the dead hard drive in my vintage Macintosh SE/30 with a modern SCSI2SD.

Next I’ll need to set up and configure the SCSI2SD to meet my needs. Now, despite the wonderful versatility of the device, its configuration is not for the faint of heart, especially when used in a vintage Macintosh. Thankfully this isn’t the first time I’ve tangled with configuring a SCSI2SD – when I initially restored my Power Macintosh 8600/200, I also used a SCSI2SD instead of a standard hard drive. In fact, I used this exact SCSI2SD!

See Adventures in Macintosh restoration Part VI: Booting up and jacking in for that story.

In short, the power of the SCSI2SD is that it can be set up to emulate one or more virtual drives all on a single SD card. However classic macs (or at least, the official disk tools needed to set up a new drive) are picky about the brands and models of drives they support. So while you can set up your SCSI2SD virtual drives to “spoof” those blessed drives, the configuration software is not very user friendly.

Sectors not files

The biggest annoyance with the SCSI2SD is how it stores these drives on the SD card. You’d expect that it would just use a standard formatted SD card with each virtual drive stored as a separate “image file”, like with the Floppy Emu. Instead the SCSI2SD writes directly to a range of raw sectors on the SD card, ignoring anything else about how the card is set up.

So if you pop the SD card into your PC, you won’t see obvious files like “Disk 1.dsk” or anything. In fact the default SCSI2SD configuration is a 2 GB virtual drive written to sector zero at the very beginning of the card. Which is actually kind of a problem.

Now, this is a simplification, but sector zero is usually where the filesystem information (the names and locations of each file) is stored. A PC will look at sector zero for a filesystem it understands, which these days is typically FAT, FAT32, exFAT, or NTFS. It won’t recognize a vintage filesystem that may be there. So when it doesn’t find the data it expects, it’ll assume the disk needs to be formatted, and will prompt you to do so.

Accepting that prompt will, in all likelihood, completely corrupt or destroy the data on your card. Yikes!

With this setup, the best you can do is always remember to say no to formatting, which will preserve your data, but also severely limit how you can interact with it. You can still use modern disk imaging utilities to back up the entire SD card to an image file on your computer. However you won’t be able to easily separate out multiple virtual drives, let alone transfer individual files in or out of them.

A better setup

While complete disk images are useful (and better than no backup), I’ve found a better setup which makes life a little easier on myself.

The trick is to put a modern filesystem on the card, starting at sector zero, but not take up the entire disk with it. If I only create a small 32 MB FAT partition, and leave the rest of the disk “unallocated”, then when I stick the card into a PC, it’ll see that small filesystem and not prompt me to format anything. The PC will ignore all of the unallocated space after the partition, so that’s where I’ll configure the SCSI2SD to write its data.

By keeping them separated in this way, neither the PC nor the SCSI2SD will ever interfere with one another in regular, everyday usage. You can add or remove files on that small FAT partition without ever worrying that you’re corrupting the vintage data managed by the SCSI2SD.

Okay, but why only a 32MB FAT drive? Why so small?

While my space needs for this vintage SE/30 are small, I don’t really intend to use the FAT partition for all that much. So there’s no need to take away a bunch of space that the SCSI2SD could be using. In fact, as we’ll see later, I only intend on using the FAT partition to store some useful tools relevant for using the SCSI2SD.

Disk planning for my SE/30

Speaking of my SE/30, my original plan was to have two virtual drives for this machine, one with System 7.5.5, and another with System 6.0.8 for older, “32-bit dirty” applications. For more information about what “32-bit dirty” means, see My Mac SE/30 Part IV: Upgrade Plans.

However, while people may have “dual-booted” back in the day, in my experiments I found that keeping a System 6 setup was completely unnecessary. There’s really nothing I can’t do in System 7 – if I need to run “32-bit dirty” apps, it’s easy enough to just toggle the switch in the Memory control panel and reboot. Actually switching between System 6 and 7 meant toggling the switch and letting each system “rebuild the desktop file” on the disk every time it restarted, which was annoying.

Ultimately, I found it much easier to just keep a set of System 6 images on my Floppy Emu, and plan on booting from floppy if I ever really need to run System 6. With that decision made, the biggest question now was how big of a disk did I need for System 7.5.5?

The maximum size of a classic mac drive (using the vintage HFS filesystem partition) is 2 GB. Realistically, I’ll probably never need that much space on this machine. I mean, the old drive in this machine wasn’t even 0.5 GB and would have been crazy expensive at the time. At my first pass, since I only want to manage one virtual drive, my first instinct is to create a 2 GB disk on a 2 GB SD card.

However, just because an SD card is advertised as being 2 GB, doesn’t mean it can literally store 2,147,483,648 bytes of data. Beyond the regular manufacturer marketing shenanigans of memory bytes vs storage bytes, different SD cards from different manufacturers may have different numbers of actual bytes available.

Which means, rather than use all of the unallocated space for my virtual drive, it’s safer for me to make the disk smaller and leave a decent safety buffer at the end. That way if my card dies and needs to be replaced with a new one that happens to be slightly smaller, I won’t have to worry about my backups not fitting.

Anyway, in the end, I decided to set up my 2 GB SD card like this:

Partition NameDescriptionTypeSector OffsetSize (Sectors)Size (Bytes)
SCSI2SDBackup UtilsFAT065,53633,554,432 (32 MB)
Unallocated65,5362,0481,048,576 (1MB)
Macintosh SDSCSI 1HFS67,5843,670,0161,879,048,192 (1.75 GB)
Unallocated3,737,600184,32094,371,840 (90 MB)
Total3,921,9202,008,023,040 (1.87 GB)
My partition setup for a 2 GB SD card (1 sector = 512 KB)

I have two main partitions: the 32 MB FAT drive at the start to satisfy modern machines, and a 1.75 GB HFS drive for my SE/30. I’ve also put a small 1 MB buffer between the partitions for a little extra safety and separation, and finally there’s some 90 MB of buffer at the end of the disk.

With that plan in mind, stay tuned for Part VIII, where I’ll walk through the steps of actually setting up the SD card in this fashion.


Want to read from the beginning? Start at Part I.

P.S. My thoughts on how to plan, execute, and document setting up my SCSI2SD was largely influenced by these two blog posts: SCSI2SD: Using a SCSI2SD adapter to setup your 68k Macintosh and Apple IIe Card and SCSI2SD: How I have my SCSI2SD setup for my Apple IIe card in my LC 475. Enormous thanks to the folks at for all of their detailed posts on classic macs and the SCSI2SD.

My Mac SE/30 Part VI: SCSI2SD Installation

In Part V of this series I upgraded the RAM and ROM in the vintage Macintosh SE/30 that I’ve been restoring. In this post, I replace the old dead hard drive with a modern SCSI2SD.

As mentioned in Part II, the hard drive that came in this machine was a 426 MB Segate ST1480N, an upgrade from a previous owner. It doesn’t boot anymore but that’s no surprise – it’s 27 years old at this point. I tried hooking it up to my bridge Power Mac 8600/200, but it didn’t even recognize a drive was connected.

In any case, my plan was always to replace the drive in this SE/30 with a SCSI2SD, which, if you aren’t aware, is a modern device that can simulate one or more SCSI drives using an SD card for storage:

Mounting options

I’ll cover setting up the software side of the SCSI2SD in a later post, for now, the goal is just to get it physically installed and hooked up where the old hard drive used to be. At first glance, it seems pretty straight-forward, but there’s a few minor problems.

First off, the original hard drive screws into the sides of SE/30’s metal drive caddy, and the SCSI2SD only has bottom mounting screw holes. Given that the SCSI2SD is just an exposed circuit board, even if you could mount it, you wouldn’t want the metal caddy to short anything underneath the board.

Secondly, the original hard drive was oriented such that the side with the SCSI port was to the rear of the machine. If I mount the SCSI2SD the same way, then the side with the SD card and USB port will be pointing inside. One of the main reasons I want to use the SCSI2SD is to be able to easily access the SD card to transfer files, make backups, or even swap it out for testing alternate cards. As-is, I’d have to take the case off every time to get to the card, or to connect a USB cable to configure the device itself.

Thankfully, Colin from This Does Not Compute solved both of these problems by designing a custom SCSI2SD Bracket for the Mac SE/30. Instead of mounting to the drive caddy, the 3D-printed plastic bracket mounts to the back of the SE/30’s chassis, and aims both the SD card slot and the USB port out the rear of the case. As detailed in his video, the SE/30 supports expansion cards, and so there’s a small opening in the rear of the case to expose any extra ports those expansion cards might have.

Since I have zero plans for adding any expansion cards, I decided to go with his bracket. He doesn’t sell them but he open-sourced the design, and since I don’t have a 3D-printer of my own, and since this was my first ever time needing a 3D-printed part for a project, I finally got to see what it takes to get someone else to make it for me.

The process was easier than I expected. After getting a little lost looking at sites that handled bulk orders, I found makexyz, an on-demand service that will forward your job to a local printer to print your one-off part. I just uploaded the STL file, kept the default settings, and in a week or so I got the bracket in the mail:

Extending the LED wire

While I waited for the bracket to arrive, I set to solving another problem. The SE/30’s case has small LED in the front that wires to two pins on the hard drive in order to show disk activity. The SCSI2SD does have pin holes for an activity LED, however with the SCSI2SD flipped around, the original wire doesn’t reach.

Wanting that LED to be functional, and not wanting to modify the original wires in any way, I finally invested in a set of various connectors and crimps and made a custom “extension wire”:

I also added a matching header to the SCSI2SD board. Hooking up the LED is very much optional, but I was positively ecstatic to see it flashing when all was said and done. But I’m getting ahead of myself.

Minor bracket adjustments

When the bracket arrived, it came time to actually install it into the machine. However I hadn’t noticed that in Colin’s setup he had removed the original hard drive caddy in order for his bracket to fit. I, on the other hand, intended on leaving the empty caddy in so I wouldn’t ever misplace it.

This was almost a non-issue, except for one tiny little spot where the bracket and caddy intersected. So I busted out my Dremel and cut a small groove in both the bracket and the SCSI2SD board itself:


With the grooves cut, the bracket cleared the caddy and installed quite easily:

The LED extension wire I made reached perfectly, and looking at the back of the machine, you can see where the bracket mounts to the expansion port slot to expose the SD card and USB port.

But now there was another problem. The SCSI port on the motherboard is near the rear of the machine, very close to the original hard drive’s port. As such, the original SCSI cable was very short, and though it’s kind of hard to see, it’s now stretched to its absolute limit to reach the port on the backwards SCSI2SD.

Not wanting to add any unnecessary strain on the parts, I went and ordered a new longer cable. And by new, I actually mean new! I assumed since SCSI cables aren’t used anymore I’d have to buy an old one, but I was happy to find someone making brand-new SCSI cables in various lengths. It worked perfectly:

The last thing to do was connect power. Now, the SCSI2SD can be powered one of three ways: directly over the SCSI cable (if the motherboard supports it), via USB (if you really want to run a cable there) or via a standard floppy power-cable.

While technically the device draws way less power than a traditional hard drive, and could therefore probably run off just the SCSI cable, I wasn’t sure that the SE/30 motherboard supported and I happened to have a spare Molex-to-floppy power adapter handy. So it was easy enough to continue using the existing hard drive power cable to power the SCSI2SD instead:

With the SCSI2SD installed, my planned hardware upgrades were complete. While there’s still work to be done inside, such as re-capping the analog board and completely cleaning and greasing the floppy drive, for now, it was finally time to close up the case.

I popped off the small door to the rear expansion slot (and taped it inside the case so I wouldn’t lose it), so here you can see the final result from the rear:

I think it looks quite clean, and since it’s recessed inside the case, it’s not immediately obvious that it’s even in there. The SD card sticks out a bit but doesn’t clear the case, so there’s little risk of accidentally bumping it.

That’s it for now, stay tuned for Part VII, where we finally turn to the software-side of restoring this machine.


Want to read from the beginning? Start at Part I.