M1kerochip
commented
3 months ago With the standard log.txt, you can see the BlueSCSI is starting fine, and mounting images etc. This is the last config I tried, where I specifically named the HDD Images etc, but, it didn't work with just the defaults, either. (I figured it was worth a shot)
Hi,
I've got an Atari ST with an AdSCSI micro board from ICD. (Or more accurately, it's a board that's been reverse engineered by t0ri, and as far as I know, is functionally an exact replica)
I've tested and used it with SCSI2SD v5.0 and the board works perfectly, so, I know the ST and the converter work ok. (Transfer rate is benchmarking at around 960Kb/sec, and is perfectly fine with the SCSI2SD v5, with 3x HDD and one CDRom)
The ST boots up, but, the activity lights come on, and stay on, on the BlueSCSI, and once you get to the desktop, no HDD is accessible, and neither are either floppy (A:\ or B:\, connected separately, or together.) (So, without the HDD booting, and floppy disabled, I can't load any software to detect the drive/adapter and partition etc)
I noticed there is a "MegaSTE" mode added in an earlier build where you can swap the ID and LUN, and I've tried that, but, it made no difference. (The AdSCSI Micro only supports SCSI ID 0,1,2,3. It's designed for one single device)
The BlueSCSI v1.1 I built myself, but, I've tried it in an Amiga A2000 with GVP Zorro II card (SCSI+8mb fast) and, it's been working perfectly in that machine for months. I even built a second BlueSCSI, and that too works in the GVP but not with the AdSCSI Micro.
The HDD Image I've tried is an 8GB image, one single HDD. Tried with 256MB, 512MB and so on, too.
The same image works fine on Hatari, and written to the SD Card on the SCSI2SD, not that it matters, since even a blank image fails to boot, and leaves the floppy disabled.
So, to that end, is there a debug build of the latest release?