Dumping the contents of SCSI devices using BlueSCSI V2

I challenge U to read a SCSI drive I have I'd 0 terminated only- it comes from a broadcast computer I'm able to dump contents onto a DVD ram DVD but cannot recognise the file system it's a distro of Linux mayb bsd stripes I'm very computer literate and eng from years ago do U accept the challenge

how can i use a scsi scanner to a modern pc thru USB 3.0 ?
Do this exist a scsi to usb

I LOOOOOVE that you're keeping and forwrding the log files and images for the developpers. It's so cool when youtubers actually PARNER with people, and be real community members instead of just grandstanders. Cheers!

Are you sure the earlier problems with the HDD's weren't due to the cheapo hard driver power supply you were using? Might be worth retrying with the big old AT power supply that you used at the end, since I've had various problems with those hard drive power supplies that come with a IDE-USB adapters.

I don't think the "dual images" bug had anything to do with the SCSI drives. I can't imagine a scenario where a drive controller (the controller board on the disk) would respond to both ID 0 and ID 7, much less being able to function if it had such a peculiar fault. Pretty sure it's an issue with the BlueSCSI.

I was surprised to see it work with removable disks, especially since you powered on the BlueSCSI before inserting a disk. I would have expected it to scan the drive, receive a "not ready" error, and then proceed to the next ID. However, the giveaway came at the end, when it ejected the Zip disk; this thing clearly has specific support for removable media.

Hi Adrian,
thanks for testing the BluSCSI. Allow me some remarks:

1. SCSI cables
Here in Germany we still have Partsdata which I as an Atari user know since the nineties shortly after Dr. Zellmer opened his shop. Partsdata is still around and still sells a variety of SCSI cables although although the selection is smaller than 30 years ago.

2. Communication problems
I remember that especially with early ACSI to SCSI adapters there were several issues: SCSI drives may want to see the parity handled correctly, furthermore there is an additional phase, the reselection phase. When the drive goes busy it can drop the transfer and do a relection when it's done. ACSI was quite limited and early ACSI to SCSI adapters didn't implement these features so that several drives failed. Although it's not important for the BlueSCSI many adapters had the problem that only the first command group (group 0) could be used. Does BlueSCSI implement parity and reselection correctly? Otherwise you may run into trouble.

There is useful little software that will show you connected serial ports, show notifications and even allow to launch another program when specified serial port is connected, it's called Serial Port Notifier. I use it, and it's really useful.

I am also very satisfied with the initiator mode of BlueSCSIv2. With this I was able to read most of my SCSI disks from old Unix workstations. It is important that the power supply for termination (TERM_POWER) only comes from one source.

But to connect SCSI disks to a modern computer, I recommend the SCSI adapter "LSI SCSI Ultra-320 Controller LSI20320IE". It is a PCIe card for which there are signed drivers for Windows 7, which also work without any problems under Windows 10 and of course also for Linux. With an appropriate adapter, you can also connect ancient SCSI1 devices to this ultrawide SCSI card.

I dunno if it's related, but the SCSI CD-ROM drive I use with my A1200 will only work if set to ID 7, it has a small dial on the back of the drive to select ID, rather than jumpers.

I had that blue Zip drive as my old job that was USB. You should find one of those.

Wait why does the Pico's LED need to be blinking when they've built an "ACT" LED onto the board next to "PWR"? And why isn't that LED actually working either, if the unit is actually doing the thing?