Replies: 2 comments 3 replies
-
|
Mounting images is something that MacOS does - SCSI/BlueSCSI is a block level device, it has no idea that it's running on MacOS or if the OS mounts it or not. Can you provide the log file? (the errors would be in the log file, if any, not the ini file) - but again, this is something to do with MacOS not BlueSCSI so I suspect no errors will be in there. Clicking on the desktop or moving things around likely updates the DesktopDB and causes things to appear (nothing to do with the specific SD Transfer app itself). Please also include how you created these images - if one image has a different SCSI driver on it - it can cause issues such as this. I'd recommend making them all in DiskJockey and you can drag images on top of DJ to see what SCSI drivers they use. Also you can use something like SCSI probe to see what SCSI devices are there and if they are mounted or not - it could be just MacOS not updating the desktop with all the drives - which are actually there. Lastly - while you can create and use 7 images - is there a use case for this? One System and one 2gb or data HFS volume would store most anything you'd ever wish to run on a Classic. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your advice erichelgeson. In the log.txt log file (I enabled the debug option in bluescsi.ini), there is no error and all partitions are seen and mounted correctly, even if they are not seen in the Desktop, or rather, only ID 6 (where the System is) and ID 0 are seen, while the other intermediates are not, despite trying to force the SCSI IDs into the bluescsi.ini file in this way: scsi_ids=0,1,2,3,4,5,6. There may be some defractmentation errors but I understand that by using the -X option with the cp command, I can solve the problem. The .hda images, first were taken from the reference link from the site [BLUSCSI] (https://bluescsi.com/), already ready with System 7.1 and 7.5.3 but I also tried to create .hda images both from the command line with Mac, and with disk Jockey, but the behavior is exactly identical, so without solving the problem (I both formatted the partitions with Macintosh Classic, which using hformat from terminal which is faster). I also tried to use only two .hda images (even just the System image); they are seen immediately on the desktop but, for example, if I insert the floppy, the floppy icon only appears when I open BLUSCSI Tool Transfer and then lock on the desktop, so the behavior is exactly like when I have multiple .hda images in the SD Card. So even just with one or two images .hda I didn't let go of the problem. I also used the BLUESCSI card on another Macintosh Classic but I didn't solve the problem. I also tried to power the card with a USB cable (thus excluding the POWER ON from the board), but this didn't help either. I couldn't update the Firmware in any way: I tried everything that was proposed, namely via USB, via SD (written not recommended), through the QMK Toolkit program. It works perfectly with 6.0.8 with 7 512 MB images This is an example of a log in which I tried to use an ExFAT file system, but I also tried FAT32. Here instead there are info of the disk images using Disk Jokey: |
Beta Was this translation helpful? Give feedback.
-
That is for BlueSCSI v1 - it looks like you're using a V2 - Please reference the docs on bluescsi.com and this wiki, not the V1 wiki. https://github.com/BlueSCSI/BlueSCSI-v2/wiki/Updating-Firmware#usb-method |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I used the instructions in that link to upgrade the firmware to my BlueSCSI V.2- But I didn't succeed. Could it be that my BlueSCSI is defective? I bought it last summer. |
Beta Was this translation helpful? Give feedback.
-
|
Could you provide more information on what didn't succeed? The update method is something the Pi has built in from the Raspberry pi foundation - I've not seen it fail. Please try a different USB cable as that is usually the culprit with poor quality cables or "power only" cables. Nothing so far has indicated anything is wrong with the BlueSCSI - again choosing when and how to mount drives on the desktop is something the Macintosh does - not BlueSCSI. |
Beta Was this translation helpful? Give feedback.
-
What happens now?
I only see two partitions. HDA (rarely more than two when I access the Desktop).
The disk images are called as follows:
HD60_512 System.hda
HD50_512 Data Disk.hda
HD40_512 Data Disk.hda
HD30_512 Data Disk.hda
HD20_512 Data Disk.hda
HD10_512 Data Disk.hda
HD00_512 Data Disk.hda
They are 524 MB each, and at startup, my Classic, only sees the BOOT image (HD60_512 System.hda that loads System 7.1 correctly), and the HD00_512 Data Disk.hda. The other images do not appear on the Desktop (they all have different names).
If I try to insert a Floppy, this seems to work, but in truth I don't see the floppy icon on the Desktop. To Eject the floppy I use diskcopy which automatically ejects the Floppy when it starts.
I discovered that if I leave BlueSCSI Utility for file transfer and then click on the desktop, all the missing partition icons magically appear and I can access them (even that of the floppy if it was inserted before). For example, if I want to eject the floppy disk, I always have to click on the BlueSCSI Utility program for Transfer and then click on the desktop, then the floppy will be ejected.
Some idea?
In the bluescsi.ini file there is no error, the images are always loaded correctly using any System (therefo also > 7.1)
Beta Was this translation helpful? Give feedback.
All reactions