Hello Kay,Hi Paolo,
I tested all my BlueSCSI V2 with real Mac SE/30. So far, we have not had any problems with our products other than scratches during PCB manufacturing. The scratched BlueSCSI will not be shipped and will be in my possession forever...
I'm also unfamiliar with what you're trying to do, so I need help from others.
@eric @Androda @OneGeekArmy , any ideas?
If you need an immediate reply, I think it would be a good idea to access Open Retro SCSI/ BlueSCSI/ BlueSCSI-support on discord and ask.
I'll share the 2.048GB file generated already, which has been proven to work on many of my Macs.
Good luck!
PS: Try some SD cards. Some products are incompatible with it.
Thanks a lot for your comments and for sharing the 2Gb image, I really appreciate your support. I will try it as soon as possible.
I am sure the hardware is ok: it’s beautifully made, you tested it, it works on a Portable, I’m not even taking the trouble of further testing it on my SE/30.
I also tried three different SD cards, always the same result.
What seems to me not OK is the configuration of the virtual devices.
For example: baseline device image naming fails to be recognized (even on the Mac). The extended naming seems to be required, including the LUN id and the sector size.
Additionally, there’s little to no documentation about the customization of the device geometry.
From the log I could infer that if a *.ini file is NOT present on the SD card, then some default settings are used.
So, I copied the “bluescsi.ini“ file from the repository and started peeking inside, it’s a mix of SCSI2SD xml configuration file, plus some other BlueSCSI specific stuff.
Is there any documentation about this?
Anyhow, I also posted a comment on the GitHub page, apparently someone managed to have it working with an Apollo, so I’m sure it can work with the HP 712 series…