• 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.

Mac se/30 SCSI2SD version

MegaImg

Well-known member
I need so guidance. I just got my 5.1 and I can not get the drive Initialized  I have a 32 ROM Fix from GGLAB and I can not boot to a Patch 7.5.3 HD tools to get it working...Any workaround to be able to get the drive recognized on 7.1 or 7.0 

 

cheesestraws

Well-known member
7.5.3
There is an issue booting 7.5 on the SE/30 with a 32-bit ROM, I believe.  You will probably have better luck with a 7.1 Disk Tools image with a patched HD SC setup.  There is almost certainly one available on the Internet, but I think I have one here somewhere if you can't find it.

Some people don't have any luck with the patched HD SC Setup at all, and in that case use Lido to format the disc.  I've never had a problem personally, so I can't say why that happens.

 

karrots

Well-known member
I personally use this guy's image. Then either copy the update files in using HFS tools on Linux and boot on my Mac Classic or mount the image in Basilisk II per his instructions, update the minimal system to system 7.5.5, then write the image to SD card.

Using Basilisk II the install stakes only a few seconds.

He also has various tools in the image like Lido.

https://www.savagetaylor.com/downloads/

 

karrots

Well-known member
Mine's a RevF, not the latest, but does use the same 6.3.1 firmware (22nd April 2020) as the '2020' version. Never turned on SCSI2.

Mine would crash out when doing installs (always at the 'writing' stage), and sometimes doing file copies. I could also get a working system through copying the System Folder, but it's not an ideal solution.
I had similar issues on a Classic II the system 7.5.3 install would hang building the system file. I ended up doing all updates with Basilisk II then writing the image to the SCSI2SD. After that all is well. 

Base image with system 7.5 or 6.0.8 minimal system here https://www.savagetaylor.com/downloads/

 

aeberbach

Well-known member
Hey I think this is fixed!

Solution: the patched Apple 7.5.3 disk setup tool that is commonly available does not correctly create a volume, it just appears to - when the installer tries to write to that volume it hits whatever didn't get fixed by the patch and it fails.

Fix: Lido does correctly create the volume and after that SCSI2HD V6 (2020c, 6.3.1 firmware) works with no special settings on a SE/30.

I was unable to try the Floppy Emu hard drive image since that is not supported on a SE/30. I suspected Lido might work better than the patched tool but I could not find a system disk image with Lido on it. Eventually I went back to the spinning HD with 6.0.8 on it, took the 6.0.8 .dsk image from BMOW that has the patched 7.5.3 HD tool, trashed it, and put Lido on the disk image instead. After reinstalling the SCSI2HD and booting from the altered .dsk Lido performed a partition/format.

6.0.8 install was initially a failure. The HD operations seemed fine but the Emu could not recognise one of the floppy images - I'll try again after another download.

7 was successful. I am now going through 7.5.3 on another partition of the same SCSI unit and everything appears to be working. Fingers crossed!

I'm feeling confident enough to solder a LED header on the SCSI2HD board and to put the back of the case back :) If you are having trouble with the V6 at all, be sure to try Lido and not the Apple patched HD tool.

 
Last edited by a moderator:

MegaImg

Well-known member
I had similar issues on a Classic II the system 7.5.3 install would hang building the system file. I ended up doing all updates with Basilisk II then writing the image to the SCSI2SD. After that all is well. 

Base image with system 7.5 or 6.0.8 minimal system here https://www.savagetaylor.com/downloads/
I just build it using Basilisk to...any way using dd so create additional disk and send it to specific sector on the SD Card...Specially if you have like 8Gb SD, Disk1 (boot), Disk2 (Maybe another version)

 

karrots

Well-known member
I don't think dd can start at a specific location. But you could always merge two images together with cat. Then write the whole image to the SD card and set the disk start locations properly in the SCSI2SD utility.

I did something similar where I wrote out my image to the first part of the disk. Then just told the SCSI2SD there was the second disk starting where the other disk left off. I then formatted it on the Mac and use it as my scratch space. So in the end I have 2x 2GB physical disks that show up. Then inside the computer you could always run the installers again on the second disk rather than have to mess with merging images.

 

MegaImg

Well-known member
Got it Installed and working, thanks everyone, I created my own disk image using Basilisk II. My SE/30 have a clean 32bit ROM and 128mb of RAM, so I needed to be sure that the image was patch special using 7.5.5. I will try 8.1 soon, now that is just swamping the SD. I 3D printed a mount to be able to access the SD card and upgrade firmware...came out really good...still a work in process...added the headers for the LED light! 

I like to know if their is a way using DD, to create additional disk and send it to specific location on the SD card. SCSI2SD tool let you provision additional partitions and give you the info on the SD location...does anyone has try this...That way I can have on SD card multiple OS and switch between the booting partition, I can maybe do this directly from the Mac...

SCSI2SD_Mount.jpg

 
Last edited by a moderator:

cheesestraws

Well-known member
I like to know if their is a way using DD
Use the oseek/seek option (some older-style dds will only support calling it seek; newer ones will accept either seek or oseek).  Note, though, that this is in units of block size, so you may need to move your discs around and/or adjust your block size in the dd command.

 
Last edited by a moderator:

MegaImg

Well-known member
Use the oseek/seek option (some older-style dds will only support calling it seek; newer ones will accept either seek or oseek).  Note, though, that this is in units of block size, so you may need to move your discs around and/or adjust your block size in the dd command.
Thanks...I will try it! any web page or place to get more info!

 
Top