Yesterday, something happened when I was using an external BlueSCSI and my SE/30 froze but later refused to boot. I put the microSD card into a full sized SD card adapter and then put that into my modern Mac, but it can't even see it in the Finder or Disk Utility or SD Card Formatter. Seems like the SD card is now totally dead. It was a 16GB PNY card that really hadn't been used all that much. Anyway, I then ordered two SanDisk Extreme 32GB microSD cards from Amazon which arrived today, and I formatted them ExFAT, which is correct for BlueSCSI. Because I didn't have a backup of the data I lost, I copied one of the bootable *.img files from my MacSD's SD card to my new microSD for BlueSCSI, then renamed it: HD10_512 OS71.img

I've heard that the .hda extension no longer matters on BlueSCSI, so I tried it like that with *.img at the end, but it refuses to boot. I then copied over another image from my MacSD which is a bootable 7.5.5 image, also 2GB in size. That one started to boot, but it had Bad F-Line instruction and Bus errors, which is very odd. I then turned to Disk Jockey for help, trying to get the System 7.1 image to be compatible with BlueSCSI.

I dragged the System 7.1 image file to Disk Jockey and it shows me this...


I then clicked "Create a Volume image" which it saved to my Downloads folder. Sadly, that image won't boot on BlueSCSI either, even if I changed the extension from .img to .hda. I tried and failed on a BlueSCSI with June firmware and on a different BlueSCSI with April firmware (2022).

I then turned to the Image Creator tab of Disk Jockey to create a blank 2GB image like this...
My intention was to mount my MacSD image and mount the new Disk Jockey created image in Basilisk II so as to manually copy the files from one image to the other. Sadly, Basilisk wouldn't mount the image created by Disk Jockey, even after I changed the filename extension from .img to .dsk. And yes, I have my Basilisk II preference file setup with the correct path.

Here is the problematic System 7.1 boot image (2GB in size), copied straight off MacSD's SD card and zipped (not modified by Disk Jockey):

And here's the System 7.5.5 boot image (2GB in size), also copied straight off my MacSD's SD card and zipped (boots off BlueSCSI but with Bad F-Line Instruction and Bus Errors using my BlueSCSI with June 2022 firmware):

Can anyone tell me what I am doing wrong in conjunction with Disk Jockey so as to make BlueSCSI boot from it?

James, for the 7.5.5 image did you edit the gusd resource to enable booting on an SE/30?

>> rikerjoe said:

James, for the 7.5.5 image did you edit the gusd resource to enable booting on an SE/30? Click to expand...

Yes. I have both a hacked and stock version for use with a stock or non-stock SE/30 ROM, in addition to a System 6 System folder, and System Picker can select among them...



My external BlueSCSI has June 2022 firmware, and it was that unit in which my PNY 16GB SD card suddenly died. The card is dead because my Mac cannot see it when inserted. But it shouldn't have died due to overwrites because it was never in continuous use. The dead of that card is odd. Anyway, when I formatted my brand new 32GB SanDisk Extreme microSD card as ExFAT via Disk Utility (since SD Card Formatter stupidly formats it as FAT32 and gives me no option to use ExFAT), I then copy my 7.1 image and my 7.5.5 image to the card. The 7.1 image is not recognized at all, and it tries to boot from the hacked 755 System Folder on the other image, but I get Bad F Line instructions and Bus Errors. However, if I then move that card to my desktop edition BlueSCSI with April 2022 firmware, it will boot into 7.5.5 without those errors. But even then the 7.1 image will not mount on the Desktop, despite the fact the BlueSCSI Log file is showing nothing wrong with either image.

This is why I turned to Disk Jockey, in hopes it would work some magic and resolve the problem, but thus far it has not.

---

I was told via PM that my earlier post wasn't very clear, so the following is a simplified and numbered recompile of what I had previously written. My hope is that someone can offer me help out of this deep hole of confusion I'm in right now. Thanks.

1. I have 2 BlueSCSI devices:
   a) External type with June 2022 firmware
   b) Internal type with April 2022 firmware
