Mac Classic - will it ever run again!!

[rubber_jonnie]

When you try to initialise the disk, what kind of message do you get ? Which software do you use to initialize ?
If you haven't tried already, here are the two file for setting up the HD.
First expand the Apple_HD_Setup until you have a Mac 68k executable.
Expand the patch and apply the patch, then you can run the Apple HD Setup and it will work on any SCSI HD, not only the one sold by Apple.
Also, make sure to have your Volumes < 2Gb.

Honestly, I don't think it's a software issue, I think there is something off with the BlueSCSI, which is annoying, but it could be something as simple as it doesn't like the termination, or the SD cards.

Different SD cards do seem to give different, but inconsistent results.

I can boot from your image, but it fails even with shift held down. The other image, which was also >2GB did boot to System 6.8.0L, and seemed to work just fine, but when I successfully installed 7.0 over the top, it crashed during boot even with shift held down.

When I couldn't prep the disk, it either couldn't partition, or failed to initialiise. Running the test said it was unable to write to the disk. It may work with another disk prep tool, so I'll see if I can give it a try, thanks.

On a positive note, after replacing those resistors, it's been running just fine today, so that seems like a result, just need to figure out the BlueSCSI now.

[olivier.jan]

Looks like a write issue, I agree.
I have an internal BlueSCSI which I need to build and flash. If I can find time over the weekend I’ll build it and try it inside my Classic, just need to remove the SCSI2SD inside it. Hopefully you’ll have found a solution by then :)

[rubber_jonnie]

Looks like a write issue, I agree.
I have an internal BlueSCSI which I need to build and flash. If I can find time over the weekend I’ll build it and try it inside my Classic, just need to remove the SCSI2SD inside it. Hopefully you’ll have found a solution by then :)

Thanks, and I really appreciate all your help, thank you.

[Tomswork]

Have you set the drive name and the rom limit of 20 megs it drove me nuts on the classic
Tom

@rubber_jonnie

[rubber_jonnie]

Have you set the drive name and the rom limit of 20 megs it drove me nuts on the classic
Tom

@rubber_jonnie

When using my own disk images, created with dd on my mac using the recommended settings, I can't even initialise a blank drive, so I'm unable to name it. When I use the 'test' option, it complains the drive cannot be written to.

I know these images work, as they did so on my Archimedes, even if the drive couldn't be booted from.

For images I've downloaded that do boot, but cannot be upgraded (not sure why), I can't subsequently upgrade that disk which is running 6.0.8L to System 7.

With regards to the ROM, what do you mean, 20 Meg limit? The machine has a 40meg physical drive, so I don't think that's the problem.

What I am testing today is termination. I read last night that with the BlueSCSI 1.1-a that I have, terminator power from the SCSI bus sometimes isn't good enough on some machines, but is taken directly from the BluePill if USB power is used.

I also need to try the patched HD setup program as well.

[rubber_jonnie]

Small update. I used the patched 7.5.3 hard disk setup tool and was able to prep the disk. This is progress, now trying a clean install of System 7.

[stephen_usher]

I'm crossing my fingers.

This is why I liked the ZuluSCSI. You can put into the configuration file an option to make the device report to the machine that it has Apple firmware and so the unpatched MacOS HDsetup program just works. :-)

[rubber_jonnie]

I'm crossing my fingers.

This is why I liked the ZuluSCSI. You can put into the configuration file an option to make the device report to the machine that it has Apple firmware and so the unpatched MacOS HDsetup program just works. :-)

Given I got the PCBs for free and haven't spent a lot on the two I've built, I can't really complain :)

But yes, fingers crossed :)

[olivier.jan]

Great news ! Actually you should be able to use the un-patched version with BlueSCSI too, by specifying the drive model in the bluescsi.ini file, but I never managed to get it to work.

[rubber_jonnie]

Great news ! Actually you should be able to use the un-patched version with BlueSCSI too, by specifying the drive model in the bluescsi.ini file, but I never managed to get it to work.

I have been looking for a decent reference for the bluescsi.ini file, but I'm not finding much, and what I so seems to suggest that it only required under certain circumstances, such as for the Mac Plus and MSTE.

Are there any good references that you know of?