Replies: 5 comments
-
Hey sorry you're having trouble, and thanks for the kind words about the project. This is an odd one - could you please attach the LOG.txt. Can you also take a photo or screen shot of the checksum errors? Lastly - could you try using one of the pre-made blanks in the Usage page under the first link. Those are made by DiskJockey and will give us a common base to test with. |
Beta Was this translation helpful? Give feedback.
-
I'll provide the data in the order you requested it, starting with the screenshots. The first screenshot shows the checksum error Disk Copy throws when mounting the image. I mounted it again immediately after and it is fine (second screenshot).
I have tested two setups, while I was at it. Setup 1: Corresponding log file: LOG-20221012-1050.txt Setup 2: Corresponding log file:LOG-20221012-1102.txt I stuck with the LCIII for testing, based on the fact it produced similar results with similar symptoms as did the Mac IIci. Possibly also of importance: any file handling on the SD card for these setups was done using Linux (specifically Kubuntu 22.04). Let me know what you think. |
Beta Was this translation helpful? Give feedback.
-
Hello Eric, Just to let you know I tried a third known-brand SD-card (SanDisk this time) with just a blank 100MB image, but the results are the same as before. I think it to be highly unlikely that the problem is related to any individual SD-card. |
Beta Was this translation helpful? Give feedback.
-
Well, this evening I received an e-mail from Jean-Michel over at Onegeekarmy, stating the following: _You have recently purchased a BlueSCSI from me and I wanted to inform you about a potential issue I’ve discovered, as well as a way to solve it. As I mention in the little note that accompanies the shipment, your STM32 runs faster than the usual 72 MHz. It turns out that the STM32 I have received from my supplier are actually not STM32s but APM32s. In essence, the APM32 has a larger memory pool (256 KB instead of the 128 KB of the STM32) and it’s a little faster for a few operations. For its use in BlueSCSI, a faster version of the firmware is needed. This is why yours was flashed with the 96 MHz firmware. As it turns out, in some cases, this is not enough._ He has provided a link to the most recent firmware: Hoping this might resolve the issues I have seen, I updated the firmware on my BlueSCSI, which completed succesfully.
Short version: it does not solve the problem. Things I have tried:
I have attached the log file from the SD card. |
Beta Was this translation helpful? Give feedback.
-
Any thoughts on this? |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
I want to start off by saying that I really love the product and am impressed by its features and build quality.
I do have a rather strange issue that is hard to pinpoint. I have already exhausted the troubleshooting section of the Github page.
First the current setup:
Past setup:
The issue:
When I mount disk images from either one of the HDD images or the CD image, most images mount fine but some give me checksum errors. However, when I mount the image again, there is no checksum error. Any and every installation I performed using disk images stored on the virtual media, failed. All installs were done to the virtual disk with SCSI ID 1.
The disk images used come from different sources and at least one set (System 7.5) is verified to be 100% error free.
Steps undertaken:
Observations on the Macintosh IIci:
It boots fine of the virtual CD and virtual HDD (ID 1) with System 7.5 installed. It does not crash and I can reboot it several times without issue. It also boots fine off the Disk Tools floppy containing the patched HD SC Setup.
System 7.5 disk images loaded from physical media (SCSI ZIP-100 drive) don't cause checksum errors and will go through the entire installation process. The same goes for a set of floppies (System 7.0.0).
However, the very same System 7.5 disk images, when copied from the ZIP-disk to the second virtual disk, will start throwing up checksum errors (as stated in the description of the issue, happens randomly to images, not the same ones over and over).
Mounting any set of disk images from the Legacy Recovery CD in the virtual CD drive produces checksum errors in a similar pattern.
Observations on the Macintosh LCIII:
A reproduction of the behavior seen on the Macintosh IIci, including a succesfull installation from disk images mounted directly from the ZIP-100 disk. However, after installation I get an illegal instruction at boot time requiring me to restart the LCIII.
It has mounted up to quite a story. I'm happy to perform any additional troubleshooting steps if required. And just to make it clear: I'm equally convinced there is something wrong with my setup as I am convinced there may be something wrong with the BlueSCSI. No offence meant. Any help is appreciated!
Beta Was this translation helpful? Give feedback.
All reactions