2. It was the External type in which my 16GB PNY SD card suddenly died two days ago when used with my SE/30.
3. I had no backup of my dead PNY card, but the content was largely what is used on my MacSD devices, which work perfectly.
4. I copied 2 images from my MacSD SD card to a brand new SanDisk Extreme microSD card freshly formatted as ExFAT in Disk Utility on a Monterey M1 MacBook Pro:
   a) OS_71.img -- which I renamed: HD10_512 OS71.img
   b) OS_755.img -- which I renamed: HD30_512 OS755.img
5. I put that brand new SanDisk card inside my External type BlueSCSI with June 2022 firmware.
6. When I try to boot with that card containing 2 images, it tries to boot into 7.5.5 from HD30_512 OS755.img, but it gives me Bad F-Line Instruction or Bus Errors during repeated reboot attempts. One time it did boot to the Desktop before it froze with a Bus error, and only the OS_755.img was mounted on the Desktop. The HD10_512 OS71.img is not recognized at all.
7. I then tried renaming the files with an .hda extension, but to no avail.
8. I then tried dragging the images one at a time from my MacSD's SD card to Disk Jockey so as to allow Disk Jockey to create it's own image, but those Disk Jockey recreated images sadly don't have any good effect when used in BlueSCSI.
9. When I put my new SanDisk Extreme microSD card into my other BlueSCSI internal type with April 2022 firmware, it boots to the System 7.5.5 Desktop without any errors at all, from the HD30_512 OS755.img, but the HD10_512 OS71.img is no where to be found. Here is LOG.txt as copied from the SD card after that boot:
   
   BlueSCSI <-> SD - https://github.com/erichelgeson/BlueSCSI
   VERSION: 1.1-20220404-USB
   DEBUG:0 SCSI_SELECT:0 SDFAT_FILE_TYPE:3
   SdFat version: 2.0.6
   SPI speed: 50Mhz
   SdFat Max FileName Length: 32
   Initialized SD Card - lets go!
   Sd MID:3 OID:SD
   Sd Name:SE32G
   Sd Date:5/2016
   Sd Serial:849571216
   - HD10_512 OS71.img / 2147418624bytes / 2097088KiB / 2047MiB
   Not an image: ._HD30_512_OS755>img
   - HD30_512 OS755.img / 2147483648bytes / 2097152KiB / 2048MiB
   ID:LUN0:LUN1:
   0:----:----:
   1: 512:----:
   2:----:----:
   3: 512:----:
   4:----:----:
   5:----:----:
   6:----:----:
   Finished initialization of SCSI Devices - Entering main loop.
   
   
10. Frustrated, I then thought about using Disk Jockey to create a blank 2000MB image, thinking I could just use Basilisk II to mount that blank and also mount my MacSD image, then do a Finder copy within Basilisk II to move all files from my MacSD 2GB image to the newly created Disk Jockey 2GB image. Sadly, Basilisk II won't recognize the Disk Jockey created image even if I rename it *.dsk, which prompted my post in that Disk Jockey thread, asking for help.

Any further thoughts would be greatly appreciated.

Thank you!

I have just posted a beta of Disk Jockey 3. Check out the top post in this thread!

It's a huge one. I need a nap.

>> OneGeekArmy said:

I have just posted a beta of Disk Jockey 3. Check out the top post in this thread! It's a huge one. I need a nap. Click to expand...

A well deserved nap too! Absolutely amazing work.

>> JDW said:

A well deserved nap too! Absolutely amazing work. View attachment 13997 Click to expand...

Thank you :)

@OneGeekArmy

I did my first test of the Apple II features today. You edited your opening post to say the following:

• Look inside DOS 3.3 disks

Unfortunately, I am not able to get a file listing for my DOS 3.3 disks. ProDOS disks do work, however.

Attached is a ZIP archive for you to test both image types.

One is a blank DOS 3.3 *.DO image and the other a blank ProDOS 143KB *.PO image. The *.DO throws the following error:



I have other disk images with a *.DSK extension which also throw the same error as above. One of them is named "Apple II Diag v4.7-1986.DSK" for example.

>> JDW said:

@OneGeekArmy I did my first test of the Apple II features today. You edited your opening post to say the following: Look inside DOS 3.3 disks Unfortunately, I am not able to get a file listing for my DOS 3.3 disks. ProDOS disks do work, however. Attached is a ZIP archive for you to test both image types. One is a blank DOS 3.3 *.DO image and the other a blank ProDOS 143KB *.PO image. The *.DO throws the following error: View attachment 14003 I have other disk images with a *.DSK extension which also throw the same error as above. One of them is named "Apple II Diag v4.7-1986.DSK" for example. Click to expand...

