Thankfully I'm far too broke to be able to afford Amigas so that's not an issue I have to deal with
-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
Introducing scuzEMU, a SCSI Emulator Utility
- Thread starter saybur
- Start date
Ha! If the Amiga community is really as toxic as I've heard, that's probably a good thing, as you suggest!Thankfully I'm far too broke to be able to afford Amigas so that's not an issue I have to deal with
The extreme prices, of course, are probably a symptom of the problem. My impression is that they all think they're this exclusive little club of ultra geeks, so snobbery and belittlement of beginners and anyone else who dares to intrude runs rampant. Artificially keeping prices unreasonably high for almost everything Amiga seems to maintain this exclusivity by acting as a barrier to entry that locks most people out completely.
It's a shame, really, as from what I've read about the Amiga platform, I find it's really quite a fascinating and intriguing platform I wouldn't have minded exploring, especially considering how it shares a CPU architecture (Motorola 68k) in common with early, pre-PPC Macs (indeed, with the proper tools, an Amiga can run early Mac OS versions almost better than a contemporary real Mac could, with the Amiga's access to bigger and better screens being one of the main reasons why, I'm sure).
c
I've finally gotten the toolbox commands supported in MAME for file downloading. I did most testing with scuzEMU 0.5, but the closed source BlueSCSI "SD Transfer" program works too because I return their dumb magic ID string. Either way I can get things from the Garden into the emulation in record time now. Just download the files to the configured "shared directory" and scuzEMU will see them.
Just came acrost this program, I have had the bluescsi for awhile. I just came across this program today. I've found the default blueSCSI tool really hit and miss, for some reason it completely ignores some files. Based on the post here it sound like the program should work with most forks but the github only says zuluscsi and scuznet. This will work with my bluescsi or do I need to get a different emulator?
From what I understand, it may work just fine as it's using the Toolbox API calls that the BlueSCSI originally introduced.
The official tool for the BlueSCSIs checks for a specific string as a form of DRM (though I don't know if this changed in the meantime), so that sort of lockout is the software checking the hardware, not the other way around.
Presumably scuzEMU just ignores any such strings being presented by the hardware.
You can always give it a try.
It should work fine, like @Daniël described the toolbox is (nominally) the same across devices. I'd be happy to add BlueSCSI to the list once someone tests it out, I don't own one to use myself and I haven't heard of anyone trying it. If you do, it'd be awesome if you post the results!
I tried it breifly and it seems to work, is ask what SCSI ID. I am assuming the file transfers happen and so type of virtual SCSI device. Files appeared to populate the list correctly were the official tool does not. I didn't copy any files yet, but so far it looks good
Cool, thanks for reporting that. For file transfers any SCSI ID that the device is on will show the same file list: for example, if you've got HD0.img, HD1.img, and a bunch of CD images in a CD3 folder, you can use 0, 1, or 3 as the SCSI ID to see the "shared" folder files. The ID is more important for changing images, in the previous example only ID 3 would work for changing CDs and it would only apply to that emulated CD drive.
Just for background info, at the moment scuzEMU doesn't support scanning for devices, to avoid having to match a specific firmware name or send vendor-specific commands against potentially incompatible devices. It sounds like a future toolbox version might change how this works, so if that happens a "Scan" button might be added.
Just for background info, at the moment scuzEMU doesn't support scanning for devices, to avoid having to match a specific firmware name or send vendor-specific commands against potentially incompatible devices. It sounds like a future toolbox version might change how this works, so if that happens a "Scan" button might be added.
Dunno how I missed it but RH bumped their hardware once again. https://shop.rabbitholecomputing.com/products/zuluscsi-blaster?variant=51474823840060 Not sure when this happened but the new blaster looks great, USBC connector, optional CD audio dac, now based on the RP2350B and up to 18MB/s. I need to get one of these new boards to try out with the toolbox, thanks for all your hard work on this software. Love to see the playing field leveled dunno why the BS folks are so petty.
Oh FYI, I'm not affiliated with RH, but I am a big fan.
Oh FYI, I'm not affiliated with RH, but I am a big fan.
I should have responded earlier to this addition and the work @Arbee did to get the backing added into MAME. It is a super-cool feature for the emulator and I'm glad scuzEMU has been working well for people. Thanks Arbee!
If I get another SCSI emulator device it'll probably the Zulu. I have used this utility in-place of the BlueSCSI tool. As I said I'll get a correct file list more consistently. I will get file errors sometime when I try to copy files. but sometime that happen sometime with the internal tool. The SD transfer tool hasn't been updated in years, so I am not sure if it get fixed. I wonder though since I still some file transfer issues here and there if this is a bug or issue with at the blueSCSI level itself. Both my external 25pin and internal 50pin models have issues, but I don't recall seeing anyone else complain. You tool does however seem to work more consistently though
Similar threads
