Hello I am not Multidisk but are there any news about a build for the Raspberry 2? Would really like to use KryoFlux with mine.mr.vince wrote:Multidisk: I think we have KF running on the new Raspberry 2, so yes, the new USB can cope with the data rate... Would need to release a build, but if you email me, can get you in touch with the dev.
Seeing as RockyBOulder has already resurrected this thread this year, I wonder if the Raspberry Pi 3 makes it practical with both USB and processor speed? I'd love to have my (external SCSI enclosure based) KryoBox fully self contained.mr.vince wrote:Hi, this never made it to "for production" status. Although the USB seems to be quick enough, the computing power itself is limiting.
Has there been any change on your position regarding open sourcing the driver or USB command specification for Kryflux?JASPP wrote: ↑Wed Mar 25, 2015 10:17 pmI appreciate your position. I'm not asking for your time or assistance to write the driver - I can do that, what I'll require is either a TRM for the Kryoflux or source from an existing driver to base it on. I'm happy to give you the end result if it helps your goals.mr.vince wrote:JASPP: The problem we're facing is a ton of communities reaching out and we only have limited manpower, hence we need to concentrate on what helps our goals. No offense, just not trying to say yes and then not delivering.
I'll look at the library. JASPP precludes commercial use, so we're in alignment on that point.mr.vince wrote:If you look at the IPF Decoder Library, you will also find the licence. If you want to go through image files, yes, this is covered by the licence. In general, since the MAME licence is used, commercial use is excluded.
The RISC OS community are still looking for a way to access floppy discs on a Pi and I'm still willing to code a RISC OS driver for Kryflux, if I can get hold of either the USB driver source or USB command specification.
Why not dump the MacOS version completely (as it's effectively dead in the water in its current state) and get a Raspberry port going? If it's a question of resources, the community is full of capable people who are ready to help. If you'd like to keep it in-house (as I suspect) than how can we buy you more time to do this? I'd be happy to chip in a few bucks and many more are willing too, I bet. Please let us know how we can move this forward...