Thanks for the test!

Are you certain you are using the beta version? It's a separate link, the regular version will not update to it: https://diskjockey.onegeekarmy.eu/files/diskjockeybeta/Disk-Jockey.dmg
Also, the error message above is different in the beta version.

Your DOS disk works fine for me:


In the view showing the surface of the disk, orange sectors are system reserved, red sectors are catalog sectors and dark blue are for user files. When you select a file in the list (there are no files in your image so it won't show anything), its sectors will highlight in purple.

I should probably add a legend to the diagram :)

Very interesting. I'm here at work right now on my late 2015 5K iMac 27", and I am definitely running version 3.0 here. Sure enough, no problem. So I guess I was using an old version at home last night.

One thing I do notice though on this Mac OS Mojave machine is that the very top content is getting cut off a little bit, and making the window taller does not fix that...



Here's a different disk image and the result is the same...


I will check it on my MacOS Sonoma M1 Mac later when I get home and report back then.

I'm at home now on my MacOS Sonoma M1 MBP, and it works great. The top part of the dialog is not cut off either.


So the problem I reported in my previous post about the top part being cut off seems to be exclusive to MacOS Mojave. Not a major problem at all. I just wanted to mention it.

And as I said earlier, your app is amazing. Bravo!

>> JDW said:

I'm at home now on my MacOS Sonoma M1 MBP, and it works great. The top part of the dialog is not cut off either. View attachment 14007 View attachment 14008 So the problem I reported in my previous post about the top part being cut off seems to be exclusive to MacOS Mojave. Not a major problem at all. I just wanted to mention it. And as I said earlier, your app is amazing. Bravo! Click to expand...

That's super. Glad you like it!

Yes, I need to run a little bit of regression testing on previous versions of macOS. Little things have changed in the way interface bits are calculated and it's not always obvious which parts are impacted.

Thanks for the heads-up!

Well the beta is going to have to stay in beta for a while longer because Xcode 15 (which I use) doesn't create correct builds for some older versions of macOS. And I still want to support at least 10.13 High Sierra with Disk Jockey.

https://github.com/apple/swift/issues/68163

Thanks @JDW for making me do non-regression testing. This might have flown under the radar.

(the Disk Jockey beta should still run fine on macOS >= 10.15 Catalina)

@OneGeekArmy
I downloaded Disk Jockey 3.4.5 today to see if it would allow me to get Total Replay v5.2 to work with my BlueSCSIv2.

METHOD #1 (ends in failure)

I download the TR5.2 *.hdv file and copy it straight to my SD card, then rename it so I can give it a SCSI ID: HD6-TotalReplayv5.2.hdv. But when I boot my Color Classic Mystic (in 24-bit addressing mode, with IIe Card installed, ProDOS extension loaded), the drive won't mount on the Desktop The BluSCSI log file shows a WARNING about it not being a valid Macintosh image (of course not! it's ProDOS!)

METHOD #2 (also ends in failure) (now works, as per my newer post below)

8 STEPS:

1. Launch Disk Jockey 3.4.5.
2. Click the "Macintosh" tab.
3. In the middle section (BSv2 photo shown at left), set SCSI ID to 6.
4. Click "Advanced Options" to expand it.
5. Delete the HFS partition.
6. Click the tiny square + icon, choose "Existing Image File...", then find and select Total Replay on your hard disk.
7. Click the purple "Create the Image" button shown in the screenshot below. That creates an *.hda file.
8. Move that *.hda file to your SD card and test with BlueSCSI.

I tested with my BlueSCSIv2 attached to my Color Classic Mystic (24-bit address mode, ProdDOS Extension loaded). Sadly, the Total Replay 32MB drive still won't mount on the Desktop.

Coming back to my modern Mac and putting that HDA into Disk-O-Matic shows this:



As you can see above, no errors in the BlueSCSI log this time; but again, it won't the ProDOS volume at the Desktop on my vintage Mac, despite my having the ProDOS extension loaded. And booting the IIe Card software doesn't show that ProDOS drive in SmartPort drives either.

I am, however, able to get my MacSD to show it because MacSD has a "Composites" feature that works some kind of magic to support those HDV files. And I am also able to attach my FloppyEMU (with Apple II firmware) to the Y-cable of my IIe Card and also get Total Relay to work.

How to get Total Replay's HDV image to mount at the Desktop (on my Mystic) using BlueSCSI and Disk Jockey 3.4.5 still eludes me, however.

If you or @eric have any ideas, I would love to give them a try!

Thank you!

>> JDW said:

@OneGeekArmy I downloaded Disk Jockey 3.4.5 today to see if it would allow me to get Total Replay v5.2 to work with my BlueSCSIv2. How to get Total Replay's HDV image to mount at the Desktop (on my Mystic) using BlueSCSI and Disk Jockey 3.4.5 still eludes me, however. If you or @eric have any ideas, I would love to give them a try! Click to expand...

Maybe you've already seen this, but version 5.0 of Total Replay has been converted to an HD image that works with BlueSCSI here. Perhaps you could use this as a model?

Unfortunately the way Mac handles ProDOS drives is different vs a real ProDOS drive - only way I ever got it to work was to make a ProDOS drive on the mac, then copy Total Replay over - which is what BK linked to above. Ron made a video on the process here

>> eric said:

Unfortunately the way Mac handles ProDOS drives is different vs a real ProDOS drive - only way I ever got it to work was to make a ProDOS drive on the mac, then copy Total Replay over - which is what BK linked to above. Ron made a video on the process here Click to expand...

Unfortunately that approach doesn't work with TR5.2, as it has pre-packed a lot of files into a single large binary file. So the contents are too large for the copy approach, and the files we want to remove are packaged up with data we want to keep.

How I got it working was with the latest disk jockey, but I merged the Total Replay ProDOS *partition* image with my HFS *drive* image, which worked fine for me.

EDIT: I suspect the ProDOS only drive image made by Disk Jockey actually worked, but it didn't auto mount on boot. @JDW did you check to see what Drive Setup says and see if it can mount the drive?

>> Nycturne said:

Unfortunately [Ron's] approach doesn't work with TR5.2... Click to expand...

Even if it did work (and yes, I've watched his otherwise excellent video 4 or 5 times since its release), it's a LOT more time and effort than just attaching a FloppyEMU to your IIe Card's Y-Cable and accessing Total Replay (any version) as a SmartPort0 drive.

>> Nycturne said:

EDIT: I suspect the ProDOS only drive image made by Disk Jockey actually worked, but it didn't auto mount on boot. @JDW did you check to see what Drive Setup says and see if it can mount the drive? Click to expand...

Drive Setup 7.3.5 shows this (and remember, my ProDOS image's SCSI ID is 6):



However, I now see that SCSI Probe shows this...



Holy cow...

I clicked "Mount" in SCSI Probe and it obeyed me!



I can now move it into Slot 5, Drive 1 within the IIe Card software, and I can confirm it now works!



So again, this was done with Disk Jockey, using METHOD #2 in my previous post.

Interesting that BlueSCSI won't mount the ProDOS drives automatically in System 7.1 though. When I connect my FloppyEMU (A2 firmware) and use any TR image, they mount on the desktop when the ProDOS extension is used.

At any rate, the SOLUTION for now is to use SCSI Probe to MOUNT it.

THANK YOU for the suggestions, @Nycturne !

>> JDW said:

Interesting that BlueSCSI won't mount the ProDOS drives automatically in System 7.1 though. Click to expand...

This has nothing to do with bluescsi - bluescsi presents data on as SD card, it's up to macos if it wants to mount it or not. Glad you got it working.

>> JDW said:

Drive Setup 7.3.5 shows this (and remember, my ProDOS image's SCSI ID is 6): View attachment 19607 Click to expand...

Keep in mind that's HD SC Setup, not Drive Setup. Of the two Apple tools, only Drive Setup can mount drives. But it does require 7.1.2 or later. I use it with 7.5 as my main OS on my 040 Mac. SCSI Probe is probably easier than going through the trouble of installing 7.1.2 and Drive Setup if you are on 7.1.

>> eric said:

This has nothing to do with bluescsi - bluescsi presents data on as SD card, it's up to macos if it wants to mount it or not. Glad you got it working. Click to expand...

Correct, as far as I can tell, System 7 just skips non-removable drives for mounting if it doesn't detect an HFS partition on